Source: https://harnsy.dev/features/checkpoints > harnsy calls you when a decision is needed, and you give it right there. The rest of the time, you work. # Answer your agents without opening their terminals. harnsy calls you when a decision is needed, and you give it right there. The rest of the time, you work. Home in the dashboard: an agent asks a question, and you answer right there. Sample data. ### Answer a question in one click. An agent stops on a question: Home shows it with its options, and one click answers it in the agent’s own session. Several steps open as tabs, several answers can be ticked, and “Other” takes your own words. Questions come from Claude Code, Codex and OpenCode. ### Allow a command, or refuse it. An agent asks permission to run a command: you see the tool and the exact command, and allow it once or refuse, with a reason if you like. Requests come from Claude Code and OpenCode. The terminal keeps working alongside; the first answer wins. Keys 1–9 and Enter work too. ### Home: what needs you. The dashboard opens on an inbox of what waits for you, in three columns: tasks for your review or blocked, agents’ questions and permission requests, and “For information”. Move through it with the arrow keys; the project you picked stays with you from section to section. ### Plain-text questions too. An agent that ends its turn asking you in chat (“say ‘yes’ and I’ll go on”) is marked “waits for you” at once, with a field for your answer, and its lead hears about it right away. ### A refusal shows in red. An agent whose permission request was refused is marked red, apart from the agents still waiting for your decision, so a stuck agent doesn’t pass for a waiting one. ### A signal instead of watching. When something waits for you, the tray icon turns amber: an agent’s question or permission request, a task ready for review, a role with no holder, a session that died. Each row says whether you have to act and why; what is only news stays folded. ### You choose the notices. Turn each kind of notice the lead gets on or off and change its times, with a reset to the defaults (System › Notifications). → ### Task board. Tasks move from role to role on the board, with checklists, reports and history; you accept or return the result in one click. → ### See what the agents changed. Changes shows every worktree’s branch, state and full diff, and warns when two of them change one file. → ### Terminals and agents. Open any agent’s terminal over the page and step in; every agent is listed with its role and status, and context left for Claude Code and Codex. → ### 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. ### Pause a whole team. “Pause” on Teams holds every message and notice to the team’s agents; nothing is closed. “Resume” delivers them in order and the team works again. Your own messages from the dashboard still go through. ### After the current step, or now. Choose “After the current step”: running turns finish and nobody is woken for new work. Or “Now”: it presses Esc in every busy agent, and on resume they are told to continue. An agent that harnsy did not open in a pane is not interrupted, and you are told which. ### A paused team is marked. Teams and Home mark it “paused” and show how many messages are held. ### See what your agents were refused. The Permissions page sums up the actions agents were refused, grouped so one fix covers many, each with a button that makes the fix. An agent stopped by a missing permission shows red, with what was refused. ### Turn a refusal into a rule, with a backup. “Allow” turns a refused action into a permission rule. You choose its scope and the file it goes in, harnsy shows you the exact change first, and it keeps a backup of the file before it writes. ### One shield for permission checks. A shield in the top bar says how harnsy starts your agents: amber means you have not chosen, green means with permission checks, red means without. A new install starts with checks until you answer “Start agents without permission checks?”; an existing install keeps working as before. Only you can change it, and the Assistant runs with its program’s permission checks. Amber is waiting for you. Green is working. Red is a failure, a refusal or a role with no holder. Blue is an action. A colour means the same everywhere and always comes with text. 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. 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 Illustrative demo · #42: analyst → developer → tester → your acceptance. 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. The lead doesn't check on the team by the clock either: harnsy tells it when an agent sits idle or silent with work in hand, leaves with open tasks, or a task stalls. One message, each thing once. Howthe lead hands out tasks and brings you only questions and finished work. Away from your desk, if the lead runs in Claude Code, you can write to it from your phone with Claude Code's own Remote Control. You lead The permission-checks shield: not chosen yet, on, off. ## Limits, honestly - Claude Code needs harnsy’s hook: run `harnsy install` again and say yes to the change it shows. It works in sessions started after that, and a request reaches the dashboard only if the dashboard is open when it comes. - Codex: questions only, and it reads your answer at the end of its current turn. Its permission requests are answered in its terminal. - “Always allow” is given only in the agent’s terminal. - The live terminal in the dashboard needs a terminal harnsy can drive: tmux if it is installed, otherwise harnsy’s own terminal host (always its own on Windows). - Checklists are read-only in the dashboard: agents close the checks. - Changes is for looking: agents edit the code, the dashboard only shows it. [Read the docs →](https://harnsy.dev/docs/answers-and-approvals) ## 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`