Each one stands alone and is self-hosted and MCP-native. They compound because they write to the same content-addressed graph — so memory, code decisions, conversations, routing and test runs are one auditable history rather than five that need reconciling.
What git was to source code, AgentStateGraph is to agent state.
Rust core · 73 MCP tools · 8 language bindings · 4 storage backends · HTTP API
Write a fact once. Every tool remembers it.
90+ MCP tools · REST API · Lens UI · SQLite or Postgres · zero telemetry
The context lives with the code, not in a chat log.
Rust core · 64 MCP tools · 9 languages · git-native sidecar · CLI, MCP and HTTP surfaces
A conversation is a tree. Stop storing it as a line.
Self-hosted · multi-LLM · built on AgentStateGraph
One passing run is a sample, not a test.
Scenario runner · judge scoring · run diffing · sealed audit epochs
Optimise cost per unit of work, not cost per token.
Not in the request path · every routing decision a commit
AgentStateLabs v1.0.0 is a suite-level release covering AgentStateGraph, CTXone and AgentStateDeveloper. Each product keeps its own version, so read the stage column rather than the suite number.
| Product | Role | Stage | Site |
|---|---|---|---|
| AgentStateGraph | The substrate | v1.0.0 · GA | agentstategraph.dev |
| CTXone | Memory and context | v1.0.0 · GA | ctxone.com |
| AgentStateDeveloper | Code intelligence | v1.0.0 · GA | agentstatedeveloper.dev |
| ThreadWeaver | Conversation state | Beta | threadweaver.org |
| AgentStateCrucible | Testing and validation | Early access | agentstatecrucible.dev |
| AgentStateRouter | Execution routing | Alpha | agentstaterouter.dev |
Nothing requires the whole suite. See how they combine in practice, or read why we built one substrate instead of six integrations.