Documentation
Hand work to agents that keep working when you leave, and come back to what they did.
KeepState runs each agent session on its own durable machine, with your provider key. You work with your agents from one terminal app: they ask before they act, their results wait for you to review and apply, and a whole session can be saved, forked and restored. KeepState is not tied to one coding agent; Runners says which ones agent sessions run today.
Start here
curl -fsSL keepstate.ai/install.sh | sh
ks login
ks The last command opens the app; press n to start your first agent. Before you start lists what you need, and the quickstart goes step by step.
By task
- Hand an agent a bug and apply its changeset when you are satisfied.
- Decide what an agent may run: it asks, and waits for your answer.
- Leave and come back: the agent keeps working, and the app tells you what happened.
- Save, fork and restore a whole session, and let one agent consult another.
- Run a verified coding task: approve the repository checks, run Cruise, follow the verdict, and apply an accepted result.
- How sessions run: what leaves your machine, what never does, and where model calls go.
- Limits: what KeepState cannot do yet, with the evidence for each limit.
Reference
- CLI reference: all 114 commands in the released client, each in its terminal and in-app form.
- Slash commands: the app's own commands, its short forms, and how a ks command runs inside it.
- API: the customer API and its published contract.
- Troubleshooting: the next safe step when something does not work.
Reference pages are generated from the released client v0.1.26 and the product repository. Found an error? Tell us.