← All tools

deadeye636/switchboard

AI Agent
Popularity 75 Updated Development & Build

Desktop app to browse, search, launch and monitor your coding-CLI sessions (Claude Code, Codex, Hermes, Pi, Antigravity) across every project.

githubauto-collected

Installation

A directly usable install command is not verified yet. Check the project documentation or releases.

Switchboard

Your command center for Claude Code, Codex, the Antigravity CLI, Hermes and Pi.

Switchboard is a desktop app that gives you one view of every session your coding agents have, across every project. Launch, resume, fork and monitor them from a single window, instead of juggling terminal tabs and digging through ~/.claude/projects for that conversation from last week.

## ⚠️ Read this first — personal fork, no warranty, no liability This repository (codename deadeye) is a personal, unofficial fork, maintained for my own use. - It is built on upstream work and has since been substantially rewritten. Who built what: Lineage & credits. - This is not an official product. It is not affiliated with, endorsed by, or supported by Anthropic, OpenAI, Google, or any upstream author. - No warranty. No support. No liability. Provided "as is" under the MIT license, with no guarantees of any kind. You use it entirely at your own risk. - Builds are unsigned. For anything you care about, build it yourself from source and run the code you audited — see Security & trust.

What it does

One sidebar for every agent. Sessions from all five CLIs group into the same project by working directory, are searchable together, and each carries a provider badge. Resume keeps a session on its own binary. A backend you do not use can be switched off entirely — a Codex-only setup is a first-class setup.

Sessions in panes. The default layout splits the area the way VS Code splits editor groups: each pane keeps its own tabs with a right-click menu (close, stop, relaunch, redraw), you drag a tab onto a pane edge to split, and the arrangement is still there after a restart. The terminal is live — connect to a running session or start a new one without leaving the app. Seven terminal themes, configurable font and zoom, clipboard image paste, drag-and-drop that inserts files and images the same way, GPU rendering with automatic fallback. A session can also move into a window of its own for a second monitor, and back again, or across into any other window that is already open — it keeps running throughout, and a window can hold as many sessions as you move into it. The other layout is the grid below: every session as a card at once, rather than one at a time.

It tells you when an agent needs you. A prioritized attention inbox, OS notifications, a taskbar badge and a tray icon — even when the window is in the background. Detection runs off CLI hooks, so it catches the permission prompts a terminal heuristic misses.

And it tells you what you missed. Come back after being away from the machine and the inbox holds one entry: every session that changed while you were gone, in one list, each row opening to what it did and which files it touched. Away means away — leaving the desk, not switching windows — and the record behind it survives a reload, a window close and a restart.

You can hand a busy session its next job and walk away. Stage a prompt for a session that is working, or sitting on a permission dialog, and Switchboard types it in once the session is ready for it — never over a turn in progress, and never over a line you have half-typed in the session's own prompt. It is a prompt of its own, not a keystroke buffer: nothing is intercepted on its way to the CLI, so the keys that answer a permission dialog still answer it. The session's row says what is waiting, and says when something you left in that prompt line is holding it up — send that line and the staged prompt follows as its own turn.

It notices when a session's context is filling up. For Claude, Codex and Pi it measures how much of the model's context window the last turn used, shows it in the row ("62 % context"), and recommends a handoff from 80 % (adjustable). Long sessions below that are marked Growing or Marathon Risk. When it is time, a guided handoff asks the agent for a context packet, starts a fresh lean session with it, and switches over.

Projects are a list you control. Add them by hand or automatically, hide them, rename them, tag them. Nothing goes missing quietly: sessions in projects that are not on your list stay indexed and searchable, and a line under the sidebar says how many there are and offers to add them.

A worktree belongs to its project, and behaves like it. Checkouts under .claude/worktrees/ and the two layouts beside it are gathered under one caret in their project's row, not scattered through the list as if they were projects of their own — a worktree created inside another one included. They read the project's settings, they are hidden when it is, and a fresh checkout with no sessions still gets a row you can start a session in. Anything running is drawn outside the fold, so collapsing it can never hide work in progress.

It introduces itself once. The first launch opens a short tour: the CLIs that are switched off, the attention hooks nobody finds, the drag that splits a pane, why the sidebar is shorter than the session list. Every pane that names a setting also carries it, so a thing you have just had explained is a thing you can change without going looking for it, and five of them draw what your choice will look like. Four ways out of it, and Settings → Maintenance brings it back.

Your repository, in the app. A git glyph on every project header opens a changes window: files grouped by state, renames as old → new, click one and its diff expands inline. Polling never takes git's index lock, so it cannot fight the agent working in that repo.

Notes that stay attached to where they came from. Tasks scoped to a project, a session or a single transcript message, created from a selection or from the terminal, with a captured quote and a jump back to the source. Plus per-message bookmarks and colored tags on both projects and sessions.

It knows what you spent. Per-backend token, message and cost metrics; a contribution heatmap; tokens per backend over time; a weekday × hour grid of when you actually work. Cost is never presented as a bill — an estimate is labelled as one, and a backend that reports no money gets no chart rather than a row of zeroes.

<details <summary<bThe full feature list</b</summary