SStateora
Get started

Hosted beta guide

How Stateora works

Stateora is the continuity layer for AI coding tools. It packages your project's decisions, blockers, context, and progress into a portable project state packet — a Stateora Pack — so your next AI tool can pick up where the last one left off instead of starting cold. This guide covers the live hosted beta workflow and the local Agent Kit path.

Use it when you're switching AI tools mid-project, handing a repo to another agent, or picking work back up after a break — anywhere the same context would otherwise need to be re-explained.

What Stateora does

Stateora reads your saved project state — summary, decisions, blockers, and receipts — and turns it into a Stateora Pack: a handoff pack plus a routed next-agent prompt. In the hosted beta you get:

  • Saved projects and generation history in your account
  • A three-part Stateora Pack — Project Memory Brief, Handoff Prompt, and Verification Notes
  • Optional read-only external access for tools like Codex via scoped client credentials

During private beta, every signed-in user receives the full pack output. Plan tiers, checkout, and licence keys are not enforced yet.

Hosted beta workflow

  1. Create an account at /sign-up and open /app.
  2. Create or import a project. Start empty from the dashboard, or import a .stateora ZIP from the project State tab (Agent Kit export with .stateora/state.json).
  3. Edit project state. Update summary, goal, current state, decisions, blockers, and receipts on the State tab. Changes save to your hosted project.
  4. Generate a pack. Open the Generate tab to produce the Project Memory Brief, Handoff Prompt, and Verification Notes from saved state.
  5. Copy or download. After a successful generation, copy individual sections or download the handoff pack as a Markdown file for your next AI tool.

Using Agent Kit locally

The local Agent Kit CLI and MCP run in your repository without a Stateora account. Install with npx stateora init and use it for local-first receipts, rescue flows, and repo tooling.

Use local Agent Kit when you want continuity inside the repo, no account required. Use hosted beta when you want saved projects, generation history, and remote context access from external clients. Both paths build the same portable project state packet — you can export from Agent Kit and import into a hosted project.

External client credentials

On project Settings, you can create a credential scoped to that project. Credentials are read-only, expire after up to 30 days, and are shown once at creation — store them securely.

Use a credential to let a target tool such as Codex read working context directly, via GET /api/external/context or the hosted MCP server at POST /api/mcp. This is a scoped, read-only connection you set up yourself — not an official vendor integration.

Beta limitations

This is an early private beta. Pack generation quality varies with how much project context you save, and heuristic tool routing is a best guess, not a guarantee. Paid checkout, licence keys, cloud sync between hosted and local, repo upload, team collaboration, and official vendor integrations are planned but not live — see pricing for the current beta-versus-planned breakdown.

Related pages

  • Sample handoff — static example of the three-part pack output.
  • Pricing — intended plans; checkout and tier enforcement are not live during beta.
  • Agent Kit — local CLI and MCP for repo-first workflows.
  • Try hosted beta — sign in and start a hosted project.