Start an interactive session:
kit
Run a one-off prompt:
kit "List files in src/"
Attach files as context using the @ prefix:
kit @main.go @test.go "Review these files"
Binary files (images, audio, PDFs) are automatically detected via MIME type and sent as multimodal attachments. You can also reference MCP resources:
kit @mcp:myserver:file:///data/report.csv "Summarize this data"
Use a specific model:
kit --model anthropic/claude-sonnet-latest
Kit can run as a non-interactive tool for scripting and automation.
Get JSON output:
kit "Explain main.go" --json
Quiet mode (final response only, no TUI):
kit "Run tests" --quiet
Ephemeral mode (no session file created):
kit "Quick question" --no-session
The standard CLI/TUI and non-interactive runs execute enabled tool calls without
a built-in per-call approval prompt by default. Shell commands run with the
process account’s permissions. The write and edit tools can change files without
using the shell. Custom extensions and SDK hooks can block calls. --quiet,
--json, and --no-session do not add isolation or approval.
Repository files, fetched content, MCP results, and issue/PR text can influence model instructions. With untrusted input, use a dedicated restricted account or an isolated runtime. Limit filesystem mounts and network access, and provide only the credentials needed for the task. A working directory is not a filesystem access boundary. Kit does not automatically provide an OS sandbox.
ACP server mode is an exception: its default approval
mode is ask, subject to read-only tool exemptions and remembered session
decisions. Approval prompts are not an OS sandbox or a complete defense against
malicious input. This guidance does not add a gate that blocks destructive
commands.
Continue the most recent session for the current directory:
kit --continue
# or
kit -c
Pick from previous sessions interactively:
kit --resume
# or
kit -r
Kit can run as an ACP (Agent Client Protocol) agent server, enabling ACP-compatible clients (such as OpenCode) to drive Kit as a remote coding agent over stdio:
# Start Kit as an ACP server (JSON-RPC 2.0 on stdin/stdout)
kit acp
# With debug logging to stderr
kit acp --debug
The ACP server exposes Kit’s full capabilities — LLM execution, tool calls (shell, read, write, edit, grep, etc.), and session persistence — over the standard ACP protocol.