Linear Integration | Rocket.new Build

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.

What you can do

Build from a ticket

Paste a Linear issue URL into chat. Rocket reads the title, description, and acceptance criteria, then generates the implementation.

Build from a project

Paste a Linear project URL. Rocket reads all child issues and the project brief, then builds the full scope.

Fix bugs from reports

Paste a bug ticket URL. Rocket reads the screen name, expected vs actual behavior, and generates a targeted fix.

Use ticket copy in your app

Pull feature descriptions and value propositions from a ticket directly into your app’s UI copy.

Create follow-up tickets

After building, ask Rocket to create QA tickets, edge case tickets, and testing tasks back in Linear.

Auto-update ticket status

Ask Rocket to move the original ticket to Done and leave an implementation comment when the build finishes.

Connect Linear

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.

Rocket chat panel showing a Connect prompt for Linear.

Option 2: From the Connectors tabClick the ... button in the preview toolbar, then select Connectors.

Toolbar dropdown with Connectors option highlighted.

Click the Linear card, then click Connect.

Connectors panel showing the Linear card with a Connect button.

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 screen showing Rocket requesting read and write access to your workspace.

A green dot appears next to Linear when the connection is active.Disconnect

Disconnect a service

Disconnect or switch accounts from workspace Settings.

Example prompts

Replace [LINEAR_URL] with your actual issue or project URL.

Reading from Linear

What you want	Prompt to use
Build a feature from a ticket	`Build the feature described in [LINEAR_URL]. Read the full requirements, edge cases, and acceptance criteria before generating.`
Build from a full project	`Read the Linear project at [LINEAR_URL] and build the described UI including all screens referenced in the project brief.`
Fix a bug from a report	`Fix the bug described in [LINEAR_URL]. Read the screen name, expected behavior, and actual behavior and generate a targeted fix.`
Apply a requirement change	`The requirements changed in [LINEAR_URL]. Read the updated ticket and modify the relevant parts of the app.`

Writing back to Linear

What you want	Prompt to use
Create QA tickets	`Create a Linear project with QA tickets for the checkout flow I just built. Include test cases based on the implementation.`
Log client change requests	`Create a Linear project with tickets for each client-requested change, organized by page and priority.`
Document what was built	`Create a Linear document describing what was built and link it to the original ticket at [LINEAR_URL].`
Create follow-up tasks	`Create Linear tickets for all the follow-up work from this build: enhancements, edge cases, and testing tasks.`

Tips

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.

What’s next?

Notion

Connect your docs and wikis so Rocket builds with full product context.

Google Workspace

Read from Docs, Sheets, and Calendar to build context-rich apps.

GitHub

Push your code to a repository and keep version history.

All connectors

Browse every available integration.

​What you can do