harnsy

From your request to your “Accept”.

The lead turns what you ask into tasks on the board, splits them by role and brings back the result with proof. You decide on the task card.

waits for you 1blocked 1all

New 0Taken 0Blocked 1Done 0Dropped 0

Backlog1
#8feature

Export orders as CSV

Send to work
nobody9 min
New0
Taken0
In progress2
#6task

Move the shop to the new payment provider sandbox

shop-lead · lead12 min
☑ 2/3
#1feature

One-page checkout

shop-lead · lead12 min
⤷ 1/3sub-task in review
  • ▾ 3 sub-tasks
  • in review #2

    Checkout API: validate the order and charge

    backend · shop-backend
  • in progress #4

    Recalculate totals on coupon change

    frontend · shop-frontend
  • done #5

    Order summary copy

    docs · docs-lead
Blocked1
In review1
#2feature

Checkout API: validate the order and charge

shop-lead · lead3 min
waits for you
AcceptReturn…
Done0
Dropped0
The task board: one card waits for your acceptance; a backlog card moves only when you send it to work. Sample data.

Plan

A request becomes a task.

Say what you need; the lead records it as a task with acceptance criteria and a type: bug, feature, research or task. The board filters by type.

Split by role.

The lead splits a task into sub-tasks for the roles below it. The parent waits until every sub-task is settled; a sub-task in review shows on the board as “part of #N”.

Priority.

Mark a task high, medium or low. The backlog sorts by priority or by date, so the work that matters most is on top.

Tasks that wait for each other.

Say which task blocks which, also across projects. A card names its blockers, and says “Ready to start” when nothing holds it. A dependency is the order of work: it shows, it does not forbid. When a blocker is done or dropped, the blocked task’s agent and lead are told.

Chains.

Tasks › Chains draws linked tasks as chains, step by step from left to right (from top to bottom on a phone). In a task, Dependencies shows its whole chain: what comes before it and what waits for it.

Chains

Five tasks in two projects: Cart API is done and holds up Checkout form and Empty-cart screen; Checkout form blocks Payment step, which blocks Release 1.4. Empty-cart screen is ready to start.

  • #31acme-apiCart APIDone→ blocks 2
  • #34acme-shopCheckout formIn progress→ blocks 1
  • #35acme-shopEmpty-cart screenReady to start
  • #36acme-shopPayment stepBlockedafter 1 open item→ blocks 1
  • #39acme-shopRelease 1.4Blockedafter 1 open item
The Chains view: linked tasks drawn as chains, one step after another. Sample data.

Work

Every task says what it waits for.

Cards on the board, the task dialog and sub-items show “waits for … · who · how long”: an agent, the lead, you, a review or something outside. A task you block says whether it waits for you or for something external.

Plan

Defer a task until a date.

“Defer until…” puts a task away until a date; on that day it returns by itself and its lead is told. A task in review can be snoozed the same way: it stays in review but does not wait for you until then. The “Deferred” column is folded by default, soonest first.

A backlog for later.

Park what can wait: nobody takes it, and it doesn’t count as open work. Send it to work when its time comes, or reject it with a reason.

Group tasks into releases.

Assign tasks to a milestone, a release of your project with a due date and a theme, filter the board by it and watch the progress strip and the burn chart. Everyone sees milestones; a harnsy Max key creates them.

Work

Progress you can see.

Agents split a task into checks and close them as they go; the card shows a progress bar. The history is folded by default and reads as short lines: who did what, and when. Criteria, results and the history render Markdown: tables, lists and links.

Branch and folder on the card.

A card shows the git branch and worktree its agent works in, with “copy path”. When the task closes, the agent is reminded to remove the worktree.

Accept

Work comes with proof.

Agents hand in work with Markdown reports, screenshots and HTML pages, such as a chart or a table, shown in a sandboxed frame.

You accept or return.

A finished task waits for you in review. Accept it, or return it with a comment that goes straight to the lead’s session.

Statistics.

Done, dropped and returned tasks by day, for today, 7 and 30 days, who closed them, and GitHub issues filed from cards.

All projects.

A summary for every project and in total: what is open, in work, waiting for you, stale and in the backlog, and what was created, done and dropped today, over 7 and over 30 days. Each project keeps its own board view: columns, filters and sub-items. Free harnsy runs one organization with 2 projects; a harnsy Max key adds more.

Pick one of several options.

An agent can submit 2 to 5 options with pictures. You press “Pick Vn”, and you have 10 seconds to undo. A “choose” request shows its options as buttons, too.

v2.3due Oct 16reports and exports
4 of 10 donerelease #425 · checks 3/7

Queued3

#415Partner webhook signature

Backend developerBlocked

#421Release notes for v2.3

Lead

#423Load test of the export

QA engineer

In progress2

#412Retry failed webhooks

Backend developer

#418Empty states on Reports

Frontend developer

Waits for you1

#409Is CSV export free or paid?

Reviewer

Done4

#401Export reports as CSV

Backend developer

#403Reports page: export button

Frontend developer

#405Rate limits on the public API

Backend developer

#407Checks for CSV export

QA engineer

The task board filtered by one milestone. Sample data.

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.
Variants to pick from3

Pick one: the item closes, and the lead starts building your pick as a new item.

  • Large headline

    The price right under it.

    To build: 2 h

    Pick V1
  • Two columnsexecutor recommends

    The comparison side by side.

    To build: 1 d

    Pick V2
  • Cards only

    No long text.

    To build: 3 h

    Pick V3

None — return with a comment

A task with three options: pick one, or return it with a comment.

Limits, honestly

  • Attachments: Markdown and HTML up to 512 KB, images up to 5 MB, up to 50 per task.
  • Checklists are read-only in the dashboard: agents close the checks.
  • Tasks move through the team under the lead’s direction, not by a fixed process engine.

How to set it up →

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.

❯