#42bug
#42 waits for your acceptance: answer lead site-3f in its chat — “accepted” or “rework: …”
You accepted — waiting for the leadanalyst-7a · analyst2 min
☑ 0/3📎 2waits for you
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.
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”.
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.
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 reads as short lines: who did what, and when.
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.
harnsy MaxFor every project: what waits for you, what is with the lead, what is open and what is in the backlog.
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
▸Backlog2
▸New0
▸Taken0
▾In progress2
#43feature
#43 waits for your acceptance: answer lead site-3f in its chat — “accepted” or “rework: …”
You accepted — waiting for the leadsite-9a · developer1 h
waits for you
▸Blocked0
▾In review0
▸Dropped0
- analyst-7a · analystAcceptance criteria
- site-9a · developerImplementation
- qa-5e · testerTests and evidence
- You · waits for youOpen #42 to accept or return with a comment
Open the task to tell the lead what to fix.
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.
Your first AI team is one prompt away.
Installing takes one sentence to your agent. To open agents for you, harnsy needs tmux.
Install harnsy following https://harnsy.dev/llms.txt