Developers

Build locally. Run it for your company.

Use the CLI to create, develop, deploy, and manage apps. Connect the agent you already use through MCP to work with the same workspace permissions.

Start building Connect MCP

Readable commands. Structured results.

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

If you’re an agent, read atrax.run/agents.md

Share a private app with one person.

An owner or admin can invite a verified email to one app. The guest proves control of that exact email before opening it.

Review access
Check the app audience, existing guest access, and public-web state before sharing.
Invite the guest
Share the app with their email and select any actions they may use.
Send the stable URL
After accepting the invitation, the guest can open the same app URL. Revoke the grant when the review ends.

atrax share reviewer@example.com \
  --app <app-id> \
  --key invite-reviewer-v1 --json

Guest sharing does not add the recipient to the workspace or change access for current company members.

Private means private

Public web must be off for a private review. A guest grant covers only the selected app and actions.

Read the access rules →

Work from a new app to a connected workspace.

Build and deploy

Create an app, run it locally, then publish it to your workspace. Sign-in begins when you first deploy.

atrax new team-chat --template chat
cd team-chat
atrax dev
# Stop the local server when ready to deploy.
atrax deploy --json

Find and call app actions

Discover an app’s named actions and input schemas. Use actions.call under your current permissions.

atrax call actions.list \
  --input '{"appId":"<app-id>"}' --json

Contribute company knowledge

Upload a document, search Library, and retrieve items or files. Agents can also create and revise entries through the operation API.

atrax library upload ./brand.md \
  --workspace <workspace-id> --key brand-v1
atrax library search "brand" --workspace <workspace-id> --json

Connect through MCP

Connect the agent you already use through the MCP stdio server. Give each connection a name and revoke its session independently.

atrax login --agent "Operations agent"
atrax workspace use <workspace-id>
atrax mcp --workspace <workspace-id>

Use the same operations from the CLI and MCP.

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.

Give your agent the guide.

Open agents.md