Linear agents that triage the backlog as it arrives
Paste one Linear API key, limited to the teams you choose. Qoren registers the webhooks, wakes an agent when issues and comments change, and lets it search, create, comment and update.
Integrations is in early access: Qoren is turning it on account by account. Already have access? Open Integrations
How do I connect Linear to an AI agent?
Create a personal API key in Linear under Settings > Security & access, limited to the teams your agents work on. Give it Admin if Qoren should set up triggers, because Linear only lets admins create webhooks. Paste it in Qoren, pick an event such as Issue created, and grant an agent access. Archiving an issue always waits for your approval.
What agents do with Linear
Example jobs, each built only from the events and tools listed further down. Write the agent's rules in plain words; these are starting points, not presets.
For agencies running it for clients
Triage a client's incoming requests
When an issue is created, the agent reads it, searches for a duplicate, sets the priority and assignee and comments with what it needs to get started.
- Wakes on
- Issue created
- Uses
- Read an issue
- Find issues
- Update an issue
- Comment on an issue
Done means the client hears about it
When an issue moves to Done, the agent adds it to the week's list and writes the client's Friday update from it.
- Wakes on
- Issue status changed
- Uses
- Read an issue
- List a team's issues
For founders running it for themselves
Bug reports from email become issues
When a customer reports a bug to the agent's mailbox, it searches Linear for the same problem and creates the issue in the right team if it is new.
- Uses
- Find issues
- Create an issue
Answers on your own issues
When someone comments on an issue, the agent reads the thread and replies with the context it can find.
- Wakes on
- Comment added
- Uses
- Read an issue
- Comment on an issue
The path one event takes
5 Linear events that can wake an agent
Pick one on an agent's Triggers tab. Each event can arrive on its own, as a digest, or as the latest state of a record, and events that do not match your conditions are logged as Filtered, with no turn and no charge.
| Event | When it fires |
|---|---|
| Issue created | An issue is created in any public team. |
| Issue updated | Any field of an issue changes: status, assignee, priority, labels, title. Public teams only. |
| Issue status changed | An issue moves to another status, for example In Progress or Done. Add a condition on data.state.type to react to one kind. |
| Issue assigned | An issue is assigned to someone, or to someone else. |
| Comment added | Someone comments on an issue in a public team. |
7 tools agents can use
Curated Linear tools, not a raw API: each returns only the fields the job needs. A read only grant never gets a write tool, and tools marked Always asks wait for a person's approval whatever the agent's autonomy setting.
| Tool | What it does | Access | Approval |
|---|---|---|---|
| Find issues | Search Linear issues by text. Returns identifier, title, status, team, assignee and link. | Read | None |
| Read an issue | Read one Linear issue: title, description, status, priority, team, assignee, labels and its first 10 comments. | Read | None |
| List a team's issues | List one team's issues, most recently updated first, at most 30. | Read | None |
| Create an issue | Create a Linear issue in a team. Search first so you do not add a duplicate. | Write | Per autonomy setting |
| Comment on an issue | Comment on a Linear issue. | Write | Per autonomy setting |
| Update an issue | Change a Linear issue's status (by name, for example In Progress), assignee (by email) or priority. | Write | Per autonomy setting |
| Archive an issue | Archive a Linear issue. Always asks a person to approve first. | Write | Always asks |
How connecting Linear works
- 01Make a Linear key with the least access it needs, following the guide below. Only the account owner can connect a tool.
- 02Paste it in Qoren. Qoren checks it before saving: which account it belongs to, what it can do and, where Linear says, when it expires.
- 03Give an agent access, read only or read and write. An agent cannot use a tool it was not given.
- 04Pick the events that should wake the agent. Qoren registers the Linear webhook itself, so there is no URL or signing secret to copy.
Making the Linear key
- 1
Use a workspace admin for triggers
Linear only lets workspace admins create webhooks. If you want triggers, create the key as an admin.
- 2
Create a personal API key
In Linear, open Settings > Security & access and create a new personal API key named Qoren.
Qoren's connect dialog links straight to this page in Linear.
- 3
Limit it
Choose Admin if Qoren should set up triggers, or Read if agents only look things up. Give Write, Create issues or Create comments only if agents should change things, and limit the key to the teams your agents work on.
- 4
Paste the key here
Copy the key and paste it here. Linear shows it once. Never send it by email or chat.
Connecting a client's account? Send a link
An agency does not need its client's key. Send a connect link instead: it shows your agency's name and the exact permissions to tick, works once, expires after 7 days and can be revoked. The client pastes the key on that page, Qoren encrypts it on arrival, and you only ever see its last four characters. A client's connection is used only by that client's agents. Connect links come with Clients, on the Ultimate, Business and Enterprise plans.
Client connect linksSecurity in plain words
Keys never reach the agent's machine
The Linear key is encrypted at rest with AES-256-GCM and used only inside Qoren's own calls to Linear. It is never written to the agent's environment, and after you connect only its last four characters are shown.
Read only until you say otherwise
Each agent gets read only or read and write access, granted one agent at a time. The Linear key itself can be limited too, and the guide asks for the least it needs.
Risky actions always ask
In Linear, these always wait for a person's approval, whatever the agent's autonomy setting: archive an issue.
Capped reads and a full audit log
By default an agent reads at most 500 records an hour from one connection. Every call, read or write, lands in the audit log with the agent, the tool and the record ids.
Event data is treated as data
Events reach the agent fenced off as data, with a warning not to follow instructions inside them. For 30 minutes after an agent reads connected data, a Qoren tool that would send it outside your account waits for your approval.
Stored events expire
Qoren keeps event bodies for 7 days on Starter, 30 on Pro, 90 on Ultimate and 180 on Business, then removes them and keeps only the metadata.
Linear limits worth knowing
When you disconnect, Qoren cannot revoke the key at Linear, so it tells you where to delete it. In Linear, open Settings > Security & access and revoke the key.
- Linear only lets workspace admins create webhooks, so the key needs Admin for triggers. Read is enough if agents only look things up.
- Triggers cover the workspace's public teams. Private teams are not included.
- Linear does not let Qoren read a key's permissions, so a permission you did not give shows up as a refused call rather than at connect.
Frequently asked questions
Why does the Linear key need Admin?
Only for triggers. Linear lets only workspace admins create webhooks, which is how Qoren wakes an agent. If your agents only look things up, a Read key is enough, and you can limit any key to specific teams.
Do triggers see issues in private teams?
No. Qoren's Linear webhooks cover all public teams in the workspace. Issues in private teams do not wake an agent.
Does my agent ever see the Linear key?
No. Qoren encrypts the key as soon as it arrives and uses it only inside its own calls to Linear. The key never reaches the agent's machine, is never shown again after you connect, and the agent only gets the results of the tools you allowed.
Can an agent archive an issue without asking?
No. In Linear, these tools always wait for a person's approval, whatever the agent's autonomy setting: archive an issue. The approval shows the exact details the agent wants to send.
ApprovalsWhat happens when I disconnect Linear?
Qoren deletes the webhooks it registered, deletes the stored key, pauses the triggers that used it and removes stored event bodies. It cannot revoke a key at Linear, so it shows you where to delete it: In Linear, open Settings > Security & access and revoke the key.
What does the Linear integration cost?
Connecting tools comes with every Qoren plan, with no limit on connections, once Integrations is on for your account. It is in early access for now, turned on account by account. An event that wakes an agent uses credits like any other agent turn, and each trigger has an hourly cap.
Qoren pricingConnect Linear once. Let agents handle the rest.
Integrations is in early access, turned on account by account. Request it and tell us how your agents should use Linear.