Use --json for machine-readable command results. Named operations take schema-checked input. Writes use a stable request key so an agent can identify the same intent across retries.
Install the released CLI below, or give your agent the agent guide.
$
curl -fsSL https://atrax.run/agents.sh | sh -s -- --client codex
Both interfaces use the platform operation registry and check the current person’s permissions. MCP exposes authenticated workspace operations; browser and device sign-in handshakes stay in the login flow.
More operations
atrax call <operation> covers team invitations, app and action audiences, guest access, sessions, backups, and recovery. Use the operation schemas for exact input and output shapes.
Current limits
For automated writes, choose a stable --key and reuse it with identical input when retrying. Inspect contracts with atrax operations inspect and workflows with atrax recipes list. Hosted agents and scheduled automation are planned for later.