Skip to main content
The Linear integration lets Roomote receive work from Linear, post progress back to the issue or agent session, and keep the full run available in the Roomote task view. When the Brain is configured, Roomote also indexes issues from the connected workspace so agents can recall product context before opening Linear. Linear is optional during onboarding. Connect it when your team wants Roomote to work from issues that already have product context, acceptance criteria, priority, or discussion.

​
Setup

1

Set up the OAuth app

On a self-hosted deployment, an administrator goes to Settings > Integrations, selects Set up Linear, and then selects Create the app to open the pre-filled manifest. The app name defaults to Roomote. After creating the private app, copy its client ID, client secret, and webhook secret back into Roomote. Roomote encrypts the saved credentials.
2

Connect the workspace

Select Connect Linear, approve the app in Linear, and return to Roomote. Deployments that provide R_LINEAR_CLIENT_ID, R_LINEAR_CLIENT_SECRET, and R_LINEAR_WEBHOOK_SECRET in the runtime environment skip Roomote’s credential-entry flow, but the Linear app must still use https://<your-roomote-origin>/api/mcp-oauth/callback as its OAuth redirect URI and https://<your-roomote-origin>/api/webhooks/linear as its AgentSessionEvent webhook URL.
3

Update or remove saved credentials

A deployment administrator can return to Settings > Integrations and select Configure on Linear. Saving a new client ID or client secret disconnects the current workspace so it can be authorized again. Removing saved credentials disables Linear but does not delete the app in Linear. Credentials managed by the deployment environment must be changed there.
4

Link your user account

Link your Linear identity when prompted so Roomote can associate issue activity with your Roomote user.
5

Make sure an environment exists

Roomote needs an environment that matches the repository or workspace the issue refers to.

​
Starting work from Linear

You can start Roomote work from a Linear agent session or by mentioning Roomote on an issue. Each agent session is a Roomote Session: Roomote reads the issue, its comments, and any agent guidance, answers directly when no workspace is needed, and otherwise picks the environment and starts a task bound to the session. Reply in the same session to redirect it, ask a follow-up, or steer a running task. The session links to the Session page in Roomote so you can follow the full transcript there. Good Linear asks include:
  • draft an implementation plan for this issue
  • investigate whether this bug is reproducible
  • implement the smallest fix that satisfies the acceptance criteria
  • explain what code paths this issue touches
  • open a PR and link it back to the issue

​
Progress and follow-up

Roomote posts its replies and the outcome of delegated tasks back to the agent session. While a delegated task runs, its thoughts, actions, and plan updates stream into the session live, and it asks its questions there when it needs your input. The Roomote Session and task views remain the best place to inspect logs, diffs, artifacts, and previews.

​
Brain context

The Brain keeps one durable page per visible Linear issue, including its current workflow state, team, project, priority, labels, assignee, description, and a bounded set of recent comments. When available, issue pages also include cycle, estimate, start date, parent, and related-issue context. Collection uses the same workspace connection configured above; it does not require another Linear token. Roomote refreshes changed issues incrementally and periodically checks the full visible issue set. Archived issues remain available as historical context. If an issue is deleted or the connected app can no longer see it, Roomote removes its page only after a complete visibility check, avoiding deletion from a partial or failed API response.
Put acceptance criteria and relevant repository links directly in the Linear issue before starting agent work.