Tabs

Tabs is a browser for the Mac with tabsh inside it.

A session is a tab. The terminal and the agent chat live in the tab strip you already use — no second window, no board to open first. WebKit, free, for macOS 14 or later.

Version 1.1.0 · 11.9 MB · Free · Intel Mac?

fig. 1 — the app with a session tab. The real screenshot lands in M2.
fig. 1 One browser, one tab strip: a tabsh session on one side of the split, the page it is building on the other.

A session is a tab.

Open a session and it appears in the tab strip like any other page. The terminal or the agent chat fills the tab; there is no board behind it, no second strip, and no separate window to ⌘-Tab back to.

Close the tab and the shell keeps running. Open the session again and you are back in the same conversation, with its scrollback. Quitting the browser does not end it either.

Split, when you need it.

The page and the session working on it, side by side. Drag the divider and the width is yours; the pair comes back with its space, including after a restart. Any two tabs can split — a session beside its page, the docs, or another session.

A quiet browser underneath.

The base is Search: a small native WebKit browser with nothing between you and the page. Everything inherited works the same here, alongside the sessions.

One package. Nothing else to install.

Tabs carries the tabsh daemon inside the app. Agents are the CLIs already on your Mac — claude, codex, opencode — as with any terminal.

Version 1.1.0 · Free · These builds are ad-hoc signed, not notarised, so macOS asks once. Nothing else is required.

Questions, answered.

What is Tabs?

A Mac browser built on Search, with the tabsh daemon inside it. A tabsh session — a terminal or an agent chat — opens as a browser tab, in the tab strip you already use.

How is this different from opening tabsh.cc in Safari?

One tab strip. The session is a browser tab, so it sits beside the page it is working on, with the same split, history and shortcuts. The daemon is bundled and local, so there is no separate app to start and nothing to sign into.

Do I need tabsh installed separately?

No. The daemon ships in the app and keeps its own database under Application Support. It does not touch a tabsh you already run, and a tabsh on another port is left alone.

Is it Chromium?

No. Tabs runs on WebKit, the engine that ships with macOS. Pages render as they do in Safari, and the app stays small because there is no second engine inside.

Which Macs?

macOS 14 or later, on Apple silicon or Intel. Intel Macs have a download of their own, linked under the download button.

Do my agents work?

Yes, if their command is on your PATH — Claude Code, Codex, Cursor CLI, OpenCode, or any CLI that takes a prompt. Tabs starts the same binaries a terminal would.

Does it sync?

No. Tabs, history, passwords and sessions stay on the Mac they run on. There is no account, no telemetry, and no server of ours.

Where do updates come from?

Not from an updater yet. Automatic updates are off in this fork until it has its own signed feed, so for now a newer build is a download from Releases. Settings and sessions are left alone when you replace the app.

Is it open source?

Yes. Tabs is a fork of Search by Office Commun, under the MIT license. The source and the fork notes are on GitHub.

Something is wrong.

Open an issue at github.com/Blaise1030/tabs. Include the app version from Settings › About and what you were doing.