Integrations directory
Roles come first — planner, implementer, reviewer, oversight. Providers sit behind them. The initial self-hosted release targets Codex and Claude; live acceptance and publication are pending. Other coding agents are outside this offering. Cloud and Enterprise are future offerings.
Repository access, branch and pull-request delivery, issue import.
Repository access and merge-request delivery. Issue import in progress.
Import work items as tasks and keep Linear authoritative for status.
Import work items and post run outcomes back to the issue.
Repository access and pull-request delivery.
Planner, implementer or reviewer sessions under your own credentials.
Planner, implementer or reviewer sessions under your own credentials.
Planner, implementer or reviewer sessions under your own credentials.
Planner, implementer or reviewer sessions under your own credentials.
OpenAI-compatible endpoints for local or private model serving.
Workspace containers and preview services on ordinary Docker hosts.
Per-repository environment definitions, including preview URLs.
Additional labelled workers with their own concurrency limits.
Scheduling workspaces onto an existing cluster.
Attach MCP tools per workflow, with per-role permission scoping.
Read-only queries by default; write access requires approval.
Drive a preview environment for smoke tests and screenshots.
Store references, inject values at run time, log every reveal.
Resolve references from your existing vault at run time.
Sign in through the identity provider configured for the deployment.
Directory-driven provisioning and deprovisioning.
Run lifecycle, attention requests and completion events.
Attention requests and approvals routed to a channel.
Run duration, cost and outcome series for your own dashboards.
What each integration page documents
Versioned integration guides must document the accepted configuration before operators enable it. Directory entries and saved credentials alone do not prove execution readiness.
Exactly which actions the integration can perform.
The auth method and the minimum scopes required.
In order, with the values you will need to hand.
What it does not do yet, stated plainly.
What data crosses the boundary, and what is logged.
The failures teams actually hit, and the fix.
Provider names are used descriptively. Logos appear only where trademark use is permitted.
Missing the provider you use?
Adapters are plugins. Integration requests can be submitted through the contact route. External code contributions require the finalized contribution terms and published repository.