CLI first

Govern agents. Right from your terminal.

Skep's CLI gives you complete control over tasks, runs, approvals, policies, and everything in between. Powerful, scriptable, local-first.

$skep chat View CLI docs

Tip: start the daemon in another terminal with skep serve

$ skep chat

Connected to Skep daemon at http://127.0.0.1:8765

You are in the command deck. Type /help for available commands.

skep > /help

Available commands:

/setupBind a repo

/reposRegistered repos

/workonSelect a repo

/policyEffective policy

/runsRecent runs

/stateRepo git state

/approvalsPending queue

/landLand a patch

skep >

Core commands

Everything you need to run, review, and control your workflows.

See the full CLI reference

skep run

Start a new supervised task.

skep run ~/code/app \
  "fix the failing test"

skep review

Inspect evidence, then approve.

skep review 7d31f9c2 --approve

skep chat

The terminal command deck.

skep chat --continue

skep serve

Local HTTP API + dashboard.

skep serve --port 8765

skep status

Runs, approvals, re-verify state.

skep status --personal --json

skep doctor

Readiness and sandbox probe.

skep doctor

skep setup

Create or update your profile.

skep setup --personal

skep template

Inspect learned templates.

skep template list

skep schedule

Recurring runs, dispatched by tick.

skep schedule add nightly ~/app \
  "run the lint fixer" --every 1d

The command deck

Deterministic operator commands the assistant's model never sees. Reads render immediately; mutations show a confirmation card, audited under actor operator-command.

/help

List the deck

/repos

Registered repos

/workon

Select a repository

/policy

Effective policy

/runs

Recent runs

/state

Repo git state

/approvals

Pending queue

/land

Land a patch · confirm

/setup

Bind a repo · confirm

/approve

Approve review · confirm

/deny

Deny review · confirm

/phase

Trust phase · confirm

A full workflow

Serve, chat, select a repo, run a task, check state, approve, land — all without leaving the terminal.

Scriptable

--oneshot sends one message, streams the reply, exits 0.

One store, two surfaces

Skip a card here, click it in the web UI. That's expected, not a leak.

Ctrl-C stops watching

It never stops the run itself.

a typical session

$ skep serve                        # start the daemon
$ skep chat                         # open the deck
skep > /workon ~/code/app          # select repository
skep > /run "add rate limiting"    # start a task
skep > /state                      # check current status
skep > /approvals                  # view pending gates
skep > /approve 7d31f9c2           # approve the review
skep > /land 7d31f9c2              # land the patch
skep > /runs 5                     # list recent runs

Options worth knowing

Use skep <command> --help for the exact parser output.

--execution-mode workspace|sandbox

Host-visible workspace execution, or the host sandbox backend.

--worker-cmd COMMAND

The worker adapter for this run. Or set SKEP_WORKER_CMD once.

--minimal

Start with empty network, env, shell, and git grants — learn through approvals.

--network DOMAIN

Allow one domain; repeatable. Omitted means deny all outbound.

--env-allow ENV

Pass one environment variable through the boundary; repeatable.

--no-template

Skip learned-template auto-match for this run.

--pr

On review --approve, open a GitHub pull request after applying.

--home HOME

Select the Skep state directory. Defaults to ~/.skep.

--minimal cannot be combined with --template, --network, or --env-allow.

The full power of Skep, in your terminal.

Script it, automate it, and make it yours.

$ pipx install skep Read CLI reference