agentbox

Install

There are two ways to run it: in the browser, or as a Mac app. Both need Node 22 and Claude Code or Codex installed and signed in.

In your browser. One command, nothing to install first:

npx agentbox-app

It starts on your machine and opens a tab. On Linux that open goes through xdg-open. Nothing is hosted: it listens only on 127.0.0.1, and the address carries a key that is new every run. Add --help to see the options. --no-open prints the address and leaves the browser to you.

From a checkout, build the screen once, then start it the same way:

npm install
npm run build
npx agentbox-app

As a desktop app. Build it from this repo. npm start is the desktop command on Omarchy and on a Mac:

git clone https://github.com/savannahfeder/agentbox.git
cd agentbox
npm install
npm start

On Linux, npm install puts agentbox on ~/.local/bin and adds the app to the launcher. The entry is $XDG_DATA_HOME/applications/agentbox.desktop (~/.local/share/applications when that variable is unset), and it runs agentbox. That command starts this checkout. Open the app from the launcher.

npm start builds the app and opens it. On first run it walks you through connecting Claude Code or Codex and choosing a folder to work in.

On macOS, the system may ask to let Terminal find devices on your local network. Agentbox does not need that, so Don't Allow is fine.

The chat window is the bottleneck

Today you run agents in chat windows and terminals, and you wait for each one to finish before you prompt it again. So the number of agents you can run is limited by the number of windows you can keep track of.

Models are now good enough that most tasks do not need watching. They need someone to review the work at the right moment. Agentbox drops the chat window and gives each agent a row in an inbox instead, so you can run far more of them than you could ever watch and only deal with one when it actually needs you.

How it works

1. File the work

Paste a list, send over a board of issues, or type one task. Each item becomes its own row, and each row is its own agent, already working.

2. Walk away

Nothing needs you while they run. Go to lunch. A row only comes back to you when its agent is done or stuck, so a hundred agents working is as quiet as one.

3. Come back to an inbox

Every row opens with what the agent did and what it wants from you, in two lines you can read at a glance. Most of the time the answer is yes. Press 1 and it merges, and the next one is already in front of you.

4. Answer however fits

5. Stay the person in the loop

Your job stops being watching agents work. It becomes reviewing what they made and deciding whether it is good enough. This agent got a failing test to pass by editing the test instead of the code, which is exactly the moment you want to be asked. Code changes open right beside the row.

What matters most goes first

Twenty agents means twenty things competing for your attention and for a limited number of running sessions. Agentbox keeps one order and uses it for both.

• Tag a task Urgent, High, Medium or Low, when you file it or later from ⌘K or Ctrl+K.
• Rank your projects once by dragging them into order. A project's place counts for more than any single task's tag, so your most important project never waits behind a side one.
• The order decides who starts. When there are more tasks than session slots, the queue starts the most important first. An answer you have already given wins a tie against new work, so replies never pile up.
• Urgent rises to the top. Urgent rows sit above everything else in the inbox under their own heading.
• Only your tags count. An agent cannot promote its own work. If it says its task is urgent, that is ignored.

Built for the keyboard

Fifteen skins, each in light and dark, from plain slate to woodblock and riso prints. Press ⌘K or Ctrl+K and type "theme". Ctrl+K is the same palette on Linux, where there is no Command key.

Runs on the plan you already have

Agentbox drives Claude Code and Codex on your own machine, signed in with your own subscription. When you first open it, it finds the agents you have already set up and offers to bring them in. There is no server, no account to make, and nothing new to pay for.

Reference

zero.config.json in the repo root, gitignored and machine-specific. Every default works unset and they all live in main/config.mjs. The ones that matter:

• storeRoot: where the store lives. On macOS this defaults to a folder named after the app in your home directory. On Linux it defaults to $XDG_DATA_HOME/agentbox, which is ~/.local/share/agentbox when that variable is unset.

• claudeBin: the binary to run. The app finds claude itself if you leave this alone.

• maxConcurrentSessions: how many agents run at once. The queue absorbs the rest, in priority order.

• sessionArgs: what a spawned session may do. The default grants only the store tools, so an agent can read the store, file questions and update work items, and nothing else. To let agents edit code and run commands, opt in:

  { "sessionArgs": ["--allowedTools", "mcp__agentbox", "--permission-mode", "acceptEdits"] }
  

  That grant is yours to make deliberately. The app never escalates it for you.

• personalProducts: workspaces that are your own tasks rather than a product, for example ["personal"]. Sessions there get your message and nothing else, and replying resumes the same session, like a thread.

• diagnostics: false turns off the counts described below.

Nothing, unless you are running a build that was signed and released with a PostHog key baked into it. A build made from this repo has no key, so a clone and a fork are silent, and with no key the whole path is off at every send.

A released build counts eighteen things, and they are counts:

• the app was opened
• the app was used today, once a day
• a setup step was reached, by its number
• first run finished
• a repo was connected
• a