Versioned goals
Lifecycle, criteria, and constraints. Completion stays blocked until required evidence is present and subgoals and conflicts are resolved.
Momentum is a continuity layer for long-horizon agents: versioned goals, typed memory, atomic checkpoints, and a verified resume.
See the continuity modelSynthetic fixture · not live agent state
Verified resume
The core validates every change against the expected stream version before writing it in one transaction. On restart, a verified ResumeBundle loads the goal, visible memory, open conflicts, drift, and an optional checkpoint. Missing or changed hashes raise an integrity error.
Momentum
Momentum keeps continuity in four parts: versioned goals, typed memory, atomic checkpoints, and a verified resume.
Track changes with a versioned goal.
Keep working, episodic, semantic, and procedural memory.
Save progress and state together in one transaction.
Check integrity before loading the ResumeBundle.
prepare-release
Each accepted change checks the expected stream version, then writes the result in one transaction.A ResumeBundle loads the goal, visible memory, open conflicts, declared drift (allow, warn, or block), and an optional checkpoint. A hash mismatch raises an integrity error.
Keep the harness you already use. Connect it to Momentum through local MCP.
Ask for a previewThird-party product names are used for identification only. No affiliation or endorsement is implied.
Continue to the demo
Momentum interface demo. The interface may change between versions. Codex and GPT-5.6 Sol are trademarks of OpenAI Group PBC. Cloudflare and Cloudflare Workers are trademarks and/or registered trademarks of Cloudflare, Inc. in the United States and other jurisdictions. Other names and marks belong to their respective owners. TACTICO is independent and is not affiliated with, sponsored by, supported by, or endorsed by OpenAI Group PBC or Cloudflare.
One committed stream
Lifecycle, criteria, and constraints. Completion stays blocked until required evidence is present and subgoals and conflicts are resolved.
Working, episodic, semantic, and procedural records. Each record is shared or private, with supersession and conflicts recorded explicitly.
Progress, working state, memory writes, and a state hash in one commit. Resume checks those hashes before loading the snapshot.
A ResumeBundle with a hash-based manifest. Missing or changed checkpoint data raises an integrity error.
Hard-rule checks on a supplied action snapshot. Each allow, warn, or block result is recorded and remains part of the history.
Surfaces
The same continuity contract is available through a local MCP for agents and a labelled Console fixture for operators. Hosted surfaces are still unavailable.
Local stdio over SQLite, identity bound at process start, twenty-one typed tools, and zero product telemetry. Hosted MCP has not shipped.
A continuity map, a cockpit for the next safe action, and an evidence inspector. The browser fixture is a labelled demonstration with no authenticated account.
Local stdio tools over the same SQLite-backed core. No hosted Momentum endpoint.
A labelled local operator workspace demonstration. It does not connect to a live account.
Manage workspace goals and memory from the terminal. Not generally available.
A typed client for the same local contract. Not currently a public package.
Goals, memory, and checkpoints stay in the local SQLite store you control. Momentum keeps Pathways walks and Ionic contracts out of hosted storage, and the Console makes no browser calls to a Tactico API.
You choose the goalMomentum resumes what you checkpoint. You set the objectives and decide which tools to run.
It stays localGoals, memory, and checkpoints remain on your machine. There is no hosted continuity service.
Both options open a pre-filled email. Send it to submit your request.