Local-first tooling

Agent Kit: the continuity layer, running in your repo

Agent Kit is Stateora's free npm CLI and MCP server. It builds the same portable project state packet as the hosted beta — decisions, blockers, context, and progress — but keeps everything local to your repository, with no account and no upload required.

What it is

Agent Kit reads and writes a .stateora/ folder in your repo: your project summary, goal, current state, decisions, blockers, and session receipts, stored as JSON and Markdown you can read, edit, or commit like any other file. From that saved state it can generate a next-agent prompt, recommend which coding agent to route to, and package a rescue prompt when a session hits a context limit — all without leaving your terminal.

It's available now as [email protected] on npm.

Install and use it

No account or sign-up needed. Run this in the root of the repo you want continuity for:

npx stateora init --name "My Project" --summary "What this repo is" --goal "What I want next"

That scaffolds .stateora/ and adds a Stateora block to your existing AGENTS.md, CLAUDE.md, and .cursor/rules/ instruction files (creating them if they don't exist yet), so agents that read those files already see your project state. From there:

stateora status                                    # check plan, active repo, resets left
stateora context --level working                   # print a context capsule
stateora route "Fix a small bug"                   # get an agent routing suggestion
stateora prompt --agent claude                      # build a next-agent prompt
stateora rescue --sourceAgent claude --output "Continue after a limit"
stateora mcp                                        # start the MCP server for your editor/agent

Point your MCP-compatible editor or agent (for example Cursor, Claude Code, or Codex) at stateora mcp as a stdio server so it can call the tools below directly instead of you running commands by hand.

MCP tools

Once connected, an agent can call these five tools against your local project state.

stateora_get_context

Pull a context capsule (flash, working, full, or audit level) for the agent to read.

stateora_get_next_prompt

Build a next-agent prompt with your saved decisions and progress embedded.

stateora_append_receipt

Record what a session did, so the next agent (or you) can see the trail.

stateora_recommend_agent

Get a routing suggestion for which coding agent fits the next task.

stateora_prepare_rescue

Package a hit-a-limit rescue prompt when a session runs out of room.

Agent Kit vs. hosted beta

Both paths build the same portable project state packet — the difference is where it lives and what wraps around it.

Agent Kit (local) — no account, state stays in your repo's .stateora/ folder, works offline, connects to your agent over MCP. Best when you want continuity inside the repo you're already in.
Hosted beta — sign in at /app, get a web dashboard with saved projects and generation history, and produce the three-part Stateora Pack (Project Memory Brief, Handoff Prompt, Verification Notes) from a browser. Best when you want an account-backed workspace, history across sessions, or read-only external access for another client.

They're companions, not competitors: export your Agent Kit .stateora state as a ZIP and import it into a hosted project from the State tab whenever you want the dashboard view of repo-local work. See the docs for the full hosted workflow.

Free Local limits (v0.1.0)

Free Local currently supports one active repo and up to five lifetime resets (stateora free-repo reset --confirm to move repos). It's entirely local — no upload, no cloud sync, no login required.

Not live in v0.1.0: login, licence keys and management, checkout, cloud sync, and account linking. Paid Pro, Team, and Enterprise access is planned for a later release — see pricing.

For saved projects, generation history, and the hosted three-part pack from a browser, use hosted beta.