harnsyRU
All features

A control panel for the boss, not a surveillance screen.

harnsy calls you when a decision is needed. The rest of the time, you work.

A signal instead of watching.

An agent waits for permission or an answer, a task is ready for review, a role has no holder, a session died: the tray icon turns amber and the bell lights up in the dashboard.

Task board.

What’s in progress, what’s blocked, what’s waiting for review. Inside each task: history, reports and screenshots. Accept or return in one click.

Links graph.

The lead in the centre, teams around it, lines for who talks to whom. See how the work really flows and where agents chat more than they should.

Every agent on one screen.

Claude Code, Codex, OpenCode: who’s working, who’s waiting, in which role, how much context is left. Where a context size is estimated rather than known, it says so.

Live terminal.

Any agent’s terminal opens on top of the page: see what it’s doing and step in if needed.

One-click launch.

Ready profiles: which harness, which model and flags. Profiles that turn off permission prompts can be started only by a person.

Amber is waiting for you. Green is working. Red is a failure or a role with no holder. Blue is an action. A colour means the same everywhere and always comes with text.

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.

How: the lead assigns it, each role hands it on with evidence, and the finished card turns amber.

waits for you

Tasks
BoardArchiveDocuments
waits for you 0blocked 0all
▸New0
▸Taken0
▾In progress2
#42
analyst-7a · analyst2 min
#43
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.

#42

Checkout: no double charge on retry

goes to the lead; the lead moves the card

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

Came back an hour later. The agent had been waiting for my "yes" the whole time.

harnsy shows you where you're waited for.

How: the tray turns amber, the bell says who waits for what and opens that terminal.

The bell: what waits for you right now.

Five agents on a phone: five chats, and someone in each is waiting for an answer.

In harnsy you have one way in: the lead. Even from your phone.

How: the lead hands out tasks and brings you only questions and finished work. From your phone, through your Claude Code's Remote Control.

You lead

1 · Set the task

#42 · Checkout: no double charge on retry

2 · The lead asks

site-3f → you

Allow payment retries for 24 hours or 7 days?

3 · #42

waits for you

Your word goes to the lead.

You talk to one agent: site-3f.
Pavel speaks into his phone; the voice message goes to five lead agents, each reporting back.

I went from managing people and development teams to managing agents. Today I run digital departments from my phone: I talk to each department's lead, and the lead hands out tasks to agents and brings me questions and finished work. Agents still can't solve a whole task and make the right call on their own, so we need to stay in touch with them all the time. harnsy helps you build that process: you talk to your leads, not to the whole team.

Limits, honestly

  • The live terminal in the dashboard needs tmux.
  • No tray on Windows yet.
  • Answering a permission prompt from the dashboard isn’t possible yet; it’s planned.

Your first AI team is one prompt away.

Installing takes one sentence to your agent.

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.

❯