Your tasks, one keystroke away.

## why monoban

Simple on purpose.

Most boards keep growing until managing the tool is a job of its own. monoban keeps what a board needs, and makes that fast.

@@ what we left out, on purpose @@- sprints, story points and burndown charts- required fields and custom workflows- a setup wizard before your first task- notification badges asking for attention+ projects → columns → tasks+ a title and a description, with checklists from - [ ]+ a column limit, when you want one+ every action one key away

• ⌘K

  Every action has a key

  The command palette lists every action with its shortcut beside it, so you learn the keys by using it. The mouse still works: drag anything anywhere.

• n↵

  Capture is instant

  Press n, type, press enter. The input stays open for the next task. No form, no dialog, no losing your train of thought.

• ↵

  One screen

  A task opens beside the board, like a tab in your editor. The board never goes away, and j and k walk through tasks with it open.

• ●

  Calm by default

  Monochrome, one monospace font. Colour shows up only when it means something: a column, your selection, a limit you went past.

• u

  Undo, not “are you sure?”

  Delete a task and bring it back with u. Only changes that touch many tasks at once ask before they happen.

• synced

  Never waits on the network

  Every change shows up the moment you make it and saves in the background. The status bar says saving… and then synced.

## one board

One board. Three ways in.

Plan in the browser, work from your terminal, hand tasks to an agent. Every change lands on the same board, in step, whichever way it came in.

## keys

Learn it in a minute. Keep it for years.

Ten keys cover almost everything. Arrows always work; vim keys are on by default and you can turn them off on any device. Forget one? ⌘K finds any action and shows its key.

## agents

From a plan to a pull request.

monoban works with the coding agents you already use. Yours turns a plan into tasks on the board. Then press R on any of them: an agent does the work on your machine and opens the pull request.

> let's plan invoices for the account page⏺ I read the board first (monoban list --json). Add these 4 tasks to SHOP?phase-1 Add the invoices table and its API routephase-1 Show invoices on the account pagephase-2 Email a receipt when an invoice is paidphase-3 Remove the old billing page> yes, and drop the last one for now⏺ monoban add "Add the invoices table and its API route" -t phase-1 -d -Added SHOP-21 to To do⏺ Added SHOP-21…SHOP-23. Shall I keep them current as I go?> 

• agentpipePlans, implements and verifies in steps; moves and comments on the task itself.$ monoban agentpipe install
• Claude Codeclaude -p in auto mode: a classifier reviews what it does, and nothing waits for you.$ npm install -g @anthropic-ai/claude-code
• Codexcodex exec in its sandbox: it writes in the folder, with the network off unless you say.$ npm install -g @openai/codex

• poll

  It asks; nothing comes in

  The runner polls for work. No open ports, no tunnels, no inbound connections.

• git

  Only in your clone

  A run works only in a checkout of the task's project, on the task's own branch. Uncommitted changes there? It won't start.

• sandbox

  Agents keep their guard rails

  Claude Code runs in auto mode, a classifier reviewing each action. Codex stays in its sandbox, offline unless the run asks.

• --confirm

  You can say no

  Start the runner with --confirm to approve each run in the terminal. Cancel from the task, or Ctrl-C.

try it in the live demo: open a task and press R ↑how runs work, step by step →

## security

Your work stays yours.

A task board ends up holding plans, bugs and notes you wouldn't post in public. monoban treats them that way.

• rls

  Locked down in the database

  Every read and write runs as you, under Postgres row-level security. Your projects are yours alone.

• auth

  Sign-ins that are hard to fake

  Sign in with Google, a password, or a one-time link sent to your email. A password has at least 12 characters, upper and lower case, a digit and a symbol, and changing it takes the current one. A bot check guards the sign-in form, and you get an email when your password changes.

• sha256

  Only hashes of tokens

  CLI sessions and personal access tokens are stored as hashes. Sign out any device, or revoke any token, in one click.

• mail

  You hear about new sign-ins

  Each time a CLI signs in to your account, you get an email saying which device and from where, with a link to sign it out.

• offline

  On your device, until you sign out

  To work offline, your browser keeps the boards you open and the changes not sent yet, never a token or your notes. Settings › This browser lists them and removes them; signing out deletes them.