macOS · Swift · Personal · Beta 2026 · Reza Ilham

CatBoard

About this note

A Kanban board for the coding agents you already use. Each card gets its own git worktree, and you stay the one who decides what merges.

Chapter 1

Why a board

I wanted something a working engineer already knows. People in companies live in Kanban. CatBoard is that board for AI coding agents, and you are the boss. You pick the work, you watch the run, you decide what merges.

Chapter 2

How a card moves

It's a native macOS app written in Swift 6. You choose a local git repo, describe a task, and pick an agent CLI you already have installed: Claude Code, Codex, Antigravity, Cursor, or OpenCode. Moving the card to In Progress creates a branch and a dedicated git worktree, spawns the CLI process headlessly in that directory, and streams stdout and stderr back to the card. Five cards can build and run tests at the same time without touching your main checkout. You read the summary and the diff on the board, then merge when it looks right.

01 · One card = one isolated git branch
Todo
In Progress
Review
Merged
CB-14

Fix pipe exit hang

claude · Swift 6

You (main) main checkout Agent (wt/cb-14) isolated folder Keep coding here — never switches branches Agent edits & runs tests here ✓ Merged
1 · Your main checkout Safe · Untouched
branch: main ~/Work/repo

Your editor stays on main. No git stash, no branch switching, and no broken builds while the agent runs.

2 · Agent worktree Running tests

Folder: .catboard/worktrees/cb-14

$ claude "Reconcile pipe EOF with exit code"

✓ 4/4 unit tests passing in sandbox

Moving a card to In Progress creates a separate folder and git branch for the agent. You keep working in your main checkout without interruption.

CatBoard ships outside the Mac App Store because it spawns local CLI processes and works across arbitrary git repositories. The agents and the board data stay on the Mac; nothing is uploaded.

Chapter 3

Cards used to be typed

I wrote every task by hand at first. Skills and MCP replaced that. You interview the problem with an agent first, then turn those decisions into a batch of tickets with file scope, acceptance criteria, and blocking edges between cards. Scoping the files and dependencies before any run starts keeps parallel agents from editing the same module at the same time. You review the batch in the app before importing it onto the board.

02 · Prevent agents from editing the same file
Agent cards on board 0 shared files — safe to run in parallel Repository files
ProcessRunner.swift Locked · CB-21
PipeMonitor.swift Locked · CB-21
GitDiffParser.swift Locked · CB-22
CardCellView.swift Queued · CB-23
CB-21 locks ProcessRunner.swift and PipeMonitor.swift. Because CB-22 edits a completely different file, both agents run at the same time with zero merge conflicts.

Chapter 4

Stuck in progress

For a while, agents would stop on their own and the card stayed In Progress even though the work was done. Some CLI runners exit after their final turn without flushing a clean completion event, or leave child processes holding the pipe open. CatBoard now reconciles process exit codes and pipe closure against the worktree's git status before marking a run finished or failed. A status you have to second-guess makes the whole board hard to trust.

03 · Know when an agent is truly done
In Progress Finished
Review Ready for you
CB-14 · claude ✓ Diff ready

Fix pipe exit hang

Moved to Review automatically

Check 01 ✓ Exit 0

Agent CLI finished

Main agent process finished its final turn.

Check 02 ✓ Closed

Leftover background pipe

Lingering helper pipe force-closed by CatBoard.

Check 03 ✓ Verified

Worktree git commits

2 new commits verified in isolated worktree.

Even when a background helper leaves the output pipe open, CatBoard closes it, verifies the worktree commits, and moves the card to Review immediately.

Chapter 5

What I open now

When I want an agent to run on its own, CatBoard is the better place. The card, the worktree, and the diff are enough. When I want to stay in the work and steer it live, I open Orca, and sometimes T3. Both have a lot of surface I never touch.

The next thing I want on the board is a way to chat with an agent and shape the task with it before the run starts, instead of writing the card first and only then watching it execute.

Chapter 6

CatAgent

CatAgent is the other product. CatBoard helps one person finish their own work, whether that's a personal project or their slice of a company repo. CatAgent is for the team as a whole, built on top of the Jira epic they already have. Together with SliceBill, they form the three setups in my research note on human gates.