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. Roomote uses the issue context and may ask you to confirm the workspace before it launches. 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