![\"Cockpit\"](\"public/banner-dark.png\")
\n \n \n
A web UI for Claude Code that frees it from your terminal.
\n\n## Why\n\nClaude Code is great. It's also a terminal app. One window, one machine, foreground only. Cockpit runs the same engine as a server: sessions live on the server, the browser is just a viewer, and closing your laptop kills nothing.\n\nThe shape is simple: **browser ↔ Cockpit server ↔ the real Claude Code CLI**. Not a reimplementation of the agent loop, the actual CLI, driven headless or through a pseudo-terminal.\n\nFour things follow:\n\n1. **Claude Code on your phone.** Reply from a train, a kitchen, anywhere a browser opens. The session you started at your desk is right there, still working.\n2. **Many sessions running at once.** Switch between projects without juggling tmux panes. Status beacons show which sessions are working, waiting, or idle, and the chat view stitches across `/clear` so long threads keep their full visual history.\n3. **Any model through the full agentic loop.** Tool use, file edits, and permission prompts work the same whether the model is Claude, something free off OpenRouter's catalog, or DeepSeek. Providers that only speak the OpenAI wire format run through a built-in translation proxy, thinking traces included.\n4. **Unattended agents on a schedule.** Not a cron wrapper: each job is a sandboxed run with its own model, its own tool and MCP allowlists, and a time budget, reporting back through an inbox or straight to your phone.\n\nInside a session: a tabbed, split-pane layout holding the chat, a diff viewer for code changes (split or inline), a file viewer with syntax highlighting, and an embedded terminal. Messages sent while Claude is working queue server-side and deliver when the turn ends, and `/btw` answers a quick side question in a separate tool-less Claude without disturbing the run. Plus global search across all sessions (Ctrl+Shift+F), searchable prompt history on the up arrow, and plan-mode approvals when Claude proposes a plan. The sidebar keeps sessions, active reviews, file changes, and file trees in collapsible sections.\n\n**Bring every provider under one roof.** One-key connect to OpenRouter, OpenCode Zen, and DeepSeek, or point Cockpit at any Anthropic-compatible endpoint of your own, each with its own credentials. Connect OpenRouter and its whole catalog is a click away, free models included, with live pricing and a FREE badge shown right in the picker. Curate the list down to the handful you actually use, then pick the model per session and per scheduled job, with 200K or 1M context and a thinking level. Each provider tracks its own spend or balance in the usage panel.\n\nEach session runs in **Stream** mode (headless JSON, the default) or **PTY** mode, which drives the interactive CLI inside a pseudo-terminal. PTY exists for a reason: subscription plans bill programmatic and interactive usage differently, and PTY keeps Cockpit sessions on the interactive side. Switch per session.\n\nIt also takes care of things you usually hand-edit: agents, skills, hooks, MCP servers, plugins, CLAUDE.md memory. All editable from the UI, or conversationally: the built-in Cockpit Assistant is a Claude session wired to Cockpit's own MCP server, so \"create a nightly job that...\" becomes a config change you approve or reject.\n\nPR reviews are a first-class flow. Pick an org, pick a repo, pick a PR. Cockpit reads the diff via the GitHub CLI and starts a Claude session scoped to it. Diff on one side, chat on the other. Active reviews pin to the sidebar alongside your sessions. Day-to-day git lives here too: review the working tree, generate a commit message, commit and push without leaving the browser.\n\n**Scheduled jobs** are where the server earns its keep. Give one a prompt and a schedule (a cron expression or a simple interval) and scope it tightly: its own model and thinking level, the exact tools and MCP servers it is allowed to touch, a run-time budget, how long to keep transcripts. It runs unattended, and each run renders as a normal session transcript you can open later. Results land in an inbox, with optional push to Telegram or ntfy.sh, so a nightly dependency bump or a morning PR-triage pass reaches your phone while you are away from the machine.\n\nRun it on your laptop the way you'd run the TUI. Or run it on a home server and reach it from your phone. Same UI either way.\n\n## Screenshots\n\n\n ![\"Chat](\"docs/screenshots/chat-view.png\")
\n ![\"Per-session](\"docs/screenshots/session-settings.png\")
\n
\n ![\"Scheduled](\"docs/screenshots/scheduled-jobs.png\")
\n ![\"Pull](\"docs/screenshots/pr-review.png\")
\n
\n ![\"Message](\"docs/screenshots/message-search.png\")
\n ![\"Settings](\"docs/screenshots/settings.png\")
\n
\n ![\"Context](\"docs/screenshots/context-usage.png\")
\n ![\"Account](\"docs/screenshots/account-usage.png\")
\n