Collaborative Claude Code for teams.
Run multiple Claude instances, share them with teammates in real time, and search across every conversation you've ever had — from the terminal or the browser.
curl -fsSL https://raw.githubusercontent.com/empathic/workshop/main/scripts/install.sh | bashInstalls the work binary to ~/.local/bin. Requires
Claude Code.
workA TUI opens where you create and switch between Claude Code sessions. Press
Ctrl+] to move between sessions and the overview. A background daemon keeps
everything running — close the TUI and your sessions stay alive.
For the web UI:
work serverThen open the URL it prints. You get live terminals, a conversation viewer, task board, and fleet overview — all in the browser. The CLI and web UI talk to the same daemon, so use whichever you prefer.
Workshop is built for collaboration. To share over a tunnel:
work server --profile tunnel
work auth enableOr on your LAN:
work server --profile server
work auth enableShare the URL. The first person to register becomes admin. From there:
- Shared terminals — watch what Claude is doing on a teammate's instance, with a lock to coordinate who's typing
- Live presence — see who's connected and which instance they're focused on
- Chat — real-time messaging, per-instance or global
- Task board — create and assign tasks tied to instances, synced to every client
Your local CLI always bypasses auth, so work attach keeps working without
credentials.
Workshop automatically syncs conversation history from Claude Code into a local SQLite database — every session, every project, fully searchable.
work server --import-all # sync all projects
work server --import-from ~/myapp # sync one projectThe web UI gives you full-text search with syntax-highlighted code and diffs. Find that conversation from three weeks ago where Claude solved the exact problem you're looking at now.
All config lives in ~/.workshop/config.toml. See
docs/configuration.md for the full reference —
profiles, env vars, auth settings, server tuning.
What happens when I type work?
A daemon starts in the background (if one isn't already running) and manages
all your Claude instances. The TUI connects to it. So does the web UI.
Closing the TUI doesn't kill anything — instances keep running until you
work kill them or work kill-server.
How is this different from tmux?
Workshop understands Claude's protocol. It detects state (thinking, tool use, idle), imports conversations into a searchable database, provides multi-user auth with live presence, and gives you a web dashboard. tmux sees raw bytes.
Does my data leave my machine?
No. Everything is local: SQLite database, conversation history, config. The
tunnel and server profiles bind to a network interface so teammates can
connect, but the data stays on your machine.
What platforms are supported?
Linux (x86_64, aarch64) and macOS (Apple Silicon, Intel).
- Configuration — profiles, env vars, CLI options
- Architecture — system design, protocols, state detection
- Operations — endpoints, metrics, troubleshooting
- Contributing — building from source, dev setup, testing
Apache 2.0 — Copyright 2025-2026 Empathic, Inc.