Big Arrow vs Orkes Conductor Human tasks

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.

Orkes Conductor Human tasks

Escalation chains with a time limit per assignee and a choice of leaving the task open or failing the workflow. No built-in Slack or email prompt, so alerts need a trigger policy and a second workflow.

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

Orkes Conductor Human tasks

1. Give every assignment you want to escalate from a non-zero slaMinutes, since 0 never expires and nothing can follow it
2. Pick TERMINATE for risky actions so an unanswered approval fails the workflow instead of staying open to anyone
3. Start approval workflows with an idempotencyKey and RETURN_EXISTING, so a retried start doesn't ask twice
4. Refresh the JWT from /api/token with a set expiry instead of requesting one that never expires
5. Fetch single doc pages, not llms.txt, which is the whole documentation in 2.57 MB