KnowledgeMay 12, 2026·2 min read

Statewave — Memory Runtime for AI Agents (API + SDKs)

Statewave is a self-hostable memory runtime: ingest episodes, compile memories, do semantic search, and build token-bounded context bundles via REST.

Agent ready

This asset can be read and installed directly by agents

TokRepo exposes a universal CLI command, install contract, metadata JSON, adapter-aware plan, and raw content links so agents can judge fit, risk, and next actions.

Native · 94/100Policy: allow
Agent surface
Any MCP/CLI agent
Kind
Workflow
Install
Manual
Trust
Trust: Established
Entrypoint
uvicorn server.app:app --host 0.0.0.0 --port 8100
Universal CLI install command
npx tokrepo install e900097c-4946-5899-829b-0b9db4c2adf7
Intro

Turn messy agent history into structured, searchable memory with an API contract: episodes → compiled memories → ranked context bundles for prompts.

Best for: Agent products that need durable memory beyond chat logs (support agents, coding agents, multi-channel assistants)

Works with: Self-hosted API (default localhost:8100); Python + TypeScript SDKs; modular connectors packages (per README)

Setup time: 15–30 minutes

Key facts (verified)

  • Quick start runs the API on port 8100 and exposes /docs and /redoc endpoints (per README).
  • API includes endpoints like POST /v1/episodes, POST /v1/memories/compile, and GET /v1/memories/search (per README table).
  • README lists connectors packages (e.g., GitHub/Slack/Markdown) as separate modular installs via npm.
  • GitHub: 214 stars · 1 forks; pushed 2026-05-11 (GitHub API verified).

Main

A memory workflow that stays practical:

  1. Ingest “episodes” as append-only facts (events, decisions, commits, incidents) — keep them small and timestamped.
  2. Compile memories on a schedule (or after a threshold) so retrieval stays fast and deterministic.
  3. Use semantic search for “similar past issues”, but always ask for source episode IDs so you can audit the chain.
  4. Build a token-bounded context bundle for prompts instead of dumping raw history.

Statewave’s API-first shape makes it easier to integrate multiple channels without rewriting memory logic per tool.

FAQ

Q: Do I need a GPU? A: No. The README says the API process is CPU-only; GPUs only matter if you self-host a model/compiler.

Q: Is there auth? A: Optional. The README mentions API keys via the X-API-Key header.

Q: Can I use it without connectors? A: Yes. The README says connectors live in a separate repo and are optional; they talk to the public HTTP API.

🙏

Source & Thanks

Source: https://github.com/smaramwbc/statewave > License: AGPL-3.0 > GitHub stars: 214 · forks: 1

Discussion

Sign in to join the discussion.
No comments yet. Be the first to share your thoughts.

Related Assets