Nothing waits for you in silence

Highlights

• A “Waiting for you” badge in the header.

  On every page a badge counts the agents that wait for your answer or your permission, with the longest wait. A click opens the list, oldest first: the agent, its team and role, what it waits for and for how long. Answer a question or a permission request right there; a refusal opens the agent’s tab. Only real waits are counted, not tasks or notices.

• Allow a refused action from the dashboard.

  On the red “denied” card of a Claude Code agent press “Allow…”: choose how far the rule reaches (this command, the same prefix, the whole tool) and where it is kept (this project’s .claude/settings.local.json or all projects’ ~/.claude/settings.json). You see the exact rules and the file change before anything is written; harnsy touches nothing else, keeps a backup and tells the agent “allowed, retry”. On a permission prompt, “Allow always” sits next to “Allow once”. Only you can press it, not an agent.

• Every open 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 now says whether it waits for you or for something external.

• Defer a task and get it back.

  “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 Tasks board has its own “Deferred” column, folded by default, soonest first.

• Sleep and Turn off.

  Two separate actions for an agent and for a whole team. “Sleep” closes the tab and keeps the seat, the session and the memory; wake brings it back. “Turn off” closes it and frees the seat for good.

• Organizations.

  A new section: organizations and their projects on the left, the content on the right. Rename an organization or a project in place. An organization with no projects can be deleted, with a confirmation that shows what goes with it. “Roles” moved here from “System”.

• Terminals on Windows.

  harnsy has its own terminal for Windows 10 1809 and later: agents open in tabs of their own, you read their screen and watch them live in the dashboard, and they keep running when harnsy restarts. No splits or windows.

• An installer that does not ask.

  harnsy install --accept=service,hooks,statusline,tray (or --yes) answers yes up front, also without a terminal, and your answers are kept so an upgrade does not ask again. If you already have a status line, harnsy can wrap it instead of replacing it; uninstall puts yours back.

• Markdown on the task card.

  Criteria, results and the history render tables, lists and links.

• Each project keeps its own board view, and Tasks › All projects is a summary.

  Columns, filters and sub-items are remembered per project. The summary counts, per 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, in 7 and in 30 days.

• A scrollable view-only terminal.

  A locked terminal in the dashboard scrolls its history with the wheel, touchpad, a finger or PageUp/PageDown; “Back to live” or End returns. Nothing is typed into the agent.

• Decisions and refusals do not get lost.

  If you accepted or asked for rework on a card and the lead has not recorded it, the lead is reminded, and a comment of yours that the lead has not answered is raised the same way. An agent that stopped after Claude Code refused a tool shows the red “waits for you” row until it gets a new prompt, and its lead is told at once.

• The right context window for Sonnet 5.5.

  harnsy took sessions started with --model claude-sonnet-5-5 for a 200k window, so 180k looked like 90% and raised false “hand over” notices. Sonnet 5 and Opus 5 are now 1M.

• Windows: Microsoft Defender no longer blocks harnsy.exe.

  Earlier packs were flagged as Trojan:Win32/Gracing.I, a false positive caused by how the binary was built. This release is built as a plain Go program, which Defender lets through.

• Windows upgrades stop the running harnsy.

  The installer now replaces a running harnsy.exe: it sets the running file aside, puts the new one in place, and only then stops the node; if that fails, nothing is stopped. Without a terminal it prints the exact command. Agents keep running when the terminal host runs outside harnsy’s task.

• Text is no longer lost on Windows.

  When an agent put JSON in a curl argument, Git Bash’s curl re-encoded it and Cyrillic in task notes became “?”. The node now refuses a body that is not UTF-8 with 400 bad_utf8 instead of saving damaged text.

Upgrading. Run the install command again. The database updates itself on first start. The installer restarts the running node on the new build; at a terminal it asks first.

How to update →