Connect Linear to Rocket and build from your tickets. Rocket reads descriptions, acceptance criteria, and briefs, then writes follow-up tickets back.
Point Rocket at a Linear ticket and it builds the feature. No copy-pasting requirements, no manually updating your board.Rocket reads your issue descriptions, acceptance criteria, and project briefs directly from Linear. When the build is done, it writes follow-up tickets and status updates back.
Linear uses OAuth, so no API key is needed. It is a workspace-level connector, so connect it once and it is available across all tasks.
Web Browser
Mobile App
You can connect from three places. All do the same thing.Option 1: From chatPaste a ticket URL or ask Rocket to create issues. Rocket detects the intent and shows a Connect button inline. Click it to open the authorization flow.
Linear connection prompt in chat
Option 2: From the Connectors tabClick the ... button in the preview toolbar, then select Connectors.
Open Connectors from the toolbar
Click the Linear card, then click Connect.
Linear card in the Connectors panel
Option 3: From workspace Settings
Connect from workspace Settings
Connect once from Settings and it is available across all tasks.
After clicking ConnectA Linear authorization screen opens. Review the permissions and click Authorize.
Linear OAuth authorization screen
A green dot appears next to Linear when the connection is active.Disconnect
Disconnect a service
Disconnect or switch accounts from workspace Settings.
You can connect from two places. Both do the same thing.Option 1: From chatPaste a ticket URL or ask Rocket to create Linear issues. Rocket shows a Connect button inline. Tap it to open the authorization flow.Option 2: From the Connectors tab
Tap the More button in the header.
Tap Integrations.
Tap the Linear card, then tap Connect.
After tapping ConnectA Linear authorization screen opens. Review the permissions and tap Authorize.A green dot appears next to Linear when the connection is active.
Be specific in your tickets. Rocket builds from what is written. Tickets with detailed descriptions, clear acceptance criteria, and labels produce better output than vague ones.
Use issue URLs, not project names. Pasting a direct URL gives Rocket unambiguous context. Referring to a project by name can match the wrong one.
For large workspaces, scope it down. Reference a specific project or issue instead of asking Rocket to read the full workspace backlog.
Write-back creates real tickets. When Rocket creates or updates Linear issues, they appear in your board immediately. Review them before sharing with your team.
Permissions apply. Rocket respects Linear’s access controls. It can only read and write what the connected account has permission to access.