The environment agents run in

An app opened from the Finder does not inherit your terminal’s environment. It gets what macOS hands every app, which has none of your custom paths in it. That single fact explains most of the cases where something works in the terminal and not in Arbitr.

What to do if an agent can’t find a tool

The reliable fix is to stop relying on lookup. In Settings → Agents, select the agent and set Binary path to the absolute path of the executable, or press Browse…. Arbitr runs exactly that file afterwards.

Get the path from your terminal:

which claude
which codex
which cursor-agent

If which prints nothing, the agent is not installed for that shell, and no setting in Arbitr will find it.

Working directory

Every agent starts in its project’s folder. Relative paths in a prompt are relative to that folder — not to your home directory, and not to whatever you last used in the terminal.

Still having trouble?

1. Run the command in Terminal. If it fails there, fix that first.
2. Put the path from which <command> into the agent’s Binary path field.
3. Restart Arbitr.