Skip to main content
Stop context-switching between your IDE and Linear. When agents connect to Linear, they can create issues from bugs they find, update status as they work, and link code changes to tickets automatically.

​
What agents can do with Linear

Once connected, agents can:
  • Create issues from context: Find a bug? The agent creates an issue with steps to reproduce, relevant code snippets, and suggested labels.
  • Update as they work: Agents can move issues to “In Progress” when they start and “Done” when they finish.
  • Search and reference: Ask about related issues, find duplicates, or get context from existing tickets.
  • Add comments: Document findings, link PRs, or note blockers directly in Linear.

​
Example workflows

"Create a Linear issue for this authentication bug with the stack trace"

"Show me all high-priority issues assigned to me in the API project"

"Move issue ABC-123 to In Progress and add a comment that I'm starting work"

"Find any existing issues about rate limiting before I create a new one"

​
Connect Linear

​
Step 1: Organization setup

An admin needs to enable Linear for your organization first.
  1. Go to Organization Settings > Integrations
  2. Find Linear and click Enable
  3. Configure default workspace settings if needed
Organization integration settings

​
Step 2: Authenticate your account

Once enabled, connect your personal Linear account:
  1. Go to User Settings > Integrations
  2. Click Connect next to Linear
  3. Authorize Ona to access your Linear workspace
  4. Select which workspaces to connect
User authentication for Linear

​
Verify it works

Start a conversation with an agent and try: 
Show me my open Linear issues
If you see your issues, you’re connected. If not, verify both organization enablement and your personal authentication are complete.

​
Tips for effective use

Be specific about projects: If you have multiple Linear teams, specify which one: “Create an issue in the API team for this bug.” Include context: The more context you give, the better the issue: “Create an issue for this null pointer exception, include the stack trace and the user flow that triggers it.” Use with AGENTS.md: Add your Linear conventions to AGENTS.md so agents know your labeling system and workflow stages.

​
Troubleshooting

​
”Agent features are not active”

This warning means the app authorization for agent capabilities (like @mentions and webhooks) is missing or expired. Basic features like reading and creating issues via MCP tools still work with your personal token. Click Authorize app to start the authorization flow.

​
Authorization shows “already installed”

Linear allows only one app installation per workspace. If another Ona organization has already authorized the app on the same Linear workspace, the authorization flow will show that the app is already installed instead of issuing a new token. To resolve this:
  1. In Linear, go to Settings > Integrations > Ona and remove the existing installation
  2. Return to Ona and click Authorize app to re-install for the correct organization
Only one Ona organization can have agent features (webhooks, @mentions) active per Linear workspace at a time. Other Ona organizations connected to the same workspace can still use MCP tools (read/write issues) through personal authentication.

​
Next steps