Lexus2016/claude-code-studio
143 stars · Last commit 2026-10-08
A fully functional web workspace for Claude Code CLI—chat, Kanban task board, task scheduling, multi-agent orchestration, MCP servers, skills, remote access (Web, SSH, Telegram), projects, and real-time data streaming.
README preview
 # 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](README.md) | [Українська](README_UA.md) | [Русский](README_RU.md) > 📖 [From Terminal to Dashboard](https://www.notion.so/From-Terminal-to-Dashboard-How-Claude-Code-Studio-Changes-AI-Assisted-Development-329676bbc5b6809f9c63e29ca66d8135) | [Remote Access Revolution](https://www.notion.so/Claude-Code-Studio-The-Remote-Access-Revolution-for-AI-Assisted-Development-329676bbc5b68097a5aefac4db29a60d) > Works on **Windows, macOS, and Linux** — zero platform-specific setup. > **v7.18.4** — **Signing out really signs out, and Stop stops everything.** An open chat or terminal connection used to stay logged in after you signed out or changed the password; it is now closed, and desktop mode and first-run setup accept only a direct local request (no DNS-rebinding or proxy tricks). Stop now ends the whole `claude` process tree, so a stray Bash tool can no longer leave a turn hanging. Kanban and Schedule no longer show a stale board after you switch project, and **Run now** really runs now. Releases are gated on the test suite. Also recent: in **v7.18.3** the Subscription engine works on a fresh install, 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