Cogito + Linear
AI that knows what your team is shipping.
Linear is the team source of truth for engineering. Cogito connects to the workspace so anyone can ask about blockers, sprint status, or release readiness, with real-time triggers on issue events and a permission model that mirrors each user's native Linear roles.
Try Cogito FreeLive in under 5 minutes. No card required.
Built deep, not via MCP
Cogito's Linear integration is a first-class API connection with the depth, reliability, and permission inheritance most AI tools cannot match.
First-class Linear API integration with full webhook support for every issue event
Awareness of cycles, projects, and roadmap hierarchy, not just flat issues
Native priority, label, and estimate field reasoning
Personal-team support for restricted projects (security, HR, exec staff)
Personal, organizational, or both
Cogito's Linear integration ships with the connection model that fits your team. The layering story is the differentiator.
Organizational mode
Admin connects once. Whole team inherits.
The team shares one Linear brain. Anyone on the team can ask about sprint progress, customer-impacting bugs, or release readiness without per-user setup, and CS or sales reps can file issues with full context attached automatically.
Reads
- •Issues, projects, cycles, and roadmaps across the workspace
- •Comments, labels, priorities, due dates, and estimate fields
- •Team and member assignments
Acts on
- •Create new issues, with full property assignment
- •Update issue state, assignee, priority, labels, and estimates
- •Post comments on issues
- •Move issues between cycles and projects
Personal mode
Per-user connection. Private contexts only.
Personal Linear unlocks team-restricted projects: security teams that hide active vulnerability work from the broader org, HR teams tracking sensitive cases, exec staff teams with hiring or strategy items. Cogito uses personal credentials only in private contexts so restricted work never leaks.
Available in
- Private DMs with Cogito
- Personal 1:1 emails to Cogito
- Private webchats
Reads
- •Issues in teams the user has personal access to but the org integration does not
- •Private projects (security, HR, exec staff teams)
- •The user's own assigned, watching, and subscribed issues
Acts on
- •Create and update issues in the user's personal teams
- •Comment on personal-team issues
How the two modes layer
Both modes layer. The org integration sees engineering, design, and product teams. Personal mode unlocks the restricted teams (security, HR, exec staff) for the users who belong to them. A security engineer can ask about open vulnerabilities in a private DM and get answers from the locked-down team without those answers ever surfacing in shared channels.
Example
A 50-person company connects the org Linear: engineering, design, product, and CS teams visible. The security team has its own Linear team that hides issues from non-security members. Two security engineers connect their personal Linear. Now they can ask 'what is our current SLA on critical CVEs?' in a private DM and Cogito reasons across the security-team issues the rest of the org cannot see.
Real-time triggers
Webhooks fire the instant something changes in Linear. Build workflows that react in seconds, not minutes.
Issue created
Example use: Auto-summarize new bug reports and post the summary plus the customer context to #engineering.
Issue state changed
Example use: Alert the account exec on Slack when a Linear issue tied to their customer moves to "Done".
Issue assigned
Example use: DM the new assignee with a summary of the issue and links to all related customer conversations.
Comment posted
Example use: Tag the original reporter when an engineer comments on their issue with a question.
Cycle started or completed
Example use: When a cycle closes, draft the release notes from completed issues and post the draft to #releases.
Project milestone reached
Example use: Post a milestone announcement to the project channel when a Linear project hits a stage.
Common workflows
Concrete day-to-day moments where Cogito + Linear earns its keep.
Triage with customer context attached
A bug report lands in #customer-issues. A CS rep asks Cogito to file it. Cogito creates a Linear issue with the customer name, contract context from your CRM, the reproduction steps from the Slack thread, and the related issues it found by searching Linear for similar reports. The on-call engineer wakes up with a fully-scoped ticket, not a one-line bug description.
Release notes from a closed cycle
A cycle closes. Cogito reads every issue completed in the cycle, groups them by theme (features, fixes, improvements), pulls the user-visible language from PR descriptions, flags breaking changes for the CS team, and drafts release notes in a Notion page. The engineering lead reviews, edits two lines, and ships.
Real-time alerts on customer-tied issues
Set a workflow: "When any Linear issue tagged customer-impact moves to In Progress, DM the account exec for the affected customer with the issue link, the engineer assigned, and the estimated complete date." Cogito subscribes to the state-change webhook and fires the moment Linear updates.
Sprint planning by customer weight
Ask Cogito: "which of our open bugs have the most customer activity in the last 14 days?" Cogito reads every open Linear issue, cross-references the customer mentions in Intercom and Slack, weights by account size, and returns a ranked list. Sprint planning starts with data instead of debate.
Permission granularity
You pick the OAuth scopes at connect time - more access unlocks more capability, less access keeps Cogito narrowly scoped
Read-only or read-write per Linear team
Write access gated per role (engineers can create, CS can comment, admins can move state)
Personal mode mirrors each user's native Linear team membership
Per-cycle or per-project scoping available for narrow rollouts
Setup time
Under 90 seconds
- 1
Open Cogito settings, navigate to Integrations
- 2
Choose Organization (admin) or Personal (any user) and click Connect Linear
- 3
Authorize Cogito in Linear, scoped to the teams and workflow states you select
- 4
Confirm and return to Cogito
OAuth scopes / permissions
You choose which scopes to grant at connect time. Cogito's capability is bounded by exactly what you authorize. Grant read-only at first, expand later as you build trust.
- read (issues, projects, cycles, teams, members)
- write (comments, issue creation and updates, when enabled)
- admin (state machine changes, when enabled by Linear admin)
Common questions
Still have questions?
Get in touchDon't see what you need?
Cogito ships new integrations on customer request, typically within about 3 days. Sign up and ask.
Last reviewed