Ntwine

One tab for all your coding agents.

Run Claude Code, Codex and any ACP agent side by side. When one needs you, it becomes a card in a single queue.

Get started
Ntwine focused on one project: the prompt box and the project's threads on the left, and on the right the first queue card, where an agent asks whether the settings store should use SQLite or a JSON file, with numbered options and a countdown to the recommended pick.

Drives the agents you already use

  • Claude Code
  • Codex
  • OpenCode
  • Gemini CLI
  • Copilot CLI
  • Cursor
  • goose
  • Qwen Code

Principles.

Kept from the original design. Every feature is held to them.

The agent decides.

A thread's state is its agent's own last word. Ntwine only checks that it holds up.

Ntwine never answers for it.

Outside a short, listed set, nothing is answered, parked or withdrawn on an agent's behalf.

Every card is yours to act on.

Nothing enters the queue just to be dismissed, and a running thread never does.

Five bands, never lost.

Pinned, Queue, Running, Snoozed, Done. Every thread is in exactly one.

One project at a time.

A project's board is the default. All projects is one click away.

Nothing of its own.

No model, no cloud and no workflow. Just your CLIs on your sign-in, on localhost.

All the principles

One queue, not ten terminals.

A worker keeps going until it reaches something only you can settle. Then it hands back a question with numbered options and its own recommendation, and you answer with one keystroke.

Threads waiting on their own sub-agents, on CI or on a review stay out of the queue, so nothing shows up just to be dismissed. If the agent marks a question as safe to default and you leave it alone, it takes the recommended option after 10m.

How the queue works
A question card asking whether the settings store should use SQLite or a JSON file, with option A marked recommended, a row for typing something else, and below it a countdown to the recommended pick.

Waits that outlive the agent.

An agent waiting on CI, a review, a reporter’s reply or another thread registers a watch and rests outside your queue. Ntwine holds the watch, not the agent’s session, so it lasts as long as the server does. That can be days, or years.

When something lands, the thread wakes up and handles it on its own. Every thread has an @handle, so agents can read, message and wait on each other the same way.

Watchers
acme-api
  @settings-store  resting · watching acme/api#391

  Tue 14:02   CI passed
  Thu 09:41   review requested
  Thu 11:17   2 review comments
              ↳ @settings-store wakes and answers them

  @parser-review   waiting on @settings-store
              ↳ wakes when it hands back

One server, every project.

One server serves every repo on your machine, and each one gets its own board. Run npx ntwine in a second repo and it joins. All projects is one click away and shows every board’s work at once.

Each agent runs in its own background process. Close the tab or stop Ntwine and it keeps working. When you relaunch, Ntwine reconnects.

Projects
The All projects page: billing-worker, marketing-site and acme-api each list their threads on the left, and the cards from every project are queued on the right.

Built for the long run.

The parts that let a thread work without you.

SnoozePark a card until tomorrow, with what to do when it wakes.Goals“Keep going until CI is green”, re-sent at every rest.Schedules“Every weekday at 9am” starts a fresh thread each time.Time limits“2h”, and the agent plans the best result by then.HandlesThreads read and message each other by @handle.SpinoffA new thread from any card, carrying its context.TerminalsA shell in the folder the agent works in, on t.GitHubIssues into threads, and watchers that wake on CI.Your editorA VS Code sidebar that sends your selection along.

Schedules, in plain words.

Type “every weekday at 9am triage new issues” and the prompt box reads the schedule as you type and shows when it next runs. Each run starts a fresh thread that lands in the queue like any other.

Schedules
The prompt box reading 'every weekday at 9am triage new issues' as a schedule: the phrase highlighted, the send button turned into a repeat button, and a strip reading 'Every weekday at 9am · next Thu Oct 8, in 22h'.

Go until 3:30.

Give a thread “2h” or “15:30”. The agent plans the best result it can hand over by then, gets reminders as time runs low, and gives its sub-agents a share. Meanwhile, the card counts down.

Time limits
A queue card whose header shows a 43m left countdown, with the time-limit panel open: +15m, +30m and +1h, a field for a new limit, and Remove time limit.

From your phone, too.

Press R in the terminal running Ntwine and pick how your phone should reach it. A private ntwine.app name needs no account and nothing installed.

Either way, Ntwine stays on localhost. The first visit from each device needs a single-use sign-in link, which it shows as a QR code.

Remote access
npx ntwine
  Reach this board from anywhere

  ❯ Private name        no account, nothing to install
    Cloudflare Tunnel   a domain you own
    Tailscale           your tailnet
    Something else      any proxy you run
    Off                 loopback only

Give it a try. It takes one command.

Read the quick start