harnsy

See what your agents changed before you accept.

Agents work in their own git worktrees. Changes shows each one: its branch, task and agent, whether it’s in master, and the full diff.

Changes5against master

Files changed in more than one worktree: 1

api/orders.go

feat/checkout-api · #2 · shop-backend

feat/recalc-totals · #4 · shop-frontend

  • masterproject folderpushed

    ~/work/acme-shop

    ↑0 ↓0 ·committed 0 · uncommitted 0

  • feat/checkout-apinot pushed

    ~/work/acme-shop-wt/checkout-api

    ↑1 ↓0 ·committed 1 · uncommitted 1 ·Also changed in another worktree ·#2 Checkout API: validate the order and charge · in progress ·shop-backend running

  • feat/recalc-totalsnot pushed

    ~/work/acme-shop-wt/recalc-totals

    ↑2 ↓0 ·committed 2 · uncommitted 0 ·Also changed in another worktree ·#4 Recalculate totals on coupon change · in progress ·shop-frontend running

  • fix/cart-totalparkedpushed

    ~/work/acme-shop-wt/cart-total

    ↑1 ↓0 ·committed 2 · uncommitted 1 ·#3 Cart total shows 0 after removing the last-but-one item · blocked ·shop-frontend not running

  • fix/readme-typoitem closedin master

    ~/work/acme-shop-wt/readme-typo

    ↑0 ↓0 ·committed 0 · uncommitted 0 ·#6 README: how to run the shop · doneRemove

Every agent’s branch and state, and a warning when two touch one file. Sample data.

See

Every worktree, per project.

Changes sits next to Tasks. It lists every git worktree of the project with its branch, the task it belongs to and the agent working in it.

Where each branch stands.

In master, not pushed yet, or parked: each worktree says where its commits are, so you see what still has to land.

The full diff.

Open a branch to see the files it touches and the whole diff, full width. The task card opens right there, over the branch.

Before it bites

Two agents, one file.

When two live worktrees change the same file, Home warns you that they overlap, and the leads of both tasks are told.

As loud as you want.

Don’t need the warning or the leads’ messages? System › Notifications turns each of them off.

Tidy up

Remove what has landed.

Worktrees whose commits are all in the base branch can go, one by one or all at once, after you confirm.

Nothing in use disappears.

A worktree used in the last 12 hours stays (changes.recent_hours in config.yaml). A detached one, often a reviewer’s copy, goes only one by one, with a warning.

The agents write code faster than I can read it.

In harnsy you don't read every line: the task moves from role to role, and you accept the finished result.

In review you don't just click Accept or Return: write what to fix, and your comment lands in the lead's session right away. The lead sends the task back to whoever did it, with your words.

Howthe lead assigns it, each role hands it on with evidence, and the finished card turns amber. Changes shows every worktree’s diff when you want to look.

waits for you

Tasks
BoardArchiveDocumentsStatistics
waits for you 0blocked 0all
▸Backlog2
▸New0
▸Taken0
▾In progress2
#42bug
analyst-7a · analyst2 min
☑ 0/3
#43feature
site-9a · developer1 h
▸Blocked0
▾In review0
▸Dropped0

  1. analyst-7a · analystAcceptance criteria
  2. site-9a · developerImplementation
  3. qa-5e · testerTests and evidence
  4. You · waits for youOpen #42 to accept or return with a comment

Open the task to tell the lead what to fix.

Illustrative demo · #42: analyst → developer → tester → your acceptance.

feat/checkout-apinot pushed~/work/acme-shop-wt/checkout-api

#2 Checkout API: validate the order and charge · in progress · shop-backend running

In the branch’s commits 2

  • addedAapi/charge.go
  • modifiedMapi/orders.go

Uncommitted 1

  • modifiedMapi/charge.go

api/orders.goIn the branch’s commits

--- a/api/orders.go

+++ b/api/orders.go

@@ -12,7 +12,14 @@ func CreateOrder(w, r)

var req OrderRequest

if err := decode(r, &req); err != nil {

fail(w, 400, "bad order")

return

}

order := newOrder(req)

if err := req.Validate(); err != nil {

fail(w, 422, err.Error())

return

}

order := newOrder(req)

if err := charge(order); err != nil {

fail(w, 402, "payment declined")

return

}

save(order)

A branch in Changes: its files and its diff, read-only. Sample data.

Limits, honestly

  • Changes is for looking: agents edit and commit the code, the dashboard only shows it.
  • It reads the project’s git worktrees; work outside git doesn’t show here.

Your first team is one prompt away.

Installing takes one sentence to your agent. To run your agents, harnsy drives a terminal: tmux if it is installed, otherwise its own terminal host (on Windows, always its own).

Install harnsy following https://harnsy.dev/llms.txt
site-3flead · Claude Codeliveview only
❯ Plan #42 with the team.

Waiting for the breakdown from analyst-7a…

from analyst-7a through harnsy❯ #42 broken down: three acceptance criteria, including a retry after 24 h.

I’ll hand #42 to site-9a.

❯