Skip to main content
Integrations · Linear
Guild agents send GraphQL queries and mutations to Linear, letting them read and update issues, projects, and cycles on your behalf. Guild stores the credential server-side and injects it into each request, so agent code never sees your API key or OAuth token. Credential policies and audit apply to every call the agent makes.

Book a demo

See how teams govern agents that use Linear.

Talk to sales

Get access to Guild, then connect Linear to your first agent.

What the Linear integration exposes

The integration provides the linear_graphql_query tool, which sends a GraphQL query or mutation to the Linear API. Through this tool, agents can reach Linear issues, projects, and cycles. The tool accepts arbitrary GraphQL, so agents can read data, create records, or update state in Linear depending on the query they send.

How it works

1

Open Credentials in Guild

Go to Credentials in Guild. The page lists services you can connect.
2

Connect your Linear account

Click Linear and enter your API key or authorize via OAuth. API keys do not expire; OAuth tokens refresh automatically.
3

Spread the tools into your agent

Import linearTools from the package and spread it into your agent’s tools object. Guild resolves the credential server-side on every call.

Why Linear access needs governing in an agent

The linear_graphql_query tool accepts arbitrary GraphQL, including mutations that create, update, or delete Linear records. Guild’s credential policies let you write ALLOW and DENY rules that the credential proxy enforces before any request reaches Linear. Rules can target specific operations, specific agents, or specific workspaces, all on the same connected credential. Credentials are stored and injected server-side through Guild’s credential proxy, so agent code, prompts, and containers never see the token. You can scope a Linear credential to one workspace, one member, or one agent using the credentials page. Every request the proxy forwards has already passed the policy check. An unmatched request is denied by default once you remove the allow-all policy.

About the Linear integration

The @guildai-services/guildai~linear package gives your agents access to Linear issues, projects, and cycles through Guild’s Linear integration.

Authentication

  • Type: API key or OAuth 2.0
  • Token management: API keys do not expire; OAuth tokens refresh automatically

Setup

1

Open Credentials

Go to Credentials in Guild.
2

Connect Linear

Click Linear and enter your API key or authorize via OAuth.

OAuth scopes

Scopes Guild requests in the latest published version of guildai~linear:

Usage

Selecting specific tools

The integration has one tool, linear_graphql_query, which sends a GraphQL query or mutation to the Linear API.

Tools

Tools in the latest published version of guildai~linear:

Frequently asked questions

Yes. The integration supports both API key and OAuth 2.0. OAuth tokens refresh automatically; API keys do not expire.
Yes. Credential policies let you write ALLOW and DENY rules scoped to specific operations, agents, or workspaces. Guild’s credential proxy enforces them before the request reaches Linear.
No. The catalog entry lists no webhook events for this integration. Agents query Linear on demand using the GraphQL tool rather than reacting to inbound events.
No. Guild injects the credential server-side through its credential proxy. The token never enters the agent’s code, container, prompt, or state.

Put a governed agent on Linear this week

Book a demo

See how teams govern agents that use Linear.

Talk to sales

Get access to Guild, then connect Linear to your first agent.
Also runs on Guild: Azure DevOps · Bitbucket · GitHub · Google Compute Read: Docs: Credential policies · Credentials · Tools in agents
Last modified on November 4, 2026