NabuCode · Agent terminal workspace
Close the app.Your agents keep running.
NabuCode runs your coding agents in a tiling terminal grid. A background daemon owns every session, so quitting the window detaches instead of killing — and you can pick the work back up from your phone.
SESSIONS LIVE IN A DAEMON, NOT IN THE WINDOW
01What's inside
A workspace built for running several agents at once.
Everything below ships in the app today. Each card carries the file it was written from.
Session status
- Working
- Needs you
- Idle
- Done
- Error
Eight panes, one grid
Split right or down, swap panes, maximise one, or drop a session into a zone to split it. Panes that scroll off the grid park in an off-grid strip instead of disappearing.
Five agent harnesses
Claude Code, Codex, Gemini and OpenCode each get a first-class integration, and generic CLI is the fifth — point it at any other agent command and the grid still tracks it. A plain shell is there for when you want no harness at all.
Panes that name themselves
A cheap model reads what a session is doing and writes the tab title, per harness and toggleable. The names survive a restart, so an eight-pane grid stays legible.
AI-drafted commit messages
The git panel hands your diff to an agent CLI already on your PATH — Claude Code, Codex, pi or your own command. It runs in a login shell on your machine; nothing is sent anywhere else.
Editor, git and worktrees
A CodeMirror editor with per-file indent detection and conflict checks, a full git panel with a commit-graph rail, and worktrees created and removed per session.
Launch presets
Save a command line, agent kind, environment, working directory and worktree policy under a name and an icon, with up to three one-tap prompts attached.
Nineteen built-in themes
Catppuccin, Dracula, Everforest, Gruvbox, Kanagawa, Nord, Rose Pine, Tokyo Night and more, plus your own themes and background images.
Starts from Finder
A FinderSync extension puts NabuCode at the top level of the folder context menu on macOS, so a project opens in a new session without a trip through the app.
A resource monitor built in
App and system CPU, memory, swap, core count, uptime and the heaviest processes — because you are the one deciding how many agents this machine can carry.
02The architecture
The app is a window. The daemon is the product.
Most agent tools die with the process that launched them. NabuCode splits the two, which is why a session can outlive the window that started it.
- 01
You lay out the grid
Start sessions from the desktop app — a preset, a Finder folder, or a bare shell — and arrange them across up to eight panes. This is the only place work gets started.
- 02
The daemon owns them
nabud holds the PTYs and every piece of persistent state. Closing a tab detaches from a session; it never kills it. Killing is something you have to ask for.
- 03
Your phone looks in
The companion app is a second thin view over the same protocol. Read what an agent is doing, answer the prompt that stopped it, and let it carry on.
03From your pocket
Supervise the run. Unblock it. Walk away.
Paired with a QR code
Scan the code the desktop app shows. The phone gets its own device identity and talks to your daemon over TLS, directly on the LAN or through the relay when you are out of the house.
Read what is happening
Every running session, its status dot and its live output — the same view the grid shows, on the device already in your hand.
Answer the thing that stopped it
An agent waiting on a yes-or-no is an agent doing nothing. Clear the prompt from the phone and it carries on without you walking back to the desk.
Built on Tauri 2 · One Rust daemon behind all of them
04FAQ
The questions that decide it.
Early access
Get told once, when there is a build worth installing.