Nodal supervises Claude Code and Codex across isolated worktrees and human-gated integration. Their work comes back as a branch you review before anything merges.
Agents never edit your working tree. Session agents work in Nodal-owned git worktrees, pipeline agents in a staged clone outside the repo, and their work reaches you as a branch and a pull request.
Transcripts, approvals, run records, staged transfers, and committed work are durable across reconnects, worker restarts, crashes, and project reopens. A crash ends the live agent process, and Nodal tells you exactly what stopped rather than pretending otherwise.
Put Claude Code and Codex in the same room. Nodal runs structured positions, critiques, revisions, and comparison, then shows accepted points, unresolved disagreements, and evidence linked to the exact frozen context each model received.
Multiple models review the work. You make the call.
Refresh the token on every request where expiry < 60s. Simple, and it never serves a stale session.
That fires a refresh per in-flight request. Under concurrency you get a token stampede and the last write wins. Refresh once behind a lock.
Conceded. Single-flight refresh behind a mutex, everyone else awaits the same promise.
Every session keeps its transcript, its territory, and its model.
[ Runs ]Stage by stage, with the gate that stopped the run named.
[ Session detail ]Tool calls, diffs, and approvals in the order they happened.
[ Cost ]On the subscription you already pay for. Nodal resells nothing.
Merging is a human action that no autonomy setting can grant. Context sharing, spend and destructive calls pass through explicit gates, and approval is bound to the exact action and material you reviewed.
Resume managed work or start from a goal.
Rule on every gated action from one audit surface.
Every run, live and past.
Structured cross-model critique with frozen context.
Delegate an autonomous run with visible limits and controls.
Plans as objects, on an editable canvas.
Agents, branches, dependencies, locks, and contention.
Recurring runs and the windows they run in.
Spend per project and per run against a monthly budget.
What Nodal keeps from finished runs.
A separate mode for design projects.
Roles, integrations, settings, and policy.
Every agent session runs inside a default-deny macOS seatbelt fence. Writes reach two directories: the session’s own checkout, and a staging dir outside the repository. Reads start closed, so your home directory, your credential files, and git’s own administration are none of them openable by the process. Nodal keeps its state on your machine and records activity in a hash-chained event log whose head is stamped into the git commits it writes, so the history can be checked by something other than Nodal.
The fence covers the filesystem, not the network. The model CLIs reach it under your provider accounts, exactly as they do when you run them yourself.
The monthly budget tracks spend and warns. It does not block it; the enforced ceilings are the operator's.
Old audit entries age out under a retention window.
API-key mode stores your Anthropic key on your machine, encrypted by the macOS keychain, and it goes nowhere except Anthropic.
Claude Code and Codex produce work. Nodal coordinates, isolates, supervises, reviews, recovers, and integrates that work.
Nodal drives the CLI sessions installed on your machine, under your provider accounts. No keys to hand over, no inference resold.
Claude Code and Codex, through the CLI sessions you already have. Runs bill the subscription you already pay for; Nodal does not resell inference.
No. An agent can open a pull request; merging is a human action that no autonomy setting can grant.
Nodal keeps its state on your machine. The model CLIs reach the network under your provider accounts, exactly as they do when you run them yourself.
Beta 1 is free and invite-only, built for macOS on Apple silicon. The first cohort is limited to 20 to 50 developers.
Beta 1 is free, invite-only, and built for macOS on Apple silicon. It supports Claude Code and Codex through their existing CLI sessions. The first cohort is limited to 20 to 50 developers.
Request a beta invite→Cohort openings, release notes, and what changed in the build. Nothing else.
A local control plane for coding agents. Built by WhenLabs.