/admin. You need at least one mapping for the orchestrator to do any work.
Mapping fields
Your Linear team identifier (e.g.
ENG). This is the short prefix shown in Linear issue identifiers. The orchestrator uses this key to match issues polled from Linear to the correct GitHub repo.GitHub organization name or username that owns the target repository (e.g.
my-org).Name of the target GitHub repository (e.g.
my-api). Combined with owner, this tells the orchestrator where to dispatch workflow runs.Name of the GitHub Actions workflow file to dispatch for implementation runs. Default:
claude-implement.yml. Change this only if you have renamed or customized the workflow file in the target repo.Branch that Claude creates pull requests against. Default:
main. Set this to master or your primary branch name if it differs.Maximum number of AI implementation runs that can be in progress simultaneously for this team. If the limit is reached, newly eligible issues are held until a slot opens. Default:
3.Where implementation runs execute. Default:
github-actions.github-actions— Claude runs inside a standard GitHub Actions job in the target repo. No additional infrastructure required.fly-machines— Claude runs inside a Fly Machine launched by the orchestrator. Requires the Fly sessions app to be configured.
How the Claude session behaves during a run. Default:
autonomous.autonomous— Claude works to completion without human interaction.interactive— Claude pauses and waits for feedback at decision points.hybrid— Claude proceeds autonomously but surfaces questions when it is uncertain.
Number of CPUs allocated to the Fly Machine for each run. Only applies when
executionMode is fly-machines. Default: 2.Memory allocated to the Fly Machine in megabytes. Only applies when
executionMode is fly-machines. Minimum: 256. Default: 4096.Whether to run a planning phase before implementation. When enabled, the orchestrator dispatches the planning workflow first, Claude posts structured analysis to Linear, and then implementation proceeds. Default:
true. See AI planning phase for details.Name of the GitHub Actions workflow file dispatched for the planning phase. Default:
claude-plan.yml. Only relevant when planningEnabled is true.When
true, the orchestrator automatically triggers implementation after the planning workflow completes without waiting for human review of the plan. When false, a team member must manually approve the plan before implementation starts. Default: true.A flat key-value object of additional environment variables to inject into the Fly Machine environment at dispatch time. Only applies when
executionMode is fly-machines. Example: {"DATABASE_URL": "postgres://..."}.The Claude provider used by the dispatched workflow. Default:
anthropic.anthropic— Uses the Anthropic API or Claude Code OAuth token, whichever is configured as an org secret in the target repo.bedrock— Uses AWS Bedrock via GitHub OIDC. RequiresawsRegionto also be set.
AWS region that hosts your Bedrock inference profile (e.g.
us-west-2). Required when provider is bedrock. Ignored for the anthropic provider.provider=bedrock is not supported when executionMode is fly-machines. Use executionMode=github-actions for Bedrock runs.