OAuth PathFor AI Agents
Back to Guides
Generated on 2026-10-31: Provider OAuth rules and review policies change frequently. Always verify current submission requirements with the official Linear documentation before submitting for production approval.

Linear's developer platform features a straightforward self-serve OAuth application registration process within user/workspace settings without mandatory upfront reviews for private integrations.

linear.appGenerated on 2026-10-31
At a glance
Executive breakdown in plain language
Difficulty
EASY

Linear's developer platform features a straightforward self-serve OAuth application registration process within user/workspace settings without mandatory upfront reviews for private integrations.

Setup Time
15-30 minutesCommunity reported

Active engineering effort required to register the OAuth app, set redirect URLs, and obtain credentials.

Approval Wait
InstantFrom official docs

Applications created in the workspace settings are available immediately for authorization.

Biggest Blocker
Redirect URI mismatch errors during authorization code exchange.

Fix: Ensure that the redirect URI sent in the initial authorization request exactly matches character-for-character the redirect URI registered in the Linear application settings.

Required Before Starting
From official docs
• Linear workspace account (From official docs)
• Workspace administrator or member privileges to create applications (From official docs)
• Valid HTTPS redirect URI (From official docs)

Step-by-Step Setup Guide

4 steps
From official docs

Follow these sequential actions to register your OAuth application and configure endpoints.

1

Navigate to Workspace Settings

Log into Linear, click on your workspace name in the top left, and navigate to Settings > API & Integrations or Developer settings.

Open in Linear Console
2

Create New OAuth Application

Go to the Applications section and click 'New Application' (or 'Create app').

Open in Linear Console
3

Configure App Details and Redirect URIs

Provide the application name, description, logo, and your backend's OAuth callback redirect URI(s).

4

Obtain Client ID and Client Secret

Save the generated Client ID and Client Secret securely to use in your AI agent backend implementation.

Common Blockers & Fixes

2 blockers
Community reported

Anticipate the pitfalls and approval rejections that catch most agent developers off guard.

Redirect URI mismatch errors during authorization code exchange.
Action Plan: Ensure that the redirect URI sent in the initial authorization request exactly matches character-for-character the redirect URI registered in the Linear application settings.
Token expiration or missing offline access.
Community reported
Action Plan: Ensure proper handling of refresh tokens if the agent needs long-term background access without repeated user re-authentication.

What an agent can do vs what you must do

Agent vs Developer
From official docs

A clear division of labor: tasks your autonomous agent can handle vs actions requiring human developer authorization.

What an Agent Can Do
  • Construct the authorization URL with required query parameters (client_id, redirect_uri, scope, state)
  • Handle the OAuth callback code exchange via backend HTTP POST request
  • Automatically store, encrypt, and refresh access tokens
What You Must Do Yourself
  • Log into the Linear web interface and complete 2FA
  • Navigate to workspace settings to create the OAuth application and copy credentials
  • Configure secure environment variables for Client ID and Client Secret

Managed OAuth vs Custom Credentials

From official docs

Evaluate whether using a managed integration platform (like Composio) is sufficient or if you must create your own app.

This tool was built for a Composio assignment, and Composio sells managed OAuth.
When Managed OAuth is Enough
Building multi-tenant AI agents where users connect their own Linear accounts via a managed integration provider like Composio that handles credential storage and token refreshing. Note: This tool was built for a Composio assignment, and Composio sells managed OAuth.
When Custom Credentials are Required
Building a tightly-scoped internal enterprise tool or commercial product requiring a branded Linear OAuth client experience and direct control over token storage policies.

Key Claims & Verification Status

Unverified estimate

Specific factual statements evaluated against sources.

Linear allows developers to create OAuth applications directly from workspace settings.
OAuth applications created via workspace settings have instant availability without manual review waits.
Unverified estimate

Official Sources & Documentation

1 sources
From official docs
Linear API Documentation - OAuth

Open Questions & Uncertainties

2 open questions
Unverified estimate

Areas currently subject to policy changes or requiring ongoing real-world verification.

  • What are the exact criteria and process if a developer wants to list their Linear OAuth app publicly in the Linear Integrations Directory?
  • Are there strict rate limits enforced specifically on custom OAuth client applications?