Skip to main content
Connect your Linear workspace to let CloudThinker agents search issues, projects, cycles, teams, comments, and status changes, and surface what is blocked or needs attention next. Linear uses OAuth, so you do not need to create a Linear API key or paste credentials into CloudThinker. Updates to work items stay deliberate actions that wait for your approval.

Prerequisites

  • A Linear account with access to the teams and projects you want CloudThinker to work with.
  • Permission to authorize CloudThinker through Linear’s OAuth flow.

Setup

1

Open CloudThinker

Navigate to Connections → Linear in your CloudThinker workspace.
2

Start the OAuth flow

Click Connect to open Linear’s authorization page.
3

Authorize CloudThinker

Sign in to the Linear account with access to the right workspace, then approve access.
4

Return to CloudThinker

After authorization, CloudThinker stores the OAuth tokens and shows a Connected status.

Connection details

Linear uses OAuth — there are no connection fields to enter manually.

Required permissions

CloudThinker inherits the Linear access granted during OAuth — agents see the teams, projects, and issues the authorizing account can see.
  • Read operations include searching issues, projects, cycles, teams, comments, and status history.
  • Updates to issues and other work items are gated by approval in CloudThinker.

Agent capabilities

Once connected, agents can:

Verify the connection

Example prompts

Troubleshooting

Your browser may be signed in to the wrong Linear account, or not signed in at all. Sign in to the intended account and retry the connection flow from Connections → Linear.
The OAuth flow was completed with an account that lacks access to those teams. Reconnect using a Linear account with the right team membership.
The authorization may have been revoked in Linear. Remove the connection in CloudThinker and run the OAuth flow again.

Security

  • Least privilege — grant only the permissions the agents need for your use case; start read-only and widen later.
  • Read-only by default — use read-only credentials unless you want agents to make changes through this connection.
  • Rotate credentials — rotate keys and tokens on your normal schedule; CloudThinker picks up the new value when you update the connection.
  • Revoke on offboarding — remove the credential at the provider when you delete a connection or a teammate leaves.
  • Approval for updates — changes to Linear work items wait for explicit approval in CloudThinker.
  • Scope by account — the connection sees exactly what the authorizing Linear account sees.

Asana Connection

Project and task management

ClickUp Connection

Workspace and task tracking