Integration

Tickets capture the 'what'. Cognia connects them to the 'why'.

Linear holds the work. Slack holds the argument. GitHub holds the change. Cognia links them in a graph and answers questions across all three.

What gets captured

●Issues (title, description, comments, status changes)

●Projects and milestones

●Cycle / sprint metadata

●Triage queue and labels

1
Open Admin → Integrations
Find Linear.
2
OAuth
Standard Linear OAuth with the 'read' scope. We don't write to Linear from this connector.
3
Pick teams
By default, we index every team you have access to. You can restrict to specific Linear teams if you want to keep some out (e.g. HR, finance).
4
Ask issue-shaped questions
'What was the last P0 we shipped a fix for?' or 'Which tickets are blocked on customer feedback?'

cogniahq.tech /agent · Linear

ask Cognia:What's blocking Polaris GA?

Returns the open tickets in the Polaris milestone, the canonical blocker (the legal compliance flag), and the related Slack thread.

1Linear sourcelinear

2linked memory meshgraph edge

cogniahq.tech /agent · Linear

ask Cognia:Did we ever ship the auth-throttling change?

Pulls the relevant ticket, status, the PR that closed it, and any post-mortem if the change caused issues.

1Linear sourcelinear

2linked memory meshgraph edge

Does Cognia poll or use webhooks?

Webhooks for new and updated issues, with a periodic full reconciliation as a backstop. Updates land in retrieval within seconds.

What about archived tickets?

We index them. Old archived tickets are often where the most useful 'we tried that and it broke' context lives.