toomux

Claude Code,
minus the babysitting.

Every session and account on one screen, in tmux. Handover instead of compaction. One Rust binary.

$ curl -fsSL https://toomux.com/install.sh | sh
$ toomux init --apply

Linux or macOS (Windows through WSL 2), tmux 3.2 or later, and Claude Code. Then press alt-s.

toomux
toomux work 5h 84% wk 64% personal 5h at limit · back 10pm
    enter open^a moveesc back? keys

    I run ten or so Claude Code sessions across two Max 20x accounts. At any moment one is waiting on a permission prompt I haven't seen, one has hit its limit, and one is 800k tokens deep, re-reading all of it on every call.

    I built toomux to deal with that. Everything in it I learned the hard way.

    two max 20x accounts, run to the limit
    205days

    196.0B tokens, $141.7K at API list prices, and plenty of it spent learning what not to do.

    #5 on ccgather · #20 on viberank

    short, sharp sessions

    Handover instead of compaction

    Every call re-reads the whole conversation. At 800k tokens that's $0.16 a call, or $6.40 if the cache has gone cold. On a Max plan it eats your limits instead. And the model gets worse at using what's in front of it as the context grows.

    When the context fills up, Claude Code compacts: it summarises the conversation and carries on, usually mid-task, and details get lost.

    toomux hands over well before that. Once a session passes 250k and finishes its turn, it writes a brief, saves what it learned to memory, and a fresh session picks up in the same pane. Nothing is summarised, and the old conversation stays searchable.

    beforewith toomux

    cost per 1,000 calls$153$58
    calls over 400k59.4%0.2%
    output tokens per dollar5,91712,709

    My own numbers from toomux tokens, at API list prices. I run handover at 200k.

    Context per call over a long stretch of work. Claude Code on its own climbs towards a full window, compacts mid-task and climbs again: 488k per call on average. With toomux each session hands over at the end of a turn: 165k per call on average.

    keeps going without you

    Voyages

    Tell a session what done looks like, and it keeps working until it gets there. You don't have to sit and watch it.

    /voyage the auth tests pass --check "cargo test auth" --budget 40

    That session works until the auth tests pass, proves it by running cargo test auth, and stops if it has spent $40. It hands over to a fresh session as it goes, and waits out a usage limit instead of stopping dead.

    how hard it pushes

    1. lighttakes the session's word for it
    2. steadywants to see the proof. The default.
    3. harda proof lap first: a clean re-run, and a read over its own changes
    4. relentlesstwo laps, the second trying to break it, then a sceptical review

    A check costs about $0.001 with Haiku.

    The ship sails towards the island as the work gets done. She drops anchor while the voyage waits on you or a usage limit, and lands when it's finished.

    one screen

    Every session, one screen

    Press alt-s anywhere in tmux: every session, sorted by what it needs from you, with the selected one live next to the list. Reply right there. Each one shows what it has cost and how long its cache stays warm, so you know when coming back to it will be expensive.

    alt-s from anywhere in tmux: toomux fills the terminal, on a session waiting for permission to run a command

    Rather stay in tmux?

    alt-b keeps the list down the side of any window, and the status bar tells you the moment something needs you.

    alt-b: the session list down the side of an ordinary tmux window, beside a session at work

    Out of room?

    When an account hits its limit, ctrl-a moves the conversation to one with room, in the same pane. alt-u shows when you'll hit the limit at your current pace.

    Every account's 5-hour and weekly windows, with pace and the past day

    remembers everything

    One memory for every session

    Every conversation is indexed as it happens, along with handover briefs and every project's Claude Code memory files. Any session can search all of it, in any project, so you don't have to explain things twice. toomux graph --open draws the lot: every project, the sessions that ran there, and the briefs they handed over with.

    The memory graph in the browser: every project as a cluster of its memory files and sessions, with chains of handover briefs running through the busiest ones

    Where the tokens went

    toomux tokens shows what your sessions used, what toomux saved, and who spent it. A one-line digest of yesterday arrives each morning.

    Nothing thrown away

    Transcripts are kept past Claude Code's 30-day cleanup, and memory files are fixed when you move a folder.

    out of the way

    Coming soon

    Get it

    $ curl -fsSL https://toomux.com/install.sh | sh
$ toomux init --apply

    Then press alt-s in tmux. Everything is on by default. Every key and setting is in the guide, and if it helps, a star on GitHub is appreciated.