Skip to main content

Coding agents at work in their tabs, Windows restarts and they are gone, Bit calls them back, and the tabmancer dashboard shows them all

tests PyPI Python 3.10+ Apache 2.0 licence

tabmancer

A dashboard for your coding-agent sessions, in the terminal: Claude Code first, Codex and Antigravity if you use them. See every recent session from every project and what the open ones are doing right now, which one waits for you, and how full each one's context is. Run a team of sessions that talk to each other. And after a reboot or a crash, call back the sessions you had open, each in its own tab and folder; the ones cut off mid-reply carry on by themselves.

tabmancer in use: a cut-off session, a card filter, a team, the team view and the keys

Try it

uvx tabmancer --demo         # made-up sessions: nothing of yours is read or changed

Every key works in the demo, but nothing opens and no model is asked. Then install it:

uv tool install tabmancer    # or: pipx install tabmancer
tabmancer                    # the dashboard

It needs Python 3.10+ and Claude Code's claude on your PATH. Upgrade it with uv tool upgrade tabmancer (or pipx upgrade tabmancer): the dashboard says when a newer version is out (updating). ? lists every key and runs the one you pick; the footer shows the common ones and what they do on the row you are on. On Windows, tabmancer shortcut adds a desktop shortcut and tabmancer startup on opens the picker at login when sessions were left open.

What it does

The dashboard: live counters, projects, recent sessions, how each one ended, and a preview with an AI summary

  • Calls your sessions back. After a reboot or a crash, the sessions that were open start out ticked: Enter opens each in its own tab and folder, and the ones cut off mid-task are told to carry on. Resume, fork or start fresh, per session.
  • Shows what each one is doing. Working, waiting for you or needing you; how each closed one ended (done, stopped, cut off, unanswered, at a usage limit); how full every context is; your plan limits in the top bar. j goes to the next one waiting for you.
  • Gets past a usage limit. Sessions stopped at a limit say when it lifts; c continues them all then, or right away once you have signed in with another account.
  • Runs teams. Several sessions on one project with an orchestrator, talking through Claude Code's own messaging between sessions: one row in the list, and a view of who tells whom what.
  • Hands crowded sessions over. h moves the work to a fresh session, with a full handover as its first message.
  • Counts. Tokens, when you work, tools and files, plan limits with a forecast, and a written report of the week to share.
  • Finds. / finds a session by anything you or Claude said in it.
  • Codex and Antigravity too, if you use them.

Everything it does, and the details: using it (what each status means, every key, writing to a session, background sessions, workspaces) · teams · handing over · stats and reports · setup and commands · how it works

Keys

Key Action
Enter open the ticked sessions, or the highlighted one, each in its own tab
Space tick a session
m how it opens: resume → auto-continue → fork → new
p write a prompt to a session (an open one: go to its tab)
j the next open session waiting for you
/ find by project, title, or anything said in a session
n fresh sessions in several projects at once
T teams
h hand a session over to a fresh one
c continue the sessions stopped at a usage limit
u stats
? every key, explained; Enter runs the one picked

All the keys.

Where it runs

Built and used every day on Windows 11 with Windows Terminal: tabs, going to a session's tab, start at login, desktop notifications and a desktop shortcut. On Linux, tabs open in tmux (tried for real), WezTerm, kitty, GNOME Terminal and Konsole; on macOS in iTerm2 and Terminal.app, which have not been tried on a real Mac yet. In any other terminal, tabmancer prints the commands to run. What has been tried where. Reports are welcome.

Claude Code's formats are its own and can change between releases: after an update, tabmancer doctor checks that everything tabmancer relies on still works.

Privacy

tabmancer runs on your machine and talks to no server of its own. It reads the transcripts the agents already keep (~/.claude, ~/.codex, ~/.gemini) and asks the claude CLI which sessions are open and how full your plan limits are (/usage, a local command). It reads which account you are signed in with (its email and plan) from ~/.claude.json and Codex's auth.json, to show it in the top bar, and remembers the emails of the Claude accounts it has seen, in its own folder, to offer them when you switch (A). Once a day it asks PyPI which version of tabmancer is the latest, to tell you of a newer one (tabmancer updates off stops it). A model is called only when you ask for one, through your own CLI and plan: an AI summary (s), a handover (h), a report (r in the stats). It types into an open session only when you have it continue the ones stopped at a usage limit (c). Nothing is sent anywhere else, and there is no telemetry.

Trademarks

tabmancer is an independent project, not made by, affiliated with or endorsed by Anthropic, OpenAI or Google. Claude Code, Codex and Antigravity are their owners' trademarks; they are named here only to say what tabmancer works with.

License

The code is licensed under the Apache License 2.0: keep the NOTICE with it and credit "tabmancer by Sinan Tüfekci". Bit, the robot, is licensed under CC BY 4.0: wherever you use it, credit "Bit by Sinan Tüfekci". Not affiliated with Anthropic.

Metadata

Release files for tabmancer 0.1.1

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for tabmancer 0.1.1
File Size Uploaded Provenance Actions
tabmancer-0.1.1.tar.gz 375.2 kB Without provenance Details for tabmancer-0.1.1.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for tabmancer 0.1.1
File Interpreter ABI Platform Actions
tabmancer-0.1.1-py3-none-any.whl Python 3 none any Details for tabmancer-0.1.1-py3-none-any.whl

Total release size: 643.9 kB

Release files / tabmancer-0.1.1.tar.gz

Download URL tabmancer-0.1.1.tar.gz
Size 375.2 kB
Tags Source
SHA-256 checksum
How to use checksums
c334536b2ebc309760187b0144ac1f7a37957cd13cb8e051fb8066518cd969ba
BLAKE2b-256 checksum
How to use checksums
666680aaee3e678f1b3c335e30e4a7f963e1fce37eb85ee65aaea2952b8eeb42
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via uv/0.13.6 {"installer":{"name":"uv","version":"0.13.6","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"26.04","id":"resolute","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}

Release files / tabmancer-0.1.1-py3-none-any.whl

Download URL tabmancer-0.1.1-py3-none-any.whl
Size 268.7 kB
Tags Python 3
SHA-256 checksum
How to use checksums
72375d5662e61ac55e13a0692c51fbed5f49aa219c56f1a9702d643ff34b7525
BLAKE2b-256 checksum
How to use checksums
c115b06c4a43cafafe34c7f41e68e93f30adc4edfadcdc4e99bd5145178f530f
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via uv/0.13.6 {"installer":{"name":"uv","version":"0.13.6","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"26.04","id":"resolute","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}

Security for tabmancer 0.1.1

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

No provenance found

None of the files in this release were uploaded with provenance metadata.

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page