Claude Code Studio

The browser interface for Claude Code CLI. Chat with AI, run tasks on autopilot, and manage your projects — all from one tab.

English | Українська | Русский

📖 From Terminal to Dashboard | Remote Access Revolution

Works on Windows, macOS, and Linux — zero platform-specific setup.

v7.18.3 — The Subscription engine works on a fresh install. On a machine where claude was never opened (any new Docker container, for one), the engine used to stop on Claude's first-run screens, close claude and lose the message. It now answers them the way the default engine already does, trusts only the folder the session runs in, and touches your ~/.claude.json only when something is missing. A screen it cannot answer is shown to you instead of being typed into. Also recent: in v7.18.2 expired chats remove their worktrees, and since v7.18.0 the macOS app is signed, notarized and updates itself (Apple Silicon only).

Upgrading a Docker install from 7.2.x or older. docker-compose.yml now keeps config.json and .env on the data volume (CCS_CONFIG_PATH / CCS_ENV_PATH) so the config UI's changes survive a container rebuild — previously they lived in the image layer and were discarded. On first start the server copies a legacy file across automatically and leaves the original in place. The one case it cannot rescue is a container whose config.json only ever existed in that discarded writable layer: copy it out before upgrading — docker cp claude-code-studio:/app/config.json ./config.json, then after docker compose up -d put it back with docker cp ./config.json claude-code-studio:/app/data/config.json && docker compose restart.

---

Why Claude Code Studio?

Claude Code CLI is powerful — it writes code, runs tests, edits files, and ships features. But it lives in the terminal, and the terminal has limits: context gets lost between sessions, parallel work means juggling tabs, and there's no way to queue tasks and walk away.

Claude Code Studio fixes this:

• Queue work and walk away — Kanban board + Scheduler. Claude works while you sleep. Come back to everything done.
• Control from anywhere — Telegram bot + Remote Access. Check results from your phone at the gym.
• Autonomous pipelines — Tasks create child tasks during execution. One "check issues" task spawns fix tasks automatically.
• Context never gets lost — SQLite-backed sessions with self-healing replay. Resume days later, right where you left off.
• True parallel execution — Multiple tasks run simultaneously in the same project. No manual tab juggling.

---

---

🖥 Desktop App

Prefer a native window over a browser tab? Claude Code Studio also ships as a desktop app for macOS, Windows and Linux. It runs the same server locally and renders the full Studio in a native window — chat, Kanban, agents, MCP, skills, everything. The web server is unchanged; the desktop build is simply a second way to launch it.

Install (from the latest release):

• macOS (Apple Silicon) — download the .dmg (signed and notarized), open it and drag the app to Applications
• Windows — download the …-Setup-….exe installer
• Linux — download the .AppImage (portable) or .deb

Prerequisite: same as the web version — the Claude Code CLI installed and logged in. The app detects it on launch and shows an install hint if it's missing.

Built-in updates: the app tells you when a new version ships and updates itself in one click on every OS. On macOS it has to run from Applications — started straight from the .dmg or from Downloads, it cannot replace itself and says so.

Coming from the CLI/web version? The desktop app keeps its own data folder, so you can pull your existing history and settings across in one step — no manual file copying:

1. Open the desktop app → menu File → Import data from CLI / web version…
2. Pick the folder of your old install — the one that contains data/ and config.json. For the web/server version that's the project folder where you ran npm start (the directory with server.js).
3. Confirm Import & Restart.

It migrates your chat history (data/chats.db), projects, SSH hosts and uploads, plus MCP servers and skills (config.json + skills/). It does not copy .env or workspace/ (server-only settings and working files). A timestamped backup of the desktop's current data is made first, then the app restarts automatically.

Where the desktop keeps its own data — macOS: ~/Library/Application Support/claude-code-studio/ · Windows: %APPDATA%\claude-code-studio\ · Linux: ~/.config/claude-code-studio/

Build from source:

npm install
npm run electron:dev     # run the desktop app locally
npm run dist:mac         # build installers — or dist:win / dist:linux

The desktop app is single-user and binds to 127.0.0.1 (no password screen, no network exposure).

---

🌐 Web version (run it yourself)

Prerequisites: Node.js 18+ + Claude Code CLI installed and logged in (Claude Pro or Max subscription)

Node.js 22.13+ — zero native compilation. Uses built-in node:sqlite, no C++ toolchain needed. Older Node.js versions fall back to better-sqlite3 (requires build tools).

npx github:Lexus2016/claude-code-studio

Open http://localhost:3000, set a password, start chatting.

It listens on localhost only. This UI drives `claude --dangerou