Nob
Open source · runs on your machine

Say what you want done. Get the result back.

Nob is an agent platform built on Claude. Type a request in plain words and walk away: agents plan it, build it on your machine and check it against your own build and tests, without stopping to ask. You get one result back — what was done, how it was checked, what was assumed — and the work waits on its own branch for one Merge.

Code runs on
your machine, in its own git worktree
Ask from
the dashboard, Claude Code, your phone
Three modes
HITL: you drive, every step waits for you · Auto: you approve the plan and answer blockers · YOLO: a software factory nobody watches
Every request ends in
one result: what it did, how it checked, what it assumed
License
AGPL-3.0 server · MIT worker
Live consoledemo · no server behind it
Spec3 criteria

Dark mode toggle

Acceptance criteria
  1. AC1User can switch between light and dark
  2. AC2Preference survives a reload
  3. AC3Toggle is visible in the navbar
Task consoleQueued

Pick a spec and dispatch it. The console fills with the records a real task produces.

How it runs
  1. 01

    Say what you want done

    One line in the dashboard is enough. Nob reads your code, sizes the request, and plans a big one as several tasks on its own.

  2. 02

    Walk away

    Nobody is asked anything along the way. When an agent hits a question it takes its best reading, writes down the assumption, and keeps going.

  3. 03

    It runs where your code is

    A driver agent gets a brief, works in a fresh worktree, runs your gate command, and posts checkpoints; you can steer it mid-run. The server records claims; it never touches your files.

  4. 04

    Get the result back

    One email when it is done: what it did, the checks it ran, the assumptions it made and anything it could not check. The work waits on its own branch for one Merge.

Two ways to run work
In a Claude Code sessionAttended

Add the Nob MCP server to your Claude Code config with an API key from the dashboard. Every dispatched task runs in a spawned subagent, never in the conversation you are typing in.

/nob  Add a dark mode toggle
      ## Acceptance Criteria
      1. ...

Claude Desktop can connect too, but it has no way to spawn a subagent, so it can read and plan without dispatching.

On a paired workerNo session needed

Settings → API keys → Connect a machine hands you a one-time command. Paste it on the machine that holds your code and it pairs, registers your checkouts as projects, installs a background service, and starts polling.

curl -fsSL https://github.com/n0b0dd/nob-worker/releases/latest/download/install.sh \
  | sh -s -- connect <PAIRING-CODE> --server https://api.ahhnob.com/mcp

Carries its own Node and Claude runtime, needs no database and no inbound ports, only writes inside the roots you list, and updates itself between tasks. On Windows the same panel hands you a PowerShell line instead (beta; needs Git for Windows). nob-worker on GitHub.

Built to hand back results
Done

A result you can trust without reading every line

Every request comes back with the real output of your build and test commands, an independent check of whether it does what you asked, and the assumptions it made while nobody was watching.

Planning

Big requests plan themselves

A request too big for one agent becomes a plan of dependent tasks that run one after another on a single branch, re-planning when a task fails. You merge the whole thing once.

Lands when it passes

Your checkout stays yours

Work happens on its own branch in its own worktree. In Auto, passing work within your scrutiny band lands on its own and anything heavier waits for you. Want a say along the way? Work in HITL.

Paired

Runs without a session open

Pair a machine with one command. It picks up what you hand off without a Claude Code session, survives reboots, updates itself, and rotates between Claude accounts as they cool down.

Metered

Cost you can see

Token usage and dollars are recorded per task, main run and subagents alike, with a usage meter that mirrors your Claude plan limits.

Run it your way

The whole product is in the repository — there is no private tree and no license check. Paying for hosting buys operations, not features.

Self-host

Free

Every feature, no limits

  • Server, dashboard, worker and team features — all in the repo
  • No seat cap, no metering, no phone-home
  • Bring your own Postgres; deploys on free tiers too
  • AGPL-3.0 server and dashboard, MIT worker and shared types
View the source
Managed hostingRecommended

Solo and Team plans

Same code, we run it

  • Always-on MCP server and Postgres, reachable from any machine
  • Migrations, backups and notification delivery handled
  • Sign in with email, Google or GitHub; invite your team
  • Pays for operations — every feature is in the open-source repo
Create an account