Linear
Connect
Connect Linear from the terminal. Pass --help for the flags Linear accepts.
polylane integration connect --type linearA personal API key with write access.
Connect Linear so agents can file Linear issues from investigations, update them, comment with findings, and start work when a Linear issue becomes urgent.
- In Linear, open Settings and go to Security & access.
- Under Personal API keys, create a key with write access. Use the key of a workspace admin to get webhook triage.
- Paste the key into Polylane. Polylane checks it against your Linear workspace and connects.
Your key is encrypted before it is stored, and the agent never sees it. On connect, Polylane registers a webhook labelled polylane in your Linear workspace.
How it works
What agents can do
Agents read your teams, workflow states, members and projects, and list, search and read Linear issues with their recent comments. They use this to find who owns a problem and what work is already open.
Agents can also change Linear:
- Create a Linear issue from investigation findings, with the evidence in the description.
- Update the state, priority, assignee, project, labels or due date of a Linear issue.
- Comment on a Linear issue with findings and status.
- Run a GraphQL query or mutation against the Linear API for anything that the other tools do not cover, such as labels, cycles or issue relations.
Each write, GraphQL mutations included, needs approval before it runs. A Linear issue that an agent creates from a thread links back to that thread.
Urgent issues start investigations
The webhook covers the issues in all public teams. When a Linear issue is created as Urgent, or its priority changes to Urgent, Polylane receives an alert, and the alert becomes a Polylane issue that an agent investigates. The alert recovers when the priority drops below Urgent, when the Linear issue is completed or canceled, or when someone deletes it.
Only a workspace admin can create the webhook in Linear. A key from another user still connects, and every agent tool works, but Polylane does not get urgent issues.
Context for pull request reviews
When a pull request names a Linear issue in its title, description, branch or commit messages, the impact assessment reads that Linear issue as context. Polylane reads it only when the author of the pull request is an owner, member or collaborator of the repository.
Key checks
Polylane checks the key every six hours. When Linear refuses it, Polylane tells you that the integration needs to be connected again.
Troubleshooting
"Invalid API key" error
- Use a personal API key from Security & access. OAuth tokens do not work here. Polylane sends the key as it is in the Authorization header, with no Bearer prefix, as Linear expects for personal keys.
- Make sure that the key is not revoked in Linear.
No alerts from urgent Linear issues
- Only the key of a workspace admin can create the webhook. Disconnect Linear, then connect it again with the key of an admin. A key replacement on a connected integration does not create the webhook.
Disconnecting
Disconnect Linear in Polylane. Polylane also removes the webhook that it registered. Then revoke the API key in Linear.
Disconnect
Disconnecting stops every sync and check and deletes the credentials Polylane held. Everything Polylane set up in Linear is removed as well; nothing is left behind.
polylane integration disconnect <id>Tools
4Operations agents can perform in threads.