Linear
Read, create and update Linear issues, projects and comments from agent work.
Connect it with: Sign in (OAuth), API key, MCP. Linear's own documentation: https://linear.app/developers/oauth-2-0-authentication.
What agents can do
Connect Linear so the agents working your tasks can reach it. With it connected, they can:
- Through Linear's MCP server, once the secret is linked to a project, use Linear's ready-made tools to search and update issues.
- Read the Linear issue a Jaah task names: its description, status, labels, sub-issues and comments.
- Create follow-up issues in the right team when an agent finds more work.
- Comment on an issue with progress, a summary or a pull request link.
- Move an issue to In Review or Done and update its assignee or labels when the work lands, if you granted write access.
- List a project's or cycle's open issues to plan or report on work.
- Start a Jaah task when someone delegates an issue to Jaah, @mentions Jaah or adds the start label, once the secret is connected as an issue tracker (see Start tasks from Linear).
Before you start
- A Linear account that is a member of the teams agents should reach.
- To connect with a sign-in: a Linear workspace admin - the sign-in installs Jaah in the workspace as an app that people can delegate issues to and @mention.
- To connect with an API key: permission to create a personal API key. Admins can restrict API keys to admins only (Settings > API).
- A Jaah account. Anyone can add a personal secret; an organization secret needs an Org Owner or Admin.
Connect with Linear
This is the quickest way in: you sign in to Linear and approve what Jaah asks for. You never copy a key.
- In Jaah, open Secrets and select New.
- Search for Linear and select its card.
- Give the secret a name you will recognize, such as the account or workspace it reaches, and choose who can use it (see Who can use it).
- Select Connect Linear. Linear's sign-in window opens.
- Sign in to Linear if asked, check the access listed, and approve it.
- You land back in Jaah on the new secret, which reads Connected once its test passes.
If the button reads Jaah app not configured, this Jaah has no app registered at Linear yet. Use an API key, or your own OAuth app, until it does.
Scopes Jaah requests
Jaah asks Linear for these scopes, and no others. A scope marked optional is a checkbox on the Connect screen: untick it and agents simply cannot do that part.
| Scope | Why Jaah asks for it | Required |
|---|---|---|
read | Read issues, projects, cycles, teams and comments, and see whose account is connected | Yes |
issues:create | Create issues when an agent finds follow-up work | No — you may untick it |
comments:create | Comment on issues with progress and pull request links | No — you may untick it |
write | Update issues: change status, assignee, labels and fields when work is done | No — you may untick it |
app:assignable | Let people delegate issues to Jaah, so a delegated issue starts a Jaah task | No — you may untick it |
app:mentionable | Let people @mention Jaah in issues and comments, so a mention starts or continues a Jaah task | No — you may untick it |
Connect with an API key
Prefer this when you cannot sign in with Linear — for example a service account, or a token your admin issued. On the Connect screen select Use an API key instead.
Find each value first:
- Personal API key: Linear > Settings > Account > Security & access > Personal API keys > New API key: name it Jaah, choose Full access or only the teams and permissions agents need, select Create, then copy the key - Linear shows it once.
Then add it to Jaah:
- In Jaah, open Secrets, select New, and pick the Linear card.
- Name the secret and choose who can use it.
- Select Use an API key instead.
- Fill in Personal API key.
- Select Save. Jaah tests the secret straight away (see Test the connection).
Jaah encrypts what you type and never shows it again — not to you, and not to an admin.
Use your own OAuth app
Register your own OAuth app at Linear when your company requires apps it controls, or before this Jaah has an app registered there.
- Create an OAuth app in Linear's developer console, https://linear.app/settings/api/applications/new (Linear's documentation).
- Set its redirect URI to
https://app.jaah.ai/api/credentials/connect/callback(on your own Jaah, its console address followed by/api/credentials/connect/callback). - Give it the scopes in Scopes Jaah requests.
- Copy its client ID and client secret.
- In Jaah, start a new Linear secret, select Use your own OAuth app, paste both values and select Connect Linear.
The client secret is stored with the connection, encrypted, like any other secret value.
Test the connection
Select Test on the secret. Jaah calls Linear's API once (POST https://api.linear.app/graphql) with the stored values, and shows who it answered as, or which value Linear refused and the status it answered. Jaah also tests automatically when you save or reconnect.
The last result and its time stay on the secret's page, so you can see whether it still works without testing again.
Who can use it
Every secret has an owner, and the owner decides who can use it:
- Personal — only your own tasks can use it. This is the default.
- Organization — every task in the organization can use it. Only Org Owners and Admins can choose this.
- Attached to a project — every task on that project can use it, whoever started the task. See Attach a secret to a project.
More on owners and access: How secrets work.
Use it in an agent session
An agent asks for the secret with its credential_get tool, by the secret's path, when it needs it, and gets the values for that one call. The path is the owner's prefix and the secret's name:
org/<name>for an organization secret,projects/<project>/<name>for one attached to a project,me/<name>for your personal one.
A signed-in connection hands the agent a live access_token, with access_token_expires_at. Jaah refreshes it before it expires, so an agent never handles a refresh token.
A key connection hands the agent its fields: api_key.
Tell the agent in your task description which secret to use, for example “use the Linear secret org/linear”.
Link Linear's MCP server to a project
Linear also runs an MCP server, which gives agents ready-made Linear tools instead of raw API calls. A project's agents get those tools only once you link the secret to the project:
- Open the project and its MCP tab.
- Select Link, pick the Linear secret, and confirm.
- New tasks on the project start with the Linear tools. Tasks already running keep the tools they started with.
Jaah connects agents to the server through a local bridge, so the token never appears in the agent's configuration or its transcript. A Google Antigravity session in the terminal runtime runs without these tools; on ACP it gets them.
Manage, rotate or disconnect
Everything is on the secret's page under Secrets:
- Rotate a key: create a new key at the vendor first, then select Replace on the secret and paste it. Revoke the old key at Linear once the test passes. Steps: Replace or delete a secret.
- Reconnect: when Linear ends the grant (a password change, a revoked app, an expired refresh), the secret shows Needs reconnect. Select Reconnect and sign in again; agents get the new token on their next call.
- Disconnect: select Delete. The stored values are destroyed and agents lose access on their next call. To end access at Linear's side too, revoke Jaah in Linear's settings, or revoke or delete the key at Linear.
Limitations
- With a sign-in, agents act as the Jaah app: issues and comments they create show Jaah as the author. With an API key they act as the key's owner.
- A personal API key reaches every workspace team its owner can see, unless you limited it to some teams when you created it.
- Linear rate-limits API requests per user and per complexity; very large bulk edits can be slowed or refused.
- Linear's sign-in grants access to one workspace at a time; connect again for each extra workspace.
- Agents can do only what the connected Linear account and its granted scopes allow.
Troubleshooting
Test says Linear rejected the personal API key (AUTHENTICATION_ERROR)
The key was revoked, mistyped or belongs to a deactivated user. Create a new key under Settings > Account > Security & access and select Replace on the secret.
Test says Linear rejected the access token
The sign-in was revoked in Linear (Settings > Account > Security & access > Authorized applications) or the workspace removed the app. Select Reconnect.
Linear shows Invalid redirect_uri on the sign-in screen
You are using your own OAuth app and its Callback URLs do not include the redirect URI on this page. Add it exactly and try again.
Agents can read issues but cannot create or update them
The connection was approved without the write scopes. Reconnect and keep issues:create, comments:create and write ticked, or use a key with write access.
Still stuck? Select Test and read the result: it names the value Linear refused and the status it answered.
FAQ
Which account do agents act as?
With a sign-in, the Jaah app installed in your workspace. With an API key, the Linear member who created the key.
Can I limit agents to one team?
Yes, with an API key: when you create it in Linear, choose only that team. A sign-in grants what the account can see in the workspace.
Does the connection expire?
A sign-in renews itself: Jaah refreshes the 24-hour access token automatically. An API key lasts until you revoke it.
Can Jaah or an admin see the key or token?
No. Jaah stores it encrypted and never shows it again. Only the tasks allowed to use the secret receive it, at the moment they ask for it.
Can I connect more than one Linear account?
Yes. Add one secret per account, each with its own name, and tell the agent which one to use.