NodumNodum
Early preview · v0.6

Mission control for a fleet of coding agents.

Nodum puts every Claude Code and Codex session on a live graph, down to the subagents, MCP connections, and background jobs they spin up. Approvals collect in one inbox, you set a budget for each agent, and when one runs away you shut it down on the spot.

macOS · Linux · Windows · Node.js 20.11+

Nodum — localconnected

Everything your agents do, in one window.

Once you're running more than a couple of agents at a time, keeping track of them gets hard fast. Nodum shows what each one is doing, collects their approvals in one place, and gives you a way to stop or undo any of them. It works with both Claude Code and Codex.

Live graph

Every session, subagent, MCP server, and background bash shows up as a node, and it moves as they do. There's no refresh button to hit.

Approval inbox

Every permission request from every agent lands in one queue, sorted by risk. Approve or deny them in batches, or write a rule once and let the routine ones clear themselves.

Guardrails

Nodum blocks the commands you never want run (rm -rf /, fork bombs, raw disk writes) and holds the merely risky ones for you to check first. Worth having when an agent is working unattended.

Agent control

Kill a runaway agent on the spot. Put a token or dollar budget on each one. Let Autopilot wave through the safe actions, or roll back what an agent did with a single click. All of it gets written to the audit log.

Claude Code and Codex

Codex CLI sessions show up on the same graph as your Claude Code ones, transcripts and all. Toggle them on or off, or narrow the view to whatever's run recently.

Audit log

A record of every approval, guardrail hit, budget stop, and rollback. Search it, filter it down, and export whatever's left.

Fleet dispatch

Hand one task to a set of repos and Nodum spins up an agent for each. You watch them all on the graph, and their approvals come back to the same inbox.

Custom agents

Save an agent profile once (its instructions, model, and tool policy) and reuse it. Spawn or dispatch a fleet from it, or export it to Claude Code's own ~/.claude/agents folder.

Activity timeline

A running feed of what's happening across every agent: fleets going out, subagents starting, approvals decided, guardrails firing, sessions wrapping up.

Transcripts at a click

Click a node to read its full history, from the messages to the tool calls, token counts, and roughly what it cost. Even a 5,000-line transcript scrolls smoothly.

Spawn, resume & terminals

Start a new session, managed (SDK) or interactive (PTY), without leaving the app. Pick an old one back up with one click. It all sits in color-coded tabs.

File tracking

Watch every Read, Edit, and Write hit your project, with a git diff and preview for each file a session touches.

See it

What you actually look at.

The parts of Nodum you'll end up spending most of your day in.

Approval inbox

Every approval in one place.

No more tabbing between agents to answer one prompt at a time. Every request lands in a single queue, sorted by risk and grouped by repo. Approve or deny them in batches, or set a rule once and let the routine ones clear themselves. The dangerous requests get flagged before they reach you.

Activity timeline

A running feed of what every agent did.

Fleets going out, subagents starting, approvals decided, guardrails firing, sessions ending: it all shows up on one color-coded timeline. Step away, come back, and scroll up to see what your agents got up to while you were gone.

Custom agents

Reusable agents, not copy-pasted prompts.

Give an agent a name, instructions, a model, and a tool policy, then save it. Flip it to read-only and it loses write and shell access. Spawn a single one or dispatch a whole fleet from the profile, and if you want it elsewhere, export it to Claude Code's ~/.claude/agents.

Transcript drawer

The whole conversation, one click away.

Open any node for the full transcript: the messages, tool calls, tool results, token counts, and what it cost. Search across thousands of lines and it keeps up.

File tracking

Every read, edit, and write, with diffs.

Nodum follows each session as it works through your project. Click a file for a git-style diff, right there in the panel. You don't have to comb the transcript to work out what changed.

How it works

Local-first by design.

Nodum reads the state Claude Code already keeps on your machine. There's no daemon and no cloud service, and it only sends telemetry if you turn it on.

Reads

Files Claude Code already writes

Session lockfiles, per-session transcripts, subagent transcripts, and IDE/MCP locks under ~/.claude/. Nothing exotic; it's state that's already sitting on your disk.

Caches

A tiny offsets file

It lives in your OS app-data directory so Nodum doesn't have to re-read every transcript on relaunch. Delete it whenever you want a clean scan.

Sends

Nothing unless you opt in

Nodum makes no network calls on its own. The first time you open it, it asks whether to share anonymous usage: feature counts only, never your code, your prompts, or your file paths. Sessions you spawn use your existing Claude credentials and talk to Anthropic exactly the way the claude CLI does.

Quick start

Download and launch.

Grab the build for your platform and open it. Any Claude Code sessions already running on your machine show up within a few seconds.

  • Requires macOS · the claude CLI on your PATH. Windows and Linux coming soon.

Latest release

Follow for updates

Know when there's a new build.

New releases, new features, and changelog notes, posted as they land.

Follow on LinkedIn