Skip to content
last verified against v0.1.26 verified 2026-10-16

Slash commands

In an agent's window, a line that starts with / is a command, not a message to the agent. Generated from the released client (v0.1.19).

Window commands

CommandWhat it does
/helpwhat the window's keys and commands do
/statusthe agent's full state, as the service states it
/taketake control of the agent from another window
/switch <agent> [session]open another of your agents without going home; two agents of one name are listed, never chosen between
/home (also /back)back to your agents; this agent keeps working
/quit (also /exit)leave the app; your agents keep working

Short forms

Each runs one ks command. Anything after it is passed on: /diff <result> runs ks result diff <result>.

TypeRunsWhat it does
/stopks agent stopstop an agent: its instruction in flight is asked to stop and its queue is held; the session keeps running
/pauseks agent pausesave the session an agent lives in and park it, waiting until it is parked
/resumeks agent resumeresume the parked session an agent lives in, waiting out a save that is still completing
/queueks agent queue showwhy an agent's queue is not moving: what blocks it, what waits behind it, what each choice would do
/tasksks task listthe instructions of a session's agents, in the order they were committed
/resultsks result listthe results of one task, or of a session's tasks: name, size, sha256, task, verification
/approvalsks approval lista session's permission requests with the instruction each was asked for, what it touches and what deciding costs
/advisersks adviser listan agent's adviser connections, live, revoked and expired, in both directions
/usageks session usagea session's model use, runtime and storage, apart, with units, source and whether each figure is actual, estimated or unavailable
/keysks key listyour keys: id, provider, alias, last four characters, enabled or disabled
/logsks agent logsthe session's setup log and its agent's log from a cursor, safe to print; --follow polls until the service says it ends
/agentsks agent listthe agents of a session: name, id, activity, role, current task
/checkpointsks session checkpointsthe saved points a restore or a fork may name: whether each is usable now and its position, boundary, state, scope and manifest identity
/restoreks session restorerestore a session from a named saved point, and say exactly what continues from it
/diffks result diffwhat an attempt's ks-changeset.json says it changed, against its recorded base, with every path escaped
/applyks result applyapply an attempt's changeset to this project, only onto the recorded base, transactionally

Two names are taken by a short form: /resume is ks agent resume (type /wake for a plain session), and /logs and /apply are the agent's (type /cruise logs and /cruise apply in full).

Every ks command

Type any ks command after /, with the same arguments and options: /session checkpoints, /result download <result>, /cruise status --watch. Tab completes a command's name, and lists the candidates when several fit. The CLI reference gives every command with its "In the app" form.

Commands the window does not run

The window refuses these 4 and says why:

CommandWhy
/agent openyou are in the agent's window already; /home, then Enter, opens another
/attachit takes over the terminal itself: run ks attach outside the app
/loginsigning in opens a browser: run ks login outside the app
/logoutit removes the sign-in the app is using: run ks logout outside the app

How a / command runs

  • It is the command itself. The window runs the same ks binary with the same arguments; its output appears in the conversation under a $ ks … line that shows exactly what ran.
  • The window's context is filled in. A command that takes --session gets this session. A session argument you leave out is this session. On an agent command, an agent you leave out is this agent: /agent tell "run the tests" tells this agent. --agent gets this agent when the command runs on this session. A new name, as in /agent create, is never filled in.
  • Nothing prompts. A command runs with --no-input: a step that needs a confirmation refuses and names the flag to pass (see Confirmations). It gets no standard input, so ks key add runs in a terminal outside the app.
  • Ctrl-C stops it. While a command runs, Ctrl-C stops that command, not the window and not the agent.

Spotted an error on this page? Tell us, and we will correct it.

Report it
← previous Interactive mode next → Agents, tasks and results