harnsy

Hear about what needs you, and nothing else.

Home and the tray show what waits for you. The lead agent hears about the rest first. System › Notifications decides what goes out, and when.

Notifications to leads

harnsy tells a team’s lead when something needs its move. Switch off what you do not need and set the times. Your bell does not change. Applies to every project on this node.

Send notifications to leads

Off: leads hear nothing below, except the high-context warning.

on

What leads are told

An agent stopped and waits for you

The agent ended its turn on a question to you in chat. The lead may answer it itself.

on

Told at once.

Two branches change the same file

A file is changed in two or more live worktrees. Settled early, it is a small merge. Switched off, these rows also leave Home.

on

Told at once.

An agent is idle with open work

The agent does nothing while it holds a taken or started item.

on

Idle for20mindefault: 20 min

An agent is busy without a report

The agent works long and writes nothing on its items.

off

Busy without a report for60mindefault: 60 min

An agent’s context is running out

Always on

Context full at40%

System › Notifications: what leads are told and when. Sample data.

What reaches you

Home counts what needs you.

The number next to Home counts every agent waiting for an answer or a permission and every task in review or blocked on you, across all projects. News folds into “For information” and isn’t counted.

A badge in the header.

On every page a badge counts the agents that wait for your answer or your permission, with the longest wait. It is hidden when nobody waits, amber while someone does, and turns solid after 10 minutes. A click opens the list, oldest first, and you can answer a question or a permission request right there.

Allow what was denied, in place.

On the red “denied” card of a Claude Code agent, “Allow…” writes a rule to permissions.allow after showing you the exact change, with a backup; on a permission prompt, “Allow always” sits next to “Allow once”. Only you can press it, not an agent. An agent that stopped after a refusal shows the red row until it gets a new prompt, and its lead is told at once.

The tray, next to the clock.

An amber icon means an agent waits for you, and its menu names who and for what. Green means agents are working; grey with a slash means harnsy isn’t answering.

Desktop notifications.

The tray tells you when an agent waits for permission or an answer, asks in text, fails, disappears mid-task, or ends a turn longer than a minute. Quiet mode keeps the icon and drops the popups.

What reaches the lead

The lead hears first.

harnsy messages a team’s lead agent when an agent waits for you, idles with open work, goes silent, leaves, or when a task stalls or has no executor. The lead may sort it out before you look.

One message, each thing once.

At most one message per lead every 5 minutes, with everything that came up meanwhile; a thing still standing after 4 hours is said once more. Questions to you and two branches changing one file are told at once.

Task updates arrive together.

An idle agent gets its task updates as one message, harnsy: N updates for you, about a minute after the last and at most three minutes after the first. A busy agent gets them when it next looks. Your decisions on a card still go at once.

Context running out.

At 40% of an agent’s context, or at the handover size you set, its nearest live lead is told, always. If no lead is online, the warning shows up for you on Home.

Your settings

Each kind on or off.

System › Notifications lists every kind with its time: idle 20 min, busy without a report 60 min, gone 2 min, stale 24 hours. Change any of them, or reset it to the default.

The waits are yours.

The batching waits are set in config.yaml: notices.batch_quiet and notices.batch_max. 0 sends at once.

One switch for all.

“Send notifications to leads” turns them all off at once, except the context warning. Task moves and your decisions always reach the lead.

The dashboard in your language.

System › Settings › Interface language: English, Russian or Spanish, applied at once and kept in this browser. The tray speaks English and Russian.

A browser notification when you are elsewhere.

If you turn it on in that browser, a notification appears when an agent asks a question, asks for a permission or waits for you while the harnsy tab is in the background. It names the project and the team and never shows the question. Press it and it opens that agent’s terminal, or the list of who waits if the agent has none.

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

harnsy shows you where you're waited for, and you answer right there.

Howthe tray turns amber, Home shows what the agent asks, a question or a command to allow, and one click answers it in the agent's session.

Needs you2Oldest first
4 min

qa-5e · tester

waiting for permission

Answer here or in the agent’s terminal.

Asks permission to use Bash

Run the payment retry tests

Command
npm test -- checkout/retry.spec.ts

“Always allow” is only in the terminal.

Home in the dashboard: what waits for you, and the answer right there.

Limits, honestly

  • Notices go to lead agents and to your desktop. With harnsy Max they also reach your phone as a push, and a Telegram or Discord bot can bring them to a chat; there is no email. Remote Control on your phone is Claude Code’s own feature.
  • The tray shows “waiting” for Claude Code agents; Codex doesn’t report that it waits.
  • The dashboard has no password: it listens only on this machine (127.0.0.1). From another machine, use an SSH tunnel, or with harnsy Max, access from outside behind a passkey.

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

Questions

Which languages does the dashboard speak?

English, Russian and Spanish.

All questions →
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.

❯