Agent

Agent configuration for Crow CI workers.

Minimum Configuration

CROW_SERVER=crow-server:9000
CROW_AGENT_SECRET=<token>

Variable	Description
`CROW_SERVER`	Server gRPC address (no protocol prefix)
`CROW_AGENT_SECRET`	Authentication token from server

Parallel Workflows

CROW_MAX_WORKFLOWS=4

By default, agents execute one workflow at a time. Increase based on available resources.

Workflow Filtering

Crow routes workflows to agents using two mechanisms:

Method	Description
Labels	Filter by matching key-value pairs
Priority	Prefer agents with higher priority when multiple match

Labels

Agents have built-in labels:

Label	Description
`backend`	Execution backend (docker, kubernetes, local, podman)
`type`	Agent type
`platform`	OS/architecture
`agent`	Agent identifier

Add custom labels to route specific workflows:

# Agent configuration
CROW_AGENT_LABELS='gpu=true,memory=high'

# Workflow configuration (.crow.yaml)
labels:
  gpu: true
  memory: high

Only agents with matching labels will process workflows with those labels.

Priority

When multiple agents match, higher priority agents are preferred. Priority is managed server-side per agent in the web UI (agent settings) or via the API, and persists across agent and server restarts.

Agent Types

Global Agents

Admin-managed agents that process all workflows. Configure via environment variables on the agent.

Organization/User Agents

Non-admin users can register agents scoped to their org or user account.

Remote agent configuration:

CROW_SERVER=grpc.crow.example.com:443
CROW_GRPC_SECURE=true
CROW_AGENT_SECRET=<token>
CROW_BACKEND=docker

Multi-Org Agents

Process workflows from multiple specified organizations or repositories.

# Multiple orgs (pipe-separated)
CROW_CUSTOM_LABELS='org=1|2|3'

# Alternative syntax (comma-separated, merged internally)
CROW_CUSTOM_LABELS='org=1,org=2,org=3'

# Limit to specific repos
CROW_CUSTOM_LABELS='org=myorg,repo=myorg/specific-repo'

Multi-org labels appear highlighted in the agent list:

Agent Scope

Admins choose an agent’s scope in the Add agent dialog. Global (the default) lets the agent run pipelines for any organization. Specific organizations scopes the agent to one or more selected orgs.

Org admins can manage agents scoped to their organization from the org’s agent settings page. Deleting a multi-org agent there removes it from that organization only; it is fully deleted when that was its last remaining organization.

Backend Options

Configure backend-specific settings at the agent level. See environment variables for all CROW_BACKEND_* options.

Local Backend Sandboxing

Enable process isolation using macOS sandbox-exec:

CROW_BACKEND_LOCAL_SANDBOX_LEVEL=standard

Level	Network	System Access	Use Case
`none`	✅ Full	✅ Full	Trusted code only
`standard`	✅ Full	⚠️ Limited	Most CI/CD workloads
`strict`	❌ Blocked	❌ Minimal	Offline builds, maximum isolation

Standard level details:

Allows	Denies
Network access (npm, go get, pip)	Writing outside workflow dirs
System libraries and frameworks	Sensitive user dirs (Documents, Desktop)
Shell configs (.bashrc, .zshrc)	SSH private keys
Workflow temp directories

none runs processes without isolation. Only use with fully trusted code.