Your Claude Code sessions, reachable from wherever you are.

Outbye is a small dispatcher that runs on your own machine, next to the Claude Code sessions you already have open. It gives every session a chat you can reach from a phone browser — full history, the turn streaming as it happens, a diff of every file edit, and a reply box.

Self-hosted No cloud relay No second login AGPL-3.0 Beta

Why another one

Nothing in the middle

The Manager is a Node process on your machine with its own SQLite file. Your code and your prompts go to Claude and nowhere else — there is no vendor in the path that could read, cache or lose them.

Not only live sessions

A message reaches a session through whichever channel exists: the VS Code panel on standby, the CLI monitor, or — when nothing is live — a headless continuation that resumes the session by id. Write to a session that went quiet hours ago and it wakes up.

It authenticates nothing

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.

What you get

A chat per session

The whole history, whatever channel it came from — including what you typed into the VS Code panel.

Tool approvals

When a turn wants to run Bash or fetch a URL, a card with Allow / Deny reaches your phone.

Files and diffs

A browser and editor over the project the session runs in, and side-by-side diffs of every edit as it lands.

Several accounts

Work and personal profiles side by side, each with its own usage bars and one-tap switching.

Images

Send a screenshot with the paperclip or Ctrl+V, straight into the turn.

Other backends

A turn can run on an Anthropic-compatible endpoint instead — the config only supplies the key.

How it works

  web / desktop clients
           │
           ▼
  Outbye Manager
  localhost:17450 · SQLite
      ▲           │
   hooks       monitor
   (events)    (long poll)
      │           ▼
  Claude Code session
  (CLI / VS Code)

A plugin reports session events to the Manager over hooks; the Manager stores sessions, events and the queue in SQLite and hands a message to whichever channel that session currently has.

Try it without installing anything

npm install
npm run demo

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.

Install

  1. Requirements: Windows, macOS or Linux · Node.js 20+ · Claude Code installed and already logged in.
  2. npm install, then copy config.example.json to config.json.
  3. npm start — the Manager comes up on localhost:17450.
  4. Install the plugin, which is what connects your sessions to it: 
    claude plugin marketplace add /path/to/outbye
claude plugin install claude-hub@claude-hub
  5. Open a Claude Code session — it shows up in the web client.

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.