Key in, team picked, spec out.
Personal API key — no OAuth. Fernet-encrypted at rest.
Circuit verifies the key by reading your teams and organisation, then stores team_id, team_name and org_url_key.
AU18 sets up a disabled “Linear: Create issue on brief” hook for you to switch on when ready.
Push the spec and Circuit creates the Linear issue. Status comes back via SWR polling (every 30s while you’re on the spec, 120s in the background).
The why travels with the ticket.
The exact quotes that drove the spec land in the Linear issue, so engineers see the why.
Push spec → Linear issue, with status polled back via SWR. Inbound webhooks for real-time Linear status changes are planned.
One click, one issue, no manual transcription.
GraphQL verification reads viewer { organization { id name urlKey } teams { nodes { id name } } } — Circuit knows your team layout. Keys encrypted with Fernet.
Asked and answered.
Linear’s recommended path for app-style integrations. The key is encrypted at rest and validates against your organisation on every call.
Yes. A spec can spawn multiple issues — Circuit keeps the rollup view so you can see ship state across all of them.
Yes. The citations and customer quotes are included in the issue body, so engineers see who asked and what they said.
Polled via SWR — 30 seconds while you’re looking at the spec, 120 seconds in the background. Real-time inbound webhooks are on the roadmap.
GitHub · PagerDuty · Cursor · All integrations
Part of Circuit’s autonomous product intelligence stack — see the full picture.