Big Arrow vs Hatchet

Big Arrow

An agent can show a person which control to click, with a labelled arrow that needs no permission to draw, never takes focus and always removes itself. The tool is a week old at version 0.4.6, runs only on macOS, reports no answer beyond how an arrow ended, and has no security policy.

Hatchet

A durable task waits for a keyed event without holding a worker slot, and resumes from its event log after a restart, in Python, TypeScript, Go or Ruby. Hatchet supplies only the pause and resume. It has no approver inbox, notification channel or record of who answered, and its MCP server cannot push the event.

Big Arrow

1. Open the exact System Settings pane or URL first, then point at the one control left for the person
2. Write the sign as a full sentence that names the action and, for approvals or payments, what the click does
3. Pass --app or --window for any target inside an app, so it is raised and the arrow hides while covered
4. On exit 4, run bigarrow doctor and ask the person to grant Accessibility to the app running your shell, not to bigarrow
5. Call bigarrow stop once the step is done, and add bigarrow stop --hook as a Claude Code UserPromptSubmit hook

Hatchet

1. Put the approval wait in a durable task, and keep API calls, database reads and random values in child tasks, because the code between checkpoints is replayed
2. Add a sleep condition in the same or group as the event condition to set a deadline, and treat the sleep firing first as a timeout
3. Give the event a scope and the wait a lookback window when the answer can arrive before the wait starts. Both must be set together
4. Filter with a CEL expression such as input.user_id == '1234' so one approval key cannot resume another request's task
5. Push the answer with the SDK's event push or POST /api/v1/tenants/{tenant}/events. The MCP server has no tool for it
6. Grant the MCP server one profile with hatchet mcp auth --grant <profile>. It refuses profiles that were not granted