TABSH

A CALMER WAY TO WORK WITH AGENTS, IN A BROWSER TAB

2026

# YOUR SHELLS AND AGENTS, ONE CALM SCROLL

tabsh runs your shells and agents in the browser tab next to your work. The list catches you up: what's moving, what needs you, and what's done.

$ curl -fsSL https://tabsh.cc/install.sh | sh  
$ tabsh  # opens the app in your browser, paired
# or Homebrew: brew install blaise1030/tap/tabsh

tabsh - A calmer way to work with agents, in a browser tab | Product Hunt

fig. 1 what you get when you install: the full app, running live.This is the tabsh app itself, built from the same code as /app/, so it never falls behind. It can run here because the app is just a web page that talks to the daemon over HTTP and WebSocket. The demo swaps in a pretend daemon that lives in this page: scripted shells and files, in memory. Nothing runs on your machine, and nothing leaves the page.

## WHY A BROWSER TAB?

## ONE LIST, EVERY PROJECT

Columns move one card. The list catches you up: every card, every project, one scroll, grouped by status and tagged with its folder. Open a card and its shell is right there.

The tabsh list beside a live terminal: cards from the shop and api projects grouped by status on the left, the shop: npm run dev shell on the right.
fig. 2 the list, with a shell beside it.
The tabsh board as columns: Backlog, In progress, Needs input, Completed and Archived, with cards from the shop and api projects.
fig. 3 the same cards as a board, when you want to drag one across.
  1. Every project, one place. A shop card and an api card, one list. Each card keeps its folder.
  2. Grouped, not scattered. Backlog, In progress, Needs input, Completed, Archived. Fold what's done.
  3. One scroll. No columns to pan, no drawer to open. If a card needs you, it's already there.

## YOUR AGENTS, YOUR CALL

Pick the agent per card: Claude Code, Codex, Cursor CLI, OpenCode, or any CLI that takes a prompt. Run it as a terminal (TUI) or a chat (UI); switch per card. Models change in the chat.

TUI Claude Code in a real terminal

Claude Code running as a terminal in a tabsh card: its refund transcript, tool lines, test result, and a prompt asking whether to commit.

UI Claude Code as a chat

Claude Code running as a chat in a tabsh card: the refund conversation, the message composer, and the Claude Sonnet 4.5 model picker.
fig. 4 one agent, two surfaces: a real terminal (TUI, left) or a chat (UI, right).

Providers are commands. Pick one to set its startup, resume and ACP commands, or add any CLI that takes a prompt. {prompt} is the card's first prompt; {session} is a resumable conversation.

The Agent providers list in tabsh's command palette: Claude Code, Codex, Cursor CLI and OpenCode, each with its startup command, and an Add provider row.Claude Code's provider settings in tabsh: its name, startup command, resume command and ACP command.
fig. 5 pick a provider, then set its startup, resume and ACP commands.

There is no worktree choreography. Agents run in the folder you started them in, on your branch. That is the trade: no isolation, so two agents in the same checkout can collide. tabsh doesn't hide that behind a copy of your repo.

## OPTIONAL: ANOTHER DEVICE

The daemon listens on loopback. If you want the same board on your phone or another laptop, tabsh can serve itself over Tailscale: turn it on, scan the code, and the device is paired. Off by default, and there is no relay of ours in between.

The Open on another device page in tabsh: Tailscale sharing is on, with a QR code for a new device and a list of paired devices.
fig. 6 optional: serve the same board to a phone over Tailscale.

## FEATURES

+--------------------------+------------------------------------+-----+
| One list, every project  | Every card in one scroll           | ⌘B  |
| Grouped by status        | Fold what is done                  |     |
| Shells outlive the tab   | Close, reload, quit: they reattach |     |
| Survives restarts        | Tabs, folders, scrollback restored |     |
| Your agents, not ours    | Claude Code, Codex, Cursor CLI…    |     |
| TUI or UI, per card      | A real terminal or a chat panel    |     |
| No worktrees             | Your checkout, not a copy          |     |
| File explorer            | Follows your shell's folder        | ⌘⇧E |
| Search files             | By name, across the project        | ⌘⇧F |
| Click paths and URLs     | Open, edit and save in a pane      |     |
| Group tabs               | By repo or by tag                  | ⌘⇧Y |
| Drop files in            | Dragged files type their path      |     |
| A bell, not a feed       | The tab rings; the favicon badges  |     |
| Themes and fonts         | 12 themes, 9 fonts                 | ⌘K  |
| Nothing leaves localhost | Keystrokes stay on 127.0.0.1       |     |
+--------------------------+------------------------------------+-----+

> Keys are the Mac defaults. Change any of them from ⌘K.

## FAQ

What's the difference between the board and the list?

The board is columns you drag cards across. The list is the same cards in one scroll, grouped by status. ⌘B switches between them; the list is the one for catching up.

Does it work in Safari?

Safari (and every iOS browser) won't let this site reach the daemon, so the daemon serves the app itself at http://tabsh.localhost:7681, and this site sends Safari there. File → Add to Dock opens it like an app.

Why does Chrome ask to access apps on my device?

That's the connection to the daemon on your machine. Allow it once.

Is it safe?

The daemon listens on 127.0.0.1 only and answers only the tabsh app carrying your token. The token rides in the URL fragment, which browsers never send to a server. Keystrokes never leave your machine.

Can I open it from my phone or another computer?

Keep the daemon on loopback — exposing the port on the network would be plain HTTP to a shell. If you need another of your devices, put Tailscale (Serve or an SSH tunnel) in front of it. Use the Tailscale IP, not MagicDNS. How to set that up.

Can it keep running after I close the terminal?

With Homebrew, brew services start tabsh runs it from login. Then openhttp://127.0.0.1:7681 once to pair this browser.

Which systems does it run on?

macOS and Linux. There's no Windows build.

How do I upgrade?

With Homebrew: brew upgrade tabsh, then brew services restart tabsh if you run it as a service. With the install script: re-run it.

Lost the link?

Open http://127.0.0.1:7681 in the same browser and the daemon sends you back to the app, paired.

Is it free?

Yes. It's open source under the MIT license, on GitHub.

~*~ EOF ~*~