Outbye is a small dispatcher that runs on your own machine, next to the sessions you already have open. Each one gets a chat you can reach from a phone browser — full history, the turn streaming live, a diff of every edit, and a reply box.
Every remote-coding product puts a relay between you and your machine. Outbye doesn't — it is the machine.
The Manager is a Node process on your machine with its own SQLite file. Your code and prompts go to Claude and nowhere else — no vendor in the path that could read, cache or lose them.
A message reaches a session through whichever channel exists: the VS Code panel on standby, the CLI monitor, or a headless continuation that resumes it by id. Write to a session that went quiet hours ago — it wakes up.
Outbye works on top of Claude Code instances that are already logged in: no claude.ai integration, no OAuth flow, no token storage of its own. It drives the official CLI you already run.
The whole history, whatever channel it came from — including what you typed into the VS Code panel.
When a turn wants to run Bash or fetch a URL, a card with Allow / Deny reaches your phone.
A browser and editor over the project the session runs in, and side-by-side diffs of every edit as it lands.
Work and personal profiles side by side, each with its own usage bars and one-tap switching.
Send a screenshot with the paperclip or Ctrl+V, straight into the turn.
A turn can run on an Anthropic-compatible endpoint instead — the config only supplies the key.
A scripted replay of the real client — the same turns, cards and bars you get on your phone.
← swipe the diagram →
A plugin reports session events to the Manager over hooks.
The Manager keeps sessions, events and the queue in SQLite.
Your message is handed to whichever channel the session has live.
Nothing live? A headless continuation resumes it by id.
Opens a fully populated Outbye on 127.0.0.1:17451 — invented projects, sessions and chats, scripted replies. No private data and no Claude account involved.
Outbye runs next to Claude Code, so the install is the dispatcher plus the plugin that reports your sessions to it.
npm install, then copy config.example.json to config.json.npm start — the Manager comes up on localhost:17450.claude plugin marketplace add /path/to/outbye claude plugin install claude-hub@claude-hub
To reach it from outside your own machine, set web.token first. The API can read
every session's history and the files of every project, and can start turns in your
repositories — treat that token like a password. With an empty token, external requests are
refused rather than allowed.