Everyday Usage

Run it with no subcommand to enter an interactive session, one line per turn:

klaus

Keys and slash commands inside a session: /help lists them all; /model <id> and /mode <mode> switch the model or the permission mode starting from the next turn; /config model=... mode=... changes both at once and reports the values that actually took effect; /exit or ctrl-d leaves. ctrl-c interrupts the turn currently running, and pressing it twice at an empty prompt exits. A line typed while a turn is in progress is fed into that turn (steering) rather than queued for the next one.

The run-and-exit form reflects the outcome in its exit code, so it can be piped straight into a script:

klaus exec "split this function up"

Other common subcommands:

• klaus ask <question>: asks once without writing to the session history — good for looking things up.
• klaus review: reviews code. By default it reviews the uncommitted changes in the workspace, but it can also review against a baseline branch, a commit, specified files, or a free-form instruction, producing structured findings with locations.
• klaus mcp: manages MCP servers, and can also invoke a named tool directly, read a resource, or fetch a server-provided prompt template without going through the model — useful for verifying whether a server actually works and whether the arguments are right.
• klaus session, klaus history, klaus rewind, klaus compact: list sessions, view history, rewind a number of turns (optionally rewinding file changes too), and compact the context.
• klaus cost, klaus context: how much this session has cost, and how much of the context window is in use.
• klaus skill, klaus plugin, klaus agent, klaus hook, klaus memory, klaus task: command-line entry points matching each of Klaus's settings pages.
• klaus engine: endpoint-level things — config files, hook files, persistent permission rules, credentials. These do not belong to any single session, so this group of commands does not open one (reading configuration should not depend on a session that is configured by that configuration).
• klaus capabilities, klaus extensions: for troubleshooting — the runtime capabilities actually resolved for the current session, and the extension graph actually in effect (skills, sub-agents, hooks, MCP).
• klaus completion <shell>: generates a shell completion script.