How lexus2016/claude-code-studio works
Claude Code Studio is a web and desktop workspace that lets a developer chat with Claude Code, queue autonomous work, and manage projects. The main workflow starts in the browser, passes through the server, and runs Claude CLI work in project sessions; task chaining, isolated worktrees, persistent sessions, terminals, and remote controls extend it. The README documents capabilities beyond the sampled excerpts, so some subsystem wiring is omitted rather than inferred. Paths for documented but unsampled features use only supported files or enclosing directories.
Main entry points: server.js Studio server · main.js Desktop shell · telegram-bot.js Telegram control · preload.js Desktop bridge
Components 25
User access
- Browser UI
- Studio server
server.js - Authentication
auth.js - Desktop shell
electron/main.js - Desktop bridge
electron/preload.js
Agent execution
- Claude CLI
claude-cli.js - Interactive CLI
claude-interactive.js - Terminal bridge
terminal-bridge.js - Terminal sessions
terminal-session.js - Worktree isolation
worktree-manager.js
Task workflows
- Task MCP
mcp-task-manager.js - Agent dependencies
agent-dag.js - Agent results
multi-agent-result.js
Sessions and state
- SQLite adapter
db-adapter.js - Configuration
config-resolve.js
Remote integrations
- Telegram control
telegram-bot.js - SSH projects
remote-env.js - Remote files
remote-files.js - Public tunnel
tunnel-manager.js - External agents
bots.js
Other components
- Developer
- Claude service
- Telegram
- SSH host
- Tunnel provider
Connections 26
- Developer → Browser UI: uses
- Browser UI → Studio server: sends requests
- Studio server → Authentication: checks access
- Desktop shell → Studio server: launches
- Desktop shell → Desktop bridge: exposes IPC
- Desktop bridge → Browser UI: bridges desktop
- Studio server → Claude CLI: runs tasks
- Claude CLI → Claude service: invokes
- Studio server → Interactive CLI: starts sessions
- Studio server → Terminal bridge: handles terminals
- Terminal bridge → Terminal sessions: manages sessions
- Studio server → Worktree isolation: isolates work
- Studio server → Task MCP: serves task tools
- Task MCP → Studio server: posts actions
- Studio server → Agent dependencies: resolves dependencies
- Studio server → Agent results: handles results
- Studio server → SQLite adapter: reads and writes
- Studio server → Configuration: loads settings
- Telegram control → Telegram: receives updates
- Telegram control → Studio server: controls tasks
- Studio server → SSH projects: connects remotely
- SSH projects → SSH host: opens SSH
- Studio server → Remote files: transfers files
- Studio server → Public tunnel: manages exposure
- Public tunnel → Tunnel provider: starts process
- Studio server → External agents: delegates tasks