Skip to main content

Maintain your Momentum as you build.

Ask for accessFor teams
The Momentum workspace: session rail, transcript with a bound goal, composer, and the goal inspector

Start to done, across pauses and runtimes.

  1. 01

    Start a durable goal

    Tell the agent what done means. The goal binds to the session itself.

    You describe what done means; Momentum records the goal binding: goal v1 · stream 1
  2. 02

    Pause. Walk away.

    Hit pause mid-turn. The checkpoint holds the reasoning.

    The composer mid-turn on Codex · GPT-6 Astra, with the pause button
  3. 03

    Switch harness

    Pick another runtime. The goal, memory, and evidence travel with it.

    The composer capability menu with Grok CLI · Grok 4.7 selectedNew harness acknowledged: GPT-6 Astra to Grok 4.7, continuity record kept
  4. 04

    Come back. It waited.

    Open the session tomorrow. The goal, its criteria, and open conflicts are still there.

    The goal card: 1/3 criteria closed, sub-goals completed, active, and blocked
  5. 05

    Done: on record.

    Completion needs the criteria satisfied. The record keeps what happened.

    The goal card, completed: 3/3 criteria satisfiedMomentum Core record: goal completed, 3/3 criteria satisfied

Momentum interface demo. The interface may change between versions. Claude and Claude Code are trademarks of Anthropic, PBC. Codex and GPT-6 Astra are trademarks of OpenAI Group PBC. Grok, Grok CLI, and Grok Build are trademarks of X.AI Corp. Gemini and Antigravity are trademarks of Google LLC. Cursor is a trademark of Anysphere, Inc. OpenCode, Pi, Cline, Windsurf, Trae, and other names and marks belong to their respective owners. TACTICO is independent and is not affiliated with, sponsored by, supported by, or endorsed by any of these companies.

No vendor lock-in.

The goal binds to the session itself: swap the harness or the model mid-flight.

Connect it with your agents via MCP&ACP.

Your work stays on your machine.

Goals, memory, and checkpoints live in a local store you control. We don't process or retain any of it on our end.

Harnesses like Claude Code or Codex talk to their own model providers. That traffic is between you and the provider under their terms.

Use Cases

Multi-day builds

  • Goals persist across restarts
  • Criteria define what done means
  • Pick up where the agent left off
A durable goal card: criteria and sub-goal statesSee it in the story

Harness switching

  • Change runtime or model mid-session
  • Memory follows the session
  • No re-briefing the new agent
The composer capability menu choosing a harness and modelSee it in the story

Work you can audit

  • Every step lands on the record
  • Conflicts stay open until resolved
  • Handoffs carry their evidence
The Core record entry confirming a completed goalSee it in the story

Build with Momentum

Talk to us

Questions

What is Momentum?

Local archive-and-resume infrastructure for agents: versioned goals, typed memory, and atomic SQLite checkpoints, so work continues after disconnects, restarts, or a full context window.

Which agent harnesses does it attach to?

Momentum attaches to existing harnesses such as Claude Code or Codex over local MCP, binding continuity to the session itself.

Where is my data stored?

Goals, memory, and checkpoints live in a local store you control. We do not process or retain any of it on our end.

Is there a hosted version?

Momentum Cloud (a self-hosted enterprise console) and Momentum Enterprise (priority support and fleet licensing) are coming soon and not generally available.

Ask for Momentum access.

Ask for previewWishlist

Both options open a pre-filled email. Send it to submit your request.

Momentum EnterpriseMomentum Cloud