Linear

Ryven installs into Linear as an agent. Team members assign or @mention Ryven on an issue and the conversation happens inside a Linear agent session — progress, clarifications, and the final result all appear in the issue's activity feed.

Like the other Ryven integrations, Linear goes through the same routing — Ryven decides whether you're asking a question, starting a new task, asking for a code review, or following up on something in flight, and responds accordingly.

Setup

Go to Settings > Integrations in the Ryven dashboard
Click Connect Linear
Authorize Ryven against your Linear workspace
Approve the requested scopes when prompted — Ryven needs read/write access plus permission to be assigned and mentioned

Once connected, Ryven appears in the assignee picker and in @mention autocomplete inside Linear.

Triggering a task

There are three ways to start a conversation with Ryven inside Linear:

1. Assign an issue to Ryven

Open any issue and set the assignee to Ryven. This opens a new agent session on the issue and Ryven starts working with the full issue context as its prompt.

2. @mention Ryven in a comment

@Ryven can you take this one? The bug repro is in the description.

Works on any existing issue. Ryven reads the issue plus the comment thread and starts an agent session.

3. Prompt Ryven from the Linear UI

Linear surfaces an explicit prompt action for agent integrations (button or keyboard shortcut in the issue view). This triggers the same agent session flow.

What Ryven reads from an issue

When a task is triggered from Linear, Ryven pulls:

Title — the issue summary
Description — the full issue body
Comments — prior discussion and any clarifications
Linked artifacts — if a GitHub PR or Slack thread is linked to the issue, that context is stitched in too

How Ryven reports progress

Ryven reports back into Linear's agent activity feed inside the session. You'll see activity entries as the task moves:

Progress — ongoing updates as Ryven clones, reads code, runs setup, edits files
Response — the final success message when the task completes
Error — a terminal failure message if something went wrong that Ryven couldn't recover from

Every comment Ryven writes into Linear ends with an identity signature — _Sent by Ryven via a connected Linear app._ — so users can always tell agent-authored text from human comments.

Workflow state automation

Ryven also moves the issue through your Linear workflow states as the task progresses:

Task phase	Target Linear state
Task starts	`In Progress`
Pull request opened, CI running	`In Review`
CI passes, PR ready	`Done`

Linear workspaces don't standardize state names, so Ryven matches on common aliases — In Progress, Doing, WIP, In Development, and so on. If none of them match your workflow, Ryven skips the state update rather than guessing. Your task still runs; only the issue state stays put.

A workflow state update failing never causes a task to fail — if Ryven can't move the issue, the PR still ships.

Identity mapping

For Linear-triggered tasks to be attributed to the correct workspace member, link your Linear account in Settings > Profile > Linked Identities > Link Linear. If a member hasn't linked their account, the task still runs but attribution in the Runs list may fall back to the workspace installer.

In the dashboard

Tasks triggered from Linear show Linear as the trigger source in the Runs list. The task detail view links back to the Linear issue for full traceability.

Quick reference

Pattern	How
Start a task on an issue	Assign the issue to Ryven
Follow up mid-run	`@Ryven <message>` inside the same session
Ask a question without starting a task	`@Ryven what repo would this land in?` — Ryven replies in the session without touching any code
Track progress	Read the agent activity feed inside the issue

Connect integrations — initial setup flow for all integrations
Jira — the analogous flow for Jira Cloud
GitHub — single-repo trigger flow via GitHub

On this page