Files and commits
The result is a tree of work on real branches, docked beside the conversation.
Momentum
Memory Layer
Goals, memory and checkpoints that stay with the work, not the provider.
Real interface, illustrative session. Momentum is in development.1
The goal is the anchor.
A title, criteria and constraints define the work. The session keeps them when the harness changes.
A record you can inspect.
Ledger
Project backendConnected
Core checkpoints
Runtimes
codexConnected
Runtime details
- Connection fingerprint
- -
- Generation
- -
- Models
- -
- Models fingerprint
- -
- Catalog observation
- -
- Catalog revision
- -
- Catalog observed
- -
- Lease renewed
- -
Catalog observations describe this harness connection. Lease renewal does not refresh its catalog.
claude codeConnected
Runtime details
- Connection fingerprint
- -
- Generation
- -
- Models
- -
- Models fingerprint
- -
- Catalog observation
- -
- Catalog revision
- -
- Catalog observed
- -
- Lease renewed
- -
Catalog observations describe this harness connection. Lease renewal does not refresh its catalog.
grok buildNot connected
Runtime details
- Connection fingerprint
- -
- Generation
- -
- Models
- -
- Models fingerprint
- -
- Catalog observation
- -
- Catalog revision
- -
- Catalog observed
- -
- Lease renewed
- -
Catalog observations describe this harness connection. Lease renewal does not refresh its catalog.
Turn receipts
- claude codeDone
turn_c1f7e9a4 - codexDone
turn_3f9a1c20
Recent app notices
No app notices.
Receipts across the handoff
See which harness ran each turn and how it ended. Changing agents doesn’t erase the record.
Local memory.
Your provider.
Goals, memory and checkpoints live in a local store you control. Inspect recorded memory and export it as JSON.
Harnesses still connect to their own model providers under those providers’ terms. Momentum does not transfer subscriptions, authentication or provider permissions.