mcue closeoutClose out a session
Capture what you meant to do, what happened, blockers, the next action, and the exact resume pointer.
local-first operating state
mcue keeps the operating state of your work on a local device and in reach of your agents.
Close out a session, resume with bounded context, and give agents the same state through MCP. Core is Apache-2.0, works offline, and needs no account.
$
mcue init payments-apiregister a project, anchored to this directory$
mcue closeout payments-apicapture intent, outcome, next action, and resume pointer$
mcue resume payments-apire-enter with a bounded context packet$
mcue hub set https://api.mcue.devoptional — choose a Hub endpoint$
mcue loginoptional — connect Core to Hub$
mcue publish payments-apioptional — keep this project reachable$
mcue sync payments-apioptional — exchange accepted operationsThe Hub commands are optional. They publish a project so its accepted state remains reachable while local devices are offline.
01 — CORE LOOP
Four moves, and none of them need a server.
The loop runs entirely on disk. Everything after this section is optional.
mcue resumeResume with bounded context
A packet capped at 300 or 1000 tokens: enough to re-enter, small enough to hand to an agent.
ls ~/.mcueKeep state legible on disk
Markdown with YAML front matter under $MCUE_HOME. Diffable, greppable, and editable.
mcue serve --mcpGive agents the same state
The local MCP server exposes the same validated read and write surface as the CLI.
02 — TRUST MODEL
Local-first is a boundary, not a feature flag.
Core makes no network request unless you run mcue login.
No account for Core
The full local product works before you sign in to anything.
Works offline
Core makes no network request until you explicitly run mcue login.
Human-readable state
Markdown and YAML you can inspect, diff, and repair by hand.
Git still owns source
mcue holds operating state. Your code stays where it is.
Apache-2.0
Permissive open-source licensing, including the patent grant.
~/.mcue/registry/projects.yaml · projects/<id>/lanes/<lane>/lane_state.md · checkpoints/<timestamp>.md
Inspectable state. Git keeps owning your source.
Inspectable state. Git keeps owning your source.
03 — HUB CONTINUITY
optionalinvite-only alphaproprietary hosted service
Take the computer offline. The state stays reachable.
Publish privately, connect the hosted MCP endpoint once, then let agents continue against accepted state while every local device is offline.
Publish privately
mcue publish creates a private Hub project.
Connect MCP once
Use one persistent endpoint, read-only until elevated.
Take local devices offline
No tunnel or local daemon remains online.
Continue through MCP
Agents use accepted state through Hub.
Reconnect and exchange
Core applies ordered operations and replays pending local work.
Your operating state, locally.
- CLI and local MCP
- Offline operation
- Full state model and reconciliation
- BYO-S3 remote path
- Open source · Apache-2.0
Optional managed continuity.
- Accepted event ordering
- Persistent hosted MCP
- Device and client controls
- Explicit project publishing
- Private · invite-only alpha
04 — OFFLINE CONTINUITY
One endpoint. Four explicit states.
Colour is never the only signal. Sequence, cursor, and pending count stay visible.
local device online
Local and hosted MCP are reachable. Cursor #1843 · pending 0.
local device offline
The computer is genuinely off. Local MCP is unavailable.
hosted mcp active
Agents keep reading and writing accepted state through Hub.
synchronized
Core pulls #1844–#1846 in order; provenance survives.
Streamable HTTP endpoint
https://api.mcue.dev/mcp05 — INSTALL
Core first. Hub only when you need continuity.
Start locally in under a minute. Publishing remains a separate, explicit action.
package manager · recommended
Homebrew
brew install ck46/tap/mcueGo 1.25+
Go toolchain
go install github.com/ck46/mcue/cmd/mcue@latest
the cue to resume
Install Core