Initialize once
Detect the stack, import existing context files, and install the hooks that keep everything in sync.
This page shows the day-to-day flow: initialize a repo, save the current work when you stop, and use the rest of the commands only when you need them.
Keep the path obvious: set it up once, save when switching, and finish with a clean handoff.
Detect the stack, import existing context files, and install the hooks that keep everything in sync.
Capture task, branch, git state, dependency drift, and the latest decisions before you move to another AI tool.
Use the handoff and resume flow to pick up the same task with the next tool or the next session.
The point is not more commands. The point is that the next AI does not need the user to re-explain the repo.
`mindswap` captures task, branch, changes, and context when you switch away.
`resume` gives the next best action, so you can continue from the same point later.
`doctor` shows whether the project is initialized, current, and ready for the next session.
These are the commands the UI should keep surfaced as the CLI evolves.
The default save flow. Auto-detects the task, dependencies, and current state, then generates all handoff files.
defaultInitialize a project. Detect the stack, import any existing AI context, and set up hooks.
setupPower-user checkpoint with task, blocker, and next-step flags for explicit state capture.
power toolLog decisions and memory items. Conflicts are surfaced when the new note contradicts prior history.
memoryManage structured items directly: list, add, update, resolve, archive, or delete blockers and questions.
structured memoryRead the current task, branch, build/test state, and conflict status at a glance.
stateDiagnose setup, stale context, hook health, and continuity gaps with actionable output.
diagnosticsGenerate context files for one or more AI tools without overwriting the user's own content.
genMark the work complete, archive the task, and reset the repo to idle.
handoff closeClear the current task and checkpoint. Decisions are preserved unless you use full reset.
cleanupKeep HANDOFF.md fresh as the repo changes, or run a full save loop with `--save` and `--all`.
auto-syncSave, generate, and open another AI tool in one step.
tool switchProduce the session narrative with commits, decisions, conflicts, and useful stats.
session narrativeAsk a question and get cited answers from the repo's memory and history.
semantic queryEmit machine-readable workstream contracts so another agent can continue without re-reading everything.
handoff contractsPush or pull shared hub state, inspect sync health, and resolve conflicts across machines.
shared continuityValidate and regenerate MCP Registry metadata so the package and manifest stay aligned.
registry metadataRun a remote Streamable HTTP MCP endpoint for hosted and browser-based clients.
remote transportThese are the product-level details people usually miss when the UI is too dense.
Every branch can keep its own task, decisions, and checkpoint so context switches are reversible and intentional.
Blockers, questions, assumptions, and resolutions stay separate from plain decisions so the handoff stays readable.
Surface stale files, missing hooks, and weak continuity before a user discovers the problem during the next session.
Use cited matches from project memory and history instead of forcing the user to remember exact words.
Move state between machines with explicit conflict handling so the team can share a single source of truth.
Keep the MCP Registry manifest and the package metadata in sync.