Big Arrow vs Trigger.dev

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.

Trigger.dev

Tokens complete from a backend, a pre-signed callback URL or the browser with a token scoped to one waitpoint. 10-minute default timeout on tokens.

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

Trigger.dev

1. Pass an explicit timeout to wait.createToken() and handle ok: false as a timeout
2. Use an idempotency key when creating the token so a retried step doesn't send the reviewer a second request
3. Give the browser the publicAccessToken, never the secret key, and don't call token.url from client code
4. Tag tokens with the user or task ID so pending approvals can be listed per reviewer
5. Start the MCP server with --readonly when the agent only needs to inspect runs