Guides
One task each, start to finish
Each guide names who it is for and what you need first, gives the commands in order, shows what you should see, and lists what goes wrong and how to tell.
Unattended agents
Hand over a task and walk away
Written against the current release. Every command was run under a throwaway home before it was written down.
- Hand Claude Code or Codex a task and walk away At the end: A Claude Code or Codex run that happened inside the sandbox, re-verified with your test command, with its patch on a skep/<task_id> branch after your approval.
- Dispatch a run from cron or a script At the end: A wrapper script cron can call, with the agent’s credential supplied where cron has none, and exit codes you can act on.
- Pin the command that proves the work At the end: A project whose verify command is pinned, and the four re-verification results read from real output.
- Let confirmed runs land by themselves At the end: A project where a confirmed patch lands on a skep/* branch without your approval, and a list of what still stops it.
Set up and govern
First run, logins, and agents you run elsewhere
Task-shaped pages from the documentation.
- Onboarding: skep onboard At the end: A home with a model, a work directory, a sandbox choice, a locked policy baseline and a role, checked by skep onboard --check.
- Run skep as an always-on assistant on Ubuntu 24.04 At the end: An Ubuntu 24.04 server running skep at boot as a user service, under an account without sudo, with bubblewrap working and Telegram connected.
- Codex runs on a ChatGPT plan login At the end: A project whose Codex runs use your ChatGPT plan login, with the worker holding an access token and no refresh token.
- The policy enforcement hook At the end: Claude Code asking skep before it runs a shell command, writes a file or fetches a URL, with each verdict recorded.
- The ACP governor At the end: An ACP agent in another client whose permission requests skep answers from your policy.
- Skep in your pocket — the mobile story At the end: A messenger that can confirm the four low-risk action classes, and the knowledge of what stays in the web UI.
- Daily-driver setup: skep from your phone At the end: Telegram confirmations, research, video summaries and a daily mail summary set up, with skep doctor naming any step still undone.
Concepts and reference are in the documentation; every command is on the CLI page.