Your local kanban board for coding agents, from backlog to delivery.

The columns do the work. Drag a card into Development and an agent starts. Drag it into Approved and the merge queue runs. Agents work in parallel, each on its own branch.

Download Kanzai free See how it works →

Start using Kanzai for free. No account required.

macOS · Windows x86_64 · Linux AppImage x86_64 · Linux deb x86_64 · arm64 builds

Kanzai · Petshop

Petshop ⚙ ✕

ACME Website ✕

Backlog

Ready

Development 3

Retry failed webhooks

PET-214backendworker

WORKING 4m 12s

You · 2h ago

Rotate auth tokens server-side

backendfrontendworker

Deploy to test Open PR Migrate…

WORKING 11m 03s

You · 4h ago

Improve SEO

frontend

WORKING 16m 21s

You · 1h ago

Drop the legacy /v1 client

frontend

WORKING 1m 47s

You · 30m ago

Review 2

Move price formatting to the server

backendfrontend

unread

+188−523 ✎

Agent · 8m ago

Signup form validation

frontend

+40−7no comments

You · 2d ago

Approved 2

Cap concurrent sessions

backend

⚠Stale · conflicts

backend/main moved 4 commits since you signed off, and no longer merges cleanly.

Rebase

You · 2h ago

Done

Rotate auth tokens server-side

kanzai/9f21-auth-rotate ← main

Deploy to test Branch and check out

Task

Files

Terminal

~/.kanzai/projects/petshop/work/9f21/petshop-api claude-opus-5

Transcript Terminal

❯Rotate the refresh tokens on the worker schedule too.

● Read src/auth/tokens.ts

⎿ 214 lines

● Edit src/auth/tokens.ts

⎿ Applied

● Bash npm test -- auth

⎿ 24 passed, 0 failed

● Edit worker/src/rotate.ts

⎿ Applied

Rotation now runs on the worker schedule. The API only reads the tokens.

● Bash npm test -- worker

❯ Queue a message for the next turn… ⏎ queue · ⎋ interrupt

Sends after the current turn. Interrupt Move to Review

Project assistant Petshop · 3 repos read-only WAITING auto Claude Code opus ▾ Clear ⌘J

❯split PET-214 into cards, then start everything about billing

● getJiraIssue PET-214

● Grep backend/src/billing

⎿ 14 matches

● create_task ×3

⎿ Dunning retry window · Proration on plan change · Invoice PDF locale

Filed three. Each names the file and the function it touches.

⚠ Allow move_task? Kanzai · asked every time

Move 3 tasks to Ready: Dunning retry window, Proration on plan change, Invoice PDF locale.

Development is at 3 / 4, so one starts now and two wait in Ready.

Yes No, tell it what to do auto mode is off

❯ Ask about the board or add work… ⏎ send · ⎋ collapse

Spend less time juggling terminals and branches. See every task, diff, review, and merge in one place.

BUILT FOR PARALLEL WORK

Run agents side by side

Start several cards at once. The board shows which agents are working, waiting, or ready for your review.

Isolated by default

Every card gets its own session, worktree, and branch. Agents can change the same repo without stepping on each other.

Review without switching tools

Read the diff, comment on individual lines, and send all your feedback back to the agent in one go.

Merge on your terms

You choose the order of the merge queue. A card that has fallen behind shows how far behind it is, whether it conflicts, and a Rebase button. If something fails, Kanzai stops and shows exactly what made it in.

Work across repos

Connect all the repos a project needs. One card can span several of them while Kanzai keeps the branches together.

Pick up where you left off

On macOS and Linux, sessions keep running in tmux even when Kanzai is closed. Reopen the app and carry on with the same prompts, questions, and plugins.

Turn tickets into clear tasks

Connect Jira or Linear through MCP. The project assistant reads the ticket and your repos, then creates focused cards that point to the relevant code.

Set what a column does

Add the columns your team already uses. Set what each column does when a card moves in: open a pull request, request a review, deploy to test, run a command, or prompt an agent.

Stack one card on another

A card can wait for another card. When the first card lands, the next one starts from its work.

Group the work by ticket

A ticket key links the card to Jira and groups related cards on the board. With a branch pattern, those cards land on the ticket's branch.

Ask an agent when a run fails

A failed merge or command offers Ask agent. The agent gets the error and output, then tries to fix the problem or explains what failed.

Comment on the code, get a card

Open any repo and branch in Files and comment on a line. Turn one comment into a card, or send all comments to the assistant to create one card for each.

Take a card over

Use Branch and check out to open the card's work in your own checkout. Finish it there, or send the changes back so the agent can continue.

Let review run in rounds

Review can send its comments straight to the agent. After the agent updates the card, the next review sees only the new changes. You choose how many times this can repeat.

Check in from your phone

Scan a QR code to chat with the project assistant and see the board on your phone. Approve a card or start the next one without going back to your desk.

REVIEW

Review the code, not a transcript.

Move price formatting to the server

kanzai/4c7a-price-format ← main

Task

Files

Terminal

backend 4 files

frontend 3 files

~/src/petshop-api

Changed All

format.ts2 ✎ src/pricing · +42 −6

money.ts1 ✎ src/pricing · +31 −4

invoice.ts1 ✓ src/http · +35 −12

pricing.test.ts test · +34 −16

One review across 2 repos. Comments carry the repo in the path.

backend/src/pricing/format.ts

Diff File

Edit Refresh

18 const currency = resolveCurrency(account);

19− return (amount / 100) + " " + currency;

19+ return formatMoney(amount, {

20+ currency,

21+ locale: account.locale,

22+ trailingZeros: true,

23+ });

Anchored context ✓ ✕

locale: account.locale,

EM You draft

Locale comes from the account here but from the browser in frontend/src/format/price.ts. Pick one and drop the other.

25}

3 comments ready sent as one message · task returns to Development

‹ 1 of 3 ›

Comment on the changes

Approve as-is

Submit Review

PROJECT ASSISTANT

Give Kanzai a ticket. Get back focused tasks.

The project assistant turns a ticket or a short request into focused cards based on your actual code. Ask why work has not landed and it checks the board for you. It can read your repos, but it only changes the board when you ask. You approve each action unless you switch on auto mode.

Project assistant Petshop · 3 repos read-only WAITING auto Claude Code opus ▾ Clear ⌘J

❯why is Cap concurrent sessions still in Approved?

● get_task 8f21

⎿ backend unmerged · base main · queue stopped 2h ago

The queue stopped at this card. backend/main has advanced by 4 commits since you signed off, so the branch no longer merges cleanly. Rebase it from the card, and the Approved queue resumes where it stopped.

❯add a Deploy to test button

● get_project Petshop

⎿ 3 repos · 2 actions · neither is a merge

⚠ Allow set_action? Kanzai · asked every time

Add Deploy to test, a merge onto test, on cards in Development, Review and Approved.

This adds the action to the project without running it. The button appears on those cards when the board refreshes.

Yes No, tell it what to do auto mode is off

❯ Ask about the board or add work… ⏎ send · ⎋ collapse

REMOTE

Keep the board in your pocket.

Press Remote in the assistant's dock and scan the QR code with your phone. Chat with the project assistant, and see the board as it changes. Open a card to read its task, its agent's transcript, and its diff, then start it, move it to Review, approve it, or run one of the project's actions. The link is end-to-end encrypted, so the relay in between only passes on messages it cannot read. Remote is in early access and still in development.

Project assistant Petshop · 3 repos read-only Remote Clear ⌘J

❯what is waiting for me?

● list_tasks Review

⎿ 1 task · 0 comments

One card is in Review: Move price formatting to the server. Its tests pass, and nobody has left a comment yet.

❯ Ask about the board or add work… ⏎ send · ⎋ collapse

9:41 5G

Petshop

Chat

Board

Development 1

Rotate auth tokens server-side

PET-198backend

WORKING 16m 21s

Move to Review

1h ago

Review 1

Move price formatting to the server

PET-211backendfrontend

+188−52no comments

Approve

8m ago

Approved 0

Done 3

Signup form validation

2d ago

ACTIONS

Run the usual jobs with one click.

Add buttons for the jobs you run all the time. Merge a branch, run a command in the card's worktree, or give an agent a one-off prompt. Choose which cards show each button, or put it at the top of the board for project-wide actions.

Petshop · Configuration

Repos

Actions

Columns

Assistant

Deploy to test merge → test Edit

Merges the card's branch into test without approving the card, changing its base branch, or moving it.

Where the button appears

Project Backlog Ready Development Review On test Approved Done

Column toggles follow the same order as the board, including your custom columns. The Project toggle adds a button to the board that runs independently of any card.

Dev server command npm run dev Edit

Runs in the card's worktree, in a window of its own, with a port no other card holds.

Review prompt Claude Code · read the diff and comment Edit

One headless turn in the worktree. It can leave review comments on the card beside yours and, when review rounds are on, send them to the agent.

On the board

New task ⌘N

Deploy to test

On a card

Retry failed webhooks

PET-214backendworker

Deploy to test Dev server Review

Dev server · :4173 Deploy to test

You · 20m ago

One action, both places. On a card, it deploys that card's branch; on the board, it deploys the branch configured for the project. The two runs are independent.

COLUMNS

Make the board match your workflow.

Add columns such as On test or In PR without losing the branch, worktrees, diff, or actions attached to a card. A column can also do something when work arrives. Drag a card to On test, for example, and start a deployment automatically.

Review can run a review prompt when a card arrives. It sends comments back to the agent, then returns the card for another review. This is off by default and stops after three rounds unless you change the limit.

Review 1

runs the Review prompt on arrival

Move price formatting to the server

backendfrontend

unread

+188−523 ✎

8m in column

On test 2

runs Deploy to test on arrival

Rotate auth tokens server-side

backendworker

Deploy to test

2h in column

Improve SEO

frontend

Deploy to test

35m in column

Approved 1

merges, then moves the card to In PR

Dunning retry window

backend

You · 6m ago

In PR 2

Signup form validation

frontend

Open PR

3d in column

Proration on plan change

backendfrontend

Open PR

5h in column

Done 31

Invoice PDF locale

backend

You · yesterday

Drop the legacy /v1 client

frontend

You · 2d ago

SKETCHES, FILES AND DOCS

Ask to see it. Kanzai puts it on screen.

The project assistant answers on screen. It can draw a diagram, open a file at the right lines, or write a document. You can also open each of these yourself, from the left edge of the app.

Draw it, then talk about it.

Ask it to sketch what happens when a user signs up. A diagram appears on the canvas. Comment on any box. The assistant replies there. It can also start a comment when it finds a problem.

Sketches +

Signup

Checkout flow

Webhook retries

Stored in this project

Comments +

On ✓ ✕

UserRepo.save

• Assistant

A second signup with the same email overwrites the first user.

You

That is a bug. Signup should refuse a taken email.

On ✓ ✕

Welcome email

EM You

Send this only after the email is verified.

Assistant

The welcome email is sent as soon as the user signs up. Send it after verification instead.

Stored separately from the sketch

Project assistant Petshop · 3 repos read-only

❯sketch what happens when a user signs up

● set_sketch signup

⎿ 5 boxes · 4 arrows · 3 regions

● show_sketch signup

● add_sketch_comment signup UserRepo.save

The route saves the user with UserRepo.save. The worker sends the welcome email. I left a note on UserRepo.save. It overwrites a user who signs up twice.

Open the code at the right lines.

Ask for the method where the user is saved. The file opens at that method, with the lines highlighted. You read the code, not a path to look up.

backend

frontend

worker

▸migrations

▸src

▸auth

▸billing

▸users

model.ts

repo.ts

routes.ts

server.ts

▸test

package.json

~/src/petshop-api · current main branch

src/users/repo.ts

34export class UserRepo {

35 constructor(private db: Db) {}

37 async byEmail(email: string) {

38 return this.db.one({ email });

39 }

41 // Insert, or update by email.

42 async save(user: User) {

43 const row = toRow(user);

44 const saved = await this.db

45 .upsert("users", row)

46 .onConflict("email")

47 .returning();

48 return fromRow(saved);

49 }

51 async remove(id: string) {

52 await this.db.delete({ id });

53 }

Project assistant Petshop · 3 repos read-only

❯show me the method where the user is saved

● Grep backend/src async save

⎿ 3 matches

● show_file backend/src/users/repo.ts 42–49

That is UserRepo.save. A second save with the same email updates the row.

Write the plan down together.

Ask it to write up the two sketch comments. It writes a document called Signup fixes. Add a note to any line. The assistant replies next to it. A card can point to the document. The agent working on that card reads it, so nobody copies the plan into the card.

Docs +

Signup fixes

Release checklist

Pricing notes

Stored as Markdown in this project

signup-fixes.md

Read Edit

Refresh

Signup fixes

From the two comments on the Signup sketch.

Refuse a taken email

UserRepo.save updates the row when the email exists. So a second signup overwrites the first user.

Check the email in POST /users before saving.
Answer 409 with "That email already has an account."
Keep save as it is for profile edits.

Welcome email after verification

The welcome email is sent as soon as the user signs up.

Send it once the user verifies their email.
At signup, send only the verification email.

Notes +

On line 10 ✓ ✕

Answer 409 with "That email already has an account."

EM You

Doesn't this tell anyone which emails have an account?

Assistant

It does. Show the same message for a new email and a taken one. If the email is taken, email the account owner.

Stored separately from the document

Project assistant Petshop · 3 repos read-only

❯write up both sketch comments as a doc

● get_sketch signup

⎿ 5 boxes · 2 comments

● set_document signup-fixes

● create_task ×2

⎿ Refuse a taken email at signup · Send the welcome email after verification

Wrote Signup fixes document and filed two cards. Each card points to the document, so its agent reads the plan there.

HOW IT WORKS

Add your local repos

Connect one or more checkouts. Kanzai finds the branches and gives every task an isolated place to work.

Turn work into cards

Write a card yourself, or give the project assistant a ticket and let it break the work into focused tasks.

Run, review, and merge

Start several cards in parallel. Finished work waits in Review and only merges after you approve it.

PRICE

FREE

$0 no key, no account

Use Kanzai on your own machine, for as long as you like, with a few limits:

Three agents working at once
Two actions per project
One custom column per project
One sketch and one document per project

Create as many projects, cards, and repositories as you need. The project assistant is unlimited too.

Download free

UNLIMITED

$19 per year

or $3 per month

Early access price, yours for as long as you stay subscribed.
Fourteen-day free trial.

Remove every free limit with one license:

Remote access from your phone
One key, three machines
Every update while you subscribe
Cancel any time

If you cancel, Kanzai simply returns to the free limits. Your boards, diffs, and worktrees stay right where they are.

Your first fourteen days lift the same limits. The first charge lands when they are up, so cancel before then and you pay nothing.

$19 per year $3 per month

Purchase and refund terms · Terms & EULA

Sold through Polar, the merchant of record. VAT and the invoice are handled at checkout.

Native app for macOS, Windows and Linux
Runs locally, with no account and your data in one file
Runs the real Claude Code, Codex, Grok Build, Antigravity and OpenCode CLIs
Use your Claude or ChatGPT plan, xAI login or Google sign-in; only OpenCode may need an API key
Works with any Git host

Ready to stop babysitting terminals?

Run Claude Code, Codex, Grok Build, Antigravity and OpenCode side by side from one local board. Drag cards to start agents, reviews, and deployments. Keep using the subscription you already pay for.

Download Kanzai free Free to use · No account · No API key · No telemetry

The button picks x86_64 for Windows and Linux. On arm64 hardware, take the arm64 build.

macOS Universal (Intel and Apple Silicon)
Windows x86_64 · arm64
Linux AppImage x86_64 · arm64
Linux deb x86_64 · arm64