Run a dozen coding agents at once. Maxxwell keeps each one moving for you and brings you only what truly needs your attention.
Maxxwell
~/src/rindler-mvp
Find a lane, a branch, a file…⌘K
7 running
Workspaces
Rrindler-mvp9
Mmaxxwell-ide2
Ssite1
Views
Needs you2
Running7
Stalled1
Done today14
Needs you 2
R kv-cache eviction policy feat/kv-evict busy 14m, no file writesasked a question +0 −014m
R flaky auth e2e fix/auth-e2e exit 137 · third attemptrunner OOM +18 −42m
Running 7
R sitemap canonical tags fix/sitemap-canon writing tests6 files +142 −386m
R billing webhook idempotency feat/wh-idemrunning suite3 files +61 −1211m
M typed config loader refactor/configreading 14 files +9 −33m
R docs: gate semantics docs/gatesqueued behind 2 ——
R search index backfill chore/backfillshard 3 of 8 +24 −021m
S mobile nav overflow fix/nav-overflowwaiting on build +7 −78m
M porter deploy retry fix/porter-retryqueued behind 1 ——
Done today 14
11 merged · 2 awaiting review · 1 abandoned ⌄
Needs you · lane 07
Busy for 14 minutes with nothing to show for it.
142 tool calls since the last file write. It is re-reading the same three files.
Working14m 08s
Last file write13m 51s ago
Diff+0 −0
Tool calls142
“Two schema options here — evict by LRU or by token budget. Which do you want?”
› 142 tool calls · 3 messages
Read src/cache/evict.ts×41
Read src/cache/index.ts×38
Grep "evictionPolicy"×29
Take overAnswerKill
12 lanes · 2 need you
the babysitting problem
Running agents is easy. Keeping them on track isn't.
More agents should mean more progress, not more windows to watch.
You give it the work
Write what you want done. Maxxwell opens one lane per task and starts watching them.
Maxxwell
~/src/rindler-mvp
Find a lane, a branch, a file…⌘K
7 running
Workspaces
Rrindler-mvp9
Mmaxxwell-ide2
Ssite1
Views
Needs you2
Running7
Stalled1
Done today14
Needs you 2
R kv-cache eviction policy feat/kv-evict busy 14m, no file writesasked a question +0 −014m
R flaky auth e2e fix/auth-e2e exit 137 · third attemptrunner OOM +18 −42m
Running 7
R sitemap canonical tags fix/sitemap-canon writing tests6 files +142 −386m
R billing webhook idempotency feat/wh-idemrunning suite3 files +61 −1211m
M typed config loader refactor/configreading 14 files +9 −33m
R docs: gate semantics docs/gatesqueued behind 2 ——
R search index backfill chore/backfillshard 3 of 8 +24 −021m
S mobile nav overflow fix/nav-overflowwaiting on build +7 −78m
M porter deploy retry fix/porter-retryqueued behind 1 ——
Done today 14
11 merged · 2 awaiting review · 1 abandoned ⌄
Needs you · lane 07
Busy for 14 minutes with nothing to show for it.
142 tool calls since the last file write. It is re-reading the same three files.
Working14m 08s
Last file write13m 51s ago
Diff+0 −0
Tool calls142
“Two schema options here — evict by LRU or by token budget. Which do you want?”
› 142 tool calls · 3 messages
Read src/cache/evict.ts×41
Read src/cache/index.ts×38
Grep "evictionPolicy"×29
Take overAnswerKill
12 lanes · 2 need you
It finds the one that is stuck
Lanes rank by what they have actually landed, so the one burning time with nothing to show drops to the bottom.
Maxxwell
~/src/rindler-mvp
Find a lane, a branch, a file…⌘K
7 running
Workspaces
Rrindler-mvp9
Mmaxxwell-ide2
Ssite1
Views
Needs you2
Running7
Stalled1
Done today14
Needs you 2
R kv-cache eviction policy feat/kv-evict busy 14m, no file writesasked a question +0 −014m
R flaky auth e2e fix/auth-e2e exit 137 · third attemptrunner OOM +18 −42m
Running 7
R sitemap canonical tags fix/sitemap-canon writing tests6 files +142 −386m
R billing webhook idempotency feat/wh-idemrunning suite3 files +61 −1211m
M typed config loader refactor/configreading 14 files +9 −33m
R docs: gate semantics docs/gatesqueued behind 2 ——
R search index backfill chore/backfillshard 3 of 8 +24 −021m
S mobile nav overflow fix/nav-overflowwaiting on build +7 −78m
M porter deploy retry fix/porter-retryqueued behind 1 ——
Done today 14
11 merged · 2 awaiting review · 1 abandoned ⌄
Needs you · lane 07
Busy for 14 minutes with nothing to show for it.
142 tool calls since the last file write. It is re-reading the same three files.
Working14m 08s
Last file write13m 51s ago
Diff+0 −0
Tool calls142
“Two schema options here — evict by LRU or by token budget. Which do you want?”
› 142 tool calls · 3 messages
Read src/cache/evict.ts×41
Read src/cache/index.ts×38
Grep "evictionPolicy"×29
Take overAnswerKill
12 lanes · 2 need you
It shows you where the time went
Not a status word. The question it is stuck on, and the calls it burned getting nowhere.
Maxxwell
~/src/rindler-mvp
Find a lane, a branch, a file…⌘K
7 running
Workspaces
Rrindler-mvp9
Mmaxxwell-ide2
Ssite1
Views
Needs you2
Running7
Stalled1
Done today14
Needs you 2
R kv-cache eviction policy feat/kv-evict busy 14m, no file writesasked a question +0 −014m
R flaky auth e2e fix/auth-e2e exit 137 · third attemptrunner OOM +18 −42m
Running 7
R sitemap canonical tags fix/sitemap-canon writing tests6 files +142 −386m
R billing webhook idempotency feat/wh-idemrunning suite3 files +61 −1211m
M typed config loader refactor/configreading 14 files +9 −33m
R docs: gate semantics docs/gatesqueued behind 2 ——
R search index backfill chore/backfillshard 3 of 8 +24 −021m
S mobile nav overflow fix/nav-overflowwaiting on build +7 −78m
M porter deploy retry fix/porter-retryqueued behind 1 ——
Done today 14
11 merged · 2 awaiting review · 1 abandoned ⌄
Needs you · lane 07
Busy for 14 minutes with nothing to show for it.
142 tool calls since the last file write. It is re-reading the same three files.
Working14m 08s
Last file write13m 51s ago
Diff+0 −0
Tool calls142
“Two schema options here — evict by LRU or by token budget. Which do you want?”
› 142 tool calls · 3 messages
Read src/cache/evict.ts×41
Read src/cache/index.ts×38
Grep "evictionPolicy"×29
Take overAnswerKill
12 lanes · 2 need you
You answer it. The lane moves again.
Answer in the window you are already in, and the flat line starts moving.
Maxxwell
~/src/rindler-mvp
Find a lane, a branch, a file…⌘K
7 running
Workspaces
Rrindler-mvp9
Mmaxxwell-ide2
Ssite1
Views
Needs you2
Running7
Stalled1
Done today14
Needs you 2
R kv-cache eviction policy feat/kv-evict busy 14m, no file writesasked a question +0 −014m
R flaky auth e2e fix/auth-e2e exit 137 · third attemptrunner OOM +18 −42m
Running 7
R sitemap canonical tags fix/sitemap-canon writing tests6 files +142 −386m
R billing webhook idempotency feat/wh-idemrunning suite3 files +61 −1211m
M typed config loader refactor/configreading 14 files +9 −33m
R docs: gate semantics docs/gatesqueued behind 2 ——
R search index backfill chore/backfillshard 3 of 8 +24 −021m
S mobile nav overflow fix/nav-overflowwaiting on build +7 −78m
M porter deploy retry fix/porter-retryqueued behind 1 ——
Done today 14
11 merged · 2 awaiting review · 1 abandoned ⌄
Needs you · lane 07
Busy for 14 minutes with nothing to show for it.
142 tool calls since the last file write. It is re-reading the same three files.
Working14m 08s
Last file write13m 51s ago
Diff+0 −0
Tool calls142
“Two schema options here — evict by LRU or by token budget. Which do you want?”
› 142 tool calls · 3 messages
Read src/cache/evict.ts×41
Read src/cache/index.ts×38
Grep "evictionPolicy"×29
Take overAnswerKill
12 lanes · 2 need you
how it works
Keep your agents working together.
Run the coding tools you already use, including Claude Code and Codex. Add a managing agent to coordinate the work, with every session visible in Maxxwell.
Follow each agent
See session activity, context usage, and requests for your attention.
Give work direction
Brief a managing agent to check progress and follow up with the others.
Focus your attention
Review questions and blockers without hunting through every terminal.
Return to the work
Open any session to see its progress and continue where you left off.
get maxxwell
Put your agents to work.
Download Maxxwell for your computer and bring your coding agents into one workspace.
prefer the terminal? install the CLI
$ curl -fsSL https://maxxwell.dev/install.sh | sh
Run maxxwell runtime to see which coding agents are installed.
Free to use. Bring your own coding agent subscriptions or API keys.