Linear × Claude Managed Agents bridge

Webhook-driven routing translates Linear AgentSessionEvent into a Claude Managed Agents session using routing metadata to map the response back to the correct Linear issue. It operates statelessly by creating a CMA session with metadata linking it to the originating Linear issue.

You prevent duplicate webhook deliveries by deduplicating retries keyed by event.id. The bridge uses a retrieve-then-filter flow for workspace-scoped deliveries via sessions.retrieve to ensure idempotency while acknowledging within the required timeout.

Yes, this bridge applies to webhook-based automation where Linear and Claude use different credentials and payload formats. You must hold both sides' keys within the bridge service to translate the payloads correctly.

The best way to route Linear webhook events to CMA is by creating Managed Agents sessions with routing metadata. This metadata links the CMA session to the originating Linear issue so idle signals can route back as comments.

Yes, you need to register two webhook endpoints: one for Linear incoming events and one for CMA outgoing signals. The bridge translates between the two formats and uses session metadata to route responses.

Filter workspace-scoped webhook deliveries from CMA by using a retrieve-then-filter flow via sessions.retrieve. This ensures you only process relevant deliveries before deduplicating by event.id.