* feat(cli): restyle chat input with horizontal rules and slim user bubbles Replace the tinted-background input field with a minimal frame: full-width horizontal rules above and below the textarea and a bold accent-colored prompt glyph, with no background fill. User message bubbles in the transcript match the new look: a slim neutral-gray bar with the same glyph, no vertical padding, and no mode-colored tint. Palette gains getInputRuleColor (neutral adaptive mid-gray for the rules) and getUserMessageBackground (neutral bubble tint), both built on a shared OKLAB lift helper extracted from getModeInputBackground. Home view's robot cursor-tracking offset is adjusted for the input's new left edge, and the spacer line between the chat input and status bar is removed. * feat(cli): replace cyan accent with new plan/act palette Swap the TUI accent colors: act mode goes from ANSI cyan to #79b8ff and plan mode from ANSI yellow to #ffea7f on dark themes. Light themes get counterparts derived in OKLCH with the same hue but darkened to hold >=4.5:1 contrast on white (#0f72cb act, #867100 plan), selected via the existing getModeAccent theme switch. All hardcoded "cyan" fg literals across dialogs, model selector, config view, and onboarding now reference palette.act so the accent is a single source of truth. The selection highlight follows the act color. The subliminal OKLAB chroma nudge on input backgrounds/foregrounds now leans blue (-a, -b) instead of cyan (-a, +b) to match the new accent hue. * feat(cli): soften success green and use act accent in markdown Swap the success/diff green from ANSI brightGreen and #22c55e to a muted sage #87af87 on dark themes (auto-approve banner, git diff +stats, diff view added-sign color); light themes keep the darker #116329 for contrast on white. Markdown prominent elements (headings, bold, list markers, links, table headers) now use the act accent via themePalette instead of hardcoded one-dark cyan #56b6c2. * feat(cli): harmonize dark syntax colors with brand accent palette Rebuild the dark syntax highlighting family around the brand anchors: functions use the act blue, strings and inline code use the success sage, types/italics use a dimmed plan yellow, and the remaining hues (keyword purple, variable coral, number orange, operator ice-blue) are regenerated in OKLCH at the same pastel lightness/chroma weight (~L 0.78, C 0.11) so code blocks read as part of the same palette. Light theme keeps its GitHub-light set. * fix(cli): brighten success green to match accent palette weight #87af87 sat at roughly half the OKLCH chroma of the act/plan anchors and read as gray next to them; #8bd28d (L 0.80, C 0.12) matches their weight. * fix(cli): brighten success green a step further (#99e89b) * feat(cli): polish status bar usage display and ClinePass model name - Cost always renders with two decimals ($0.00) instead of switching to four decimals under a cent; the turn summary line drops its three-decimal format for the same reason. - Token count next to the context bar is now just the number; the word 'tokens' was redundant with the bar right beside it. - Context window bar shrinks from 8 to 6 cells. - ClinePass models resolve their friendly models.dev name like every other provider and get a (ClinePass) suffix: 'GLM 5.2 (ClinePass)' instead of 'ClinePass/glm-5.2'. - ClinePass no longer shows '$0.00 (included with subscription)' -- cost is simply hidden for subscription providers. * fix(cli): place ClinePass suffix after reasoning effort in model name * fix(cli): format ClinePass model name as 'ClinePass: <model>' prefix * feat(cli): color transcript entries by the mode they were produced in (#12083) * feat(cli): color transcript entries by the mode they were produced in Previously the whole transcript retinted to the current mode's accent on every plan/act toggle. Entries now record the agent mode active when they were produced and keep that accent permanently, so a session reads as a visible history of plan (yellow) and act (blue) segments. How the mode is captured: - Live sessions: appendEntry in SessionProvider stamps entries from a uiMode ref, covering every creation site including mid-run switch_to_act_mode flips (which already call setUiMode through the runtime dialog bridge). - Resumed sessions: hydrateSessionMessages recovers the mode from the persisted <user_input mode="..."> wrappers via a new shared parseUserInputMode helper, and flips to act at switch_to_act_mode tool calls. Transcripts without wrappers stay unstamped and keep the current-mode fallback accent, matching the old behavior. - Restores: the /history resume and checkpoint-restore paths insert hydrated history via replaceEntries instead of appendEntry loops, so live-entry stamping cannot overwrite hydration's stamps (which would lock resumed transcripts to the resume-time accent). The load-bearing core fix: readPersistedMessagesFile stripped the user_input wrappers and mode notices from user text on every read ('display sanitization'). That read path also feeds session restarts (mode toggle, compaction-mode change, model change, fork, recovery), which re-persist what they read -- so every restart laundered the mode markers off disk and out of the model's seeded context, leaving nothing for hydration to recover. Reads now return persisted messages verbatim and formatting is the display surface's job: the CLI TUI, history titles, and the VS Code SDK history loader already formatted at their boundaries; the cline-hub webview history mapping and the CLI HTML export (which used normalizeUserInput and leaked mode_notice text) now do too. Connectors only surface assistant text, and the remaining readMessages consumers are programmatic (usage math, re-seeding, compaction input) where raw is correct. * fix(shared): match parseUserInputMode exactly to what the writer emits Drop the case-insensitive flag and the 'zen' value from the wrapper regex: formatUserInputBlock only ever writes lowercase act/plan/yolo, so anything else the parser accepted (uppercase look-alikes in adversarial content, a zen value with no writer) could never be real persisted data.
Cline CLI
Run Cline in your terminal. Interactive chat for paired sessions, or fully headless for CI/CD and scripting. The CLI shares its agent core with the Cline VS Code extension, JetBrains plugin, and SDK, so plan/act modes, MCP servers, checkpoints, rules, skills, and provider configuration all behave the same across surfaces.
Install
npm install -g cline
For nightly builds:
npm install -g cline@nightly
Platform binaries are published for macOS, Linux, and Windows on arm64 and x64. The cline package resolves the correct binary for your platform via optional dependencies, so no Node, Bun, or Zig runtime is required at install time.
Quick start
Run interactively:
cline
Run a single prompt:
cline "Audit this package and propose fixes"
Pipe input:
cat file.txt | cline "Summarize this"
See cline --help for the full flag reference.
Use any provider
Cline supports the same providers as the VS Code extension. You can sign in to Cline directly, use your ChatGPT Subscription through openai-codex, or bring an API key from Anthropic, OpenAI, Google Gemini, OpenRouter, AWS Bedrock, GCP Vertex, Cerebras, Groq, and any OpenAI-compatible endpoint.
cline auth # interactive sign-in
cline auth cline # OAuth sign-in
cline auth --provider anthropic --apikey sk-... --modelid claude-sonnet-4-6
cline auth without a provider opens the interactive auth setup TUI with the same options as the old CLI flow (Sign in with Cline, Sign in with ChatGPT Subscription, Sign in with OCA, or use your own API key).
OAuth-supported providers (cline, openai-codex, oca) do not auto-launch a browser on normal startup. Authenticate explicitly first with cline auth <provider>. For non-interactive runs, if an OAuth provider is selected and no saved credentials are available, cline fails fast with an authentication message instead of launching a hidden browser flow.
Modes
Cline CLI runs in a few different shapes depending on what you need:
- Interactive TUI:
clineorcline -iopens a full terminal UI with plan/act toggle, slash commands, file mentions, and live tool approvals - One-shot:
cline "your prompt"runs a single turn and exits - JSON:
cline --json "..."streams NDJSON events for piping into other tools - Yolo:
cline --yolo "..."skips approval prompts and exits when the turn finishes - Zen:
cline --zen "..."fires the task to the background hub daemon and exits immediately (see below)
Headless mode for CI/CD
Run Cline with zero interaction for scripting and automation. Pipe input, get JSON output, chain commands, integrate into CI/CD pipelines.
# One-shot prompt, auto-approve all tools
cline --yolo "Run tests and fix any failures"
# Pipe a diff in for review
git diff origin/main | cline "Review these changes for issues"
# NDJSON output for downstream tooling
cline --json "List all TODO comments" | jq -r 'select(.type == "agent_event" and .event.text) | .event.text'
Features
- Streaming TUI built on OpenTUI with markdown rendering, syntax-highlighted diffs, scrollable chat, and mouse support
- Plan/Act mode toggle for switching between planning and execution
- Native MCP support for connecting custom tools
- Checkpoints with
/undoto rewind workspace state - Sub-agent spawning and agent teams for parallel work
- OAuth login for Cline, ChatGPT Subscription (
openai-codex), and OCA - Configurable thinking budgets per run
- Cron and event-driven schedules for recurring agent work
- Chat connectors for Telegram, Google Chat, and WhatsApp
Usage
# Start Cline CLI without a prompt to enter interactive mode
cline
# Single prompt (one-shot) - includes tools, spawn, and teams
cline "Audit this package and propose fixes"
# Interactive mode with a starting prompt
cline -i "Let's work on this together. First, analyze the current state."
# With a custom system prompt
cline -i -s "You are a pirate" "Tell me about the sea"
# Require approval before each tool call
cline --auto-approve false "Inspect and modify this repository"
# Explicit yolo: enables submit_and_exit and disables spawn/team tools by default
cline --yolo --retries 5 "Refactor this package"
# Override consecutive internal mistake (retry) limit (default: 3)
cline --retries 5 "Fix failing tests"
# Team workflow with persistent name
cline --team-name my-team "Plan, implement, and verify release checklist"
cline --team-name my-team "Continue yesterday's team workflow"
# Show verbose run stats (elapsed time, tokens, estimated cost when available)
cline -v "Explain quantum computing"
# Use a specific provider, model, and access token for a single prompt
cline -P openrouter -m google/gemini-3-pro -k sk-... "Set up a storybook"
# Use a different model with the last used provider
cline -m anthropic/claude-opus-4-6 "Explain string theory"
# Stream structured NDJSON output
cline --json "Summarize this repository"
# Quick provider setup
cline auth --provider anthropic --apikey sk-... --modelid claude-sonnet-4-6
cline auth --provider openai-native --apikey sk-... --modelid gpt-5 --baseurl https://api.example.com/v1
MCP servers
Manage MCP servers with the interactive wizard:
cline mcp
cline config mcp
Open the add-server wizard with the name, transport, and command or URL already filled in with cline mcp install (cline mcp add also works). Stdio servers use everything after -- as the command and arguments:
cline mcp install fs -- npx -y @modelcontextprotocol/server-filesystem /tmp
Remote HTTP and SSE servers take a name, transport, and URL. The wizard still asks for auth details before saving:
cline mcp install ctx7 --transport http https://mcp.context7.com/mcp
cline mcp install events --transport sse https://example.com/sse
Because this command opens the wizard, it requires a TTY.
Connectors
Bridge a chat surface into RPC-backed Cline sessions. Each conversation thread maps to a session with full context. Supported platforms: Telegram, Slack, Google Chat, WhatsApp, and Linear.
# Telegram (polling mode)
cline connect telegram -k 123456:ABCDEF...
# Slack (webhook mode)
cline connect slack --bot-token $SLACK_BOT_TOKEN --signing-secret $SLACK_SIGNING_SECRET --base-url https://your-domain.com
# Slack (socket mode)
cline connect slack --bot-token $SLACK_BOT_TOKEN --app-token $SLACK_APP_TOKEN
# Google Chat (webhook mode)
cline connect gchat --base-url https://your-domain.com
# WhatsApp (webhook mode)
cline connect whatsapp --base-url https://your-domain.com
# Linear (webhook mode)
cline connect linear --api-key $LINEAR_API_KEY --base-url https://your-domain.com
# Stop connector bridges and delete their sessions
cline connect --stop
cline connect --stop telegram
In chat surfaces, connector slash commands include /help, /start, /new, /clear, /whereami, /tools, /yolo, /cwd <path>, /schedule, /abort, and /exit. Run cline connect <adapter> --help to see the full flag list for any adapter.
Schedules
Schedule agents on cron-like intervals or external events.
cline schedule create "Daily code review" \
--cron "0 9 * * MON-FRI" \
--prompt "Review PRs opened yesterday and summarize issues." \
--workspace /path/to/repo \
--provider cline \
--model openai/gpt-5.3-codex \
--timeout 3600 \
--tags automation,review
cline schedule list
cline schedule get <schedule-id>
cline schedule trigger <schedule-id>
cline schedule history <schedule-id> --limit 20
cline schedule export <schedule-id> > daily-review.yaml
cline schedule import ./daily-review.yaml
Schedules can route results back to chat surfaces with --delivery-adapter, --delivery-bot, and --delivery-thread.
Options
| Flag | Description |
|---|---|
-s, --system <prompt> |
Override the system prompt |
-P, --provider <id> |
Provider id (default: cline) |
-m, --model <id> |
Model id (default: anthropic/claude-sonnet-4.6) |
-k, --key <api-key> |
API key override for this run |
-p, --plan |
Run in plan mode (default is act mode) |
-i, --tui |
Interactive TUI multi-turn mode |
-t, --timeout <seconds> |
Optional run timeout in seconds |
-c, --cwd <path> |
Working directory for tools |
--config <path> |
Configuration directory (used for CLI home resolution) |
--hooks-dir <path> |
Additional hooks directory hint for runtime hook injection |
--acp |
ACP (Agent Client Protocol) mode |
--thinking [none|low|medium|high|xhigh] |
Model thinking level when supported. Defaults to medium when the flag is provided without a level; thinking is off when the flag is omitted. |
--compaction <agentic|basic|off> |
Context compaction mode. Defaults to basic; use agentic for LLM compaction or off to disable. |
--retries <count> |
Maximum consecutive mistakes (retries) before halting (default: 3) |
--json |
Output NDJSON instead of styled text |
--data-dir <path> |
Use isolated local state at <path> instead of ~/.cline (enables sandbox mode automatically) |
--auto-approve [true|false] |
Set tool auto-approval for all tools |
--kanban |
Run the external kanban app |
-y, --yolo |
Skip tool approval prompts, enable submit_and_exit, and disable spawn/team tools by default |
-z, --zen |
Dispatch the task to the background hub and exit the CLI immediately |
--team-name <name> |
Override the runtime team state name |
-h, --help |
Show help and exit |
-v, --verbose |
Show verbose runtime diagnostics |
-V, --version |
Show version and exit |
--json is non-interactive and requires either a prompt argument or piped stdin. --key takes precedence over environment variables.
Top-level commands
cline config- Open the interactive config viewcline history|h [options]- List session history or manage saved sessionscline version- Show CLI versioncline update [options]- Check for CLI and kanban updatescline auth <provider>- Authenticate or seed provider credentialscline connect <adapter>- Run a chat connector bridge (telegram,gchat,whatsapp)cline connect --stop [adapter]- Stop connector bridge processes and their sessionscline schedule <command>- Create and manage scheduled runscline doctor- Inspect local CLI health and stale processescline doctor fix- Kill stale local RPC listeners and old CLI processescline doctor log- Open the CLI runtime log filecline hook- Handle a hook payload from stdincline hub- Manage the local hub daemoncline kanban- Run the externalkanbanapp, installing it first when needed
Zen mode
--zen (alias -z) runs a task in the background hub daemon and exits the CLI immediately. It is intended for long-running tasks you want to fire off and walk away from.
cline --zen "Refactor the authentication module and add unit tests"
Behavior:
- The CLI starts (or reuses) the local hub daemon, submits the task, then exits. It does not stream output or stay attached to the session.
- Because there is no human in the loop once the CLI exits, zen sessions run with full tool auto-approval (same semantics as
--yolo).spawn/teamtools are disabled by default for safety, consistent with yolo-mode defaults. - If the Cline menubar app is running, it subscribes to hub
ui.notifyevents and will surface a system notification when the task completes. - If the menubar app is not running, there is no live UI for the task. Use
cline historylater to find the session and inspect the result. --zenis incompatible with--data-dir(the implicit sandbox requires a local backend that exits with the CLI) and with--tui(there is no terminal UI to render into).
Tool approval
Tool calls are auto-approved by default. Use --auto-approve false to require review before tool execution.
cline --auto-approve false "Inspect and modify this repository"
When approval is required, the CLI prompts in TTY mode:
Approve tool "<tool_name>" with input <preview>? [y/N]
- Enter
yoryesto approve. - Enter anything else (or press Enter) to reject.
- If stdin/stdout is not a TTY, required-approval calls are denied in terminal mode.
Desktop-integrated approval mode is also supported via env wiring (CLINE_TOOL_APPROVAL_MODE=desktop and CLINE_TOOL_APPROVAL_DIR=<path>). In desktop mode, CLI writes a request JSON file and waits for a matching decision JSON file.
Environment variables
ANTHROPIC_API_KEY- API key for AnthropicCLINE_API_KEY- API key for Cline (when using-P cline)OPENAI_API_KEY- API key for OpenAI (when using-P openai)OPENROUTER_API_KEY- API key for OpenRouter (when using-P openrouter)AI_GATEWAY_API_KEY- API key for Vercel AI Gateway (when using-P vercel-ai-gateway)V0_API_KEY- API key for v0 (when using-P v0)CLINE_DATA_DIR- Base data directory for sessions/settings/teams/hooksCLINE_SANDBOX- Set to1to force sandbox modeCLINE_SANDBOX_DATA_DIR- Override sandbox state directoryCLINE_TEAM_DATA_DIR- Override team persistence directoryCLINE_BUILD_ENV- Runtime build mode for SDK-owned subprocess launchesCLINE_DEBUG_HOST- Host for development inspector listeners (default127.0.0.1)CLINE_DEBUG_PORT_BASE- Base inspector port for development child processesCLINE_TOOL_APPROVAL_MODE- Approval mode (desktopuses file IPC; unset uses terminal prompt)CLINE_TOOL_APPROVAL_DIR- Directory for desktop approval request/decision filesCLINE_LOG_ENABLED- Set to0/falseto disable runtime file loggingCLINE_LOG_LEVEL- Runtime log level (trace|debug|info|warn|error|fatal|silent, defaultinfo)CLINE_LOG_PATH- Runtime log file path (default<CLINE_DATA_DIR>/logs/cline.log)CLINE_LOG_NAME- Logger name embedded in runtime log records
--key takes precedence over environment variables.
Contributing
See DEVELOPMENT.md for local development setup, monorepo structure, and TUI architecture. See DISTRIBUTION.md for how the CLI is packaged and distributed.