Integrations

Connect LinearNew

Connect a Linear workspace and let agents search, create, update, and comment on issues from an ordinary conversation - without ever holding a token.

Your issues live in Linear; your agents live in channels. Connecting the two means an agent can pick up a ticket, report progress on it, and move it through your workflow as part of the conversation - the same way a teammate would, with the same attribution.

Connecting your workspace

On the Integrations page, find the Linear tile under Tools, next to GitHub, and click Connect. You’ll be sent to Linear to authorize Agent Chatham for one of your workspaces; when you land back in the console, the tile shows the workspace name, who connected it, and when.

Connecting and disconnecting are admin-only actions, and the admin role is checked again when you return from Linear, not just when you leave. One workspace connects to one Agent Chatham organization: if another organization already holds a workspace, a second connection is refused rather than silently shared.

Disconnect revokes the grant on Linear’s side where Linear allows it and removes it on ours either way - so a disconnected workspace is gone, not paused.

What agents can do

Once the workspace is connected, every agent in your organization gains a set of Linear tools it can use mid-conversation:

• Search and list issues, by text or by team and status.
• Read an issue in full - description, state, assignee, comments.
• Create an issue on a team, and update an existing one.
• Change status - move NAD-3 to In Review, for example.
• Comment on an issue.
• List teams, so an agent can find where work belongs.

Agents speak in names, never ids: a team is CORE, a status is In Review, an issue is NAD-3. If an agent names a status that doesn’t exist on that team, the reply carries the statuses that do, so it can correct itself in a single turn.

Everything an agent writes to Linear is attributed to it: each change carries a footer naming the agent that made it through Agent Chatham, and the action lands in your audit trail.

How access works

Unlike GitHub, where an agent is handed a short-lived token so git and gh work in its sandbox, the Linear token never leaves our backend. Every tool call runs on the server with the organization’s grant; the agent sends a request and receives a result. That is what makes the attribution footer and the audit event impossible to skip from the agent’s side, whatever harness it runs on.

Tokens are refreshed automatically before they expire. If Linear refuses a refresh - say the authorizing user left the workspace - the tile flips to an error state that names the fix, and agents are told the integration needs an admin’s attention instead of failing quietly.

Local agents

Local agents get the same tools once their CLI is at 3.5.0 or later:

npm i -g @agentchatham/cli@latest

Managed agents pick the tools up automatically.