Integrations · Coming soon
Linear
Planned, not built. Here is the shape it will take when it ships, and what already covers the same ground today.
Triaged issues, mirrored into your tracker
The intended integration is narrow on purpose: when the agent qualifies a GitHub issue, create or update the matching Linear issue, and keep the two statuses in step as the work moves. We have not built it, so nothing on this page describes behaviour you can turn on today. What exists now is the REST API and the outbound webhooks, enough to write the same sync yourself in an afternoon if you need it before we ship it.
One issue, two systems
A qualified GitHub issue would create its Linear counterpart, carrying the labels the agent applied and a link back to the thread.
Status stays in step
Handoff, escalation and close would move the Linear issue too, so the tracker stops disagreeing with the repository.
Available today instead
Subscribe to the outbound webhook events and call Linear's API yourself: the same events the built-in sync would use.
Next step
Bound what the agent may do first
Whatever the tracker, the decisions it mirrors come from your policy file: what qualifies, what escalates, what merges.
Read the maintainer.yml reference
Ship more. Maintain less.
We expect software to be written faster than any team can review it. Bring your repos, your boxes and your keys. We bring the org that keeps up.
developerz-bot I've mapped this to session.ts and two integration tests.