Skip to content
Lime

Non-interactive use

Lime exposes several non-interactive surfaces. Each is suited to a different shape of automation.

Run a slash command against a saved session

Terminal window
lime --resume latest /status
lime --resume latest /commit
lime --resume <session-id> /pr
lime --resume path/to/session.jsonl /memory

Trailing tokens after --resume must be slash commands. If no session reference is given, latest is implied. Only commands marked [resume] in /help are valid here — interactive-only commands return a clear error pointing you at the correct invocation.

Snapshot subcommands

These print structured information and exit. They do not require an existing session.

Terminal window
lime status              # session + model + provider + workspace snapshot
lime sandbox             # sandbox isolation snapshot
lime version             # version + build info
lime system-prompt       # render the resolved system prompt for the cwd
lime bootstrap-plan      # print the bootstrap-phase skeleton
lime agents              # list configured agents
lime skills              # list discovered skills

lime system-prompt accepts --cwd PATH and --date YYYY-MM-DD to inspect what the system prompt would look like for a different working directory or date.

Configuration & resource management

Terminal window
lime init                      # bootstrap repo-local Lime files
lime login [...]               # store credentials (see Installation)
lime logout [...]              # clear credentials
lime model list|add|rm         # manage user entries in ~/.lime/models.json
lime command list|create|...   # manage user-scope custom slash commands
lime mcp list|add|...          # manage MCP servers
lime remote pair|devices|...   # manage remote-control devices

Bridge mode (programmatic)

For deeper integration, run the JSON-RPC 2.0 bridge directly:

Terminal window
# stdio (one client per process — VS Code uses this)
lime bridge


# WebSocket (bound to 127.0.0.1, bearer-token gated)
lime bridge --ws --ws-port 9111 --ws-token "$(openssl rand -hex 32)"


# WebSocket with device-registry auth
lime bridge --ws --device-auth


# Inspect a registered bridge engine
lime bridge --status

The bridge protocol surface includes initialize, session.create / list / continue / fork / compact, turn.send / cancel, permission.respond, slash.list, and shutdown, plus push notifications (runtime.event, turn.completed, session.created, permission.request).

This is the same protocol the VS Code extension and the Web companion (PWA) speak. Use it directly when you want to embed Lime in another tool.

Structured JSON output

Lime can constrain a turn’s output to a JSON Schema with --output-schema:

Terminal window
lime --output-schema ./schema.json --resume latest /…

See Structured output for the full pattern.

What’s intentionally not in this list

  • There is no --output-format flag. The CLI parser explicitly rejects it.
  • There is no --print / -p shortcut.
  • There is no lime prompt "…" subcommand.
  • Plain lime "some prompt" is not a one-shot — unrecognized first arguments raise unknown subcommand.

If you need a one-shot prompt-and-exit flow, use the bridge with a custom client, or open a session and drive it with --resume plus a slash command.