Integrations

Linear

Connect Buildprint to Linear to use the AI agent directly from your issue tracker. Mention @Buildprint in any Linear issue to get AI-powered analysis of your Bubble app without leaving Linear. You can also attach Linear issues to Buildprint chat conversations for additional context.

Connecting Linear

Workspace admins can connect Linear from Agent → Integrations.

  1. Click Connect next to Linear.

  2. Authorize Buildprint in the Linear popup.

  3. Your Linear organization name will appear once connected.

To disconnect, use the dropdown menu next to the connected organization name.

Configuring team scope

After connecting, map your Linear teams to Buildprint projects. This tells the agent which Bubble apps to use when responding to issues from each team.

In the Team scope section, select one or more Buildprint projects for each Linear team. When the agent receives a mention on an issue, it resolves the team and uses the mapped projects as context.

If no projects are mapped for a team, the agent will return an error when mentioned on that team's issues.

You are currently not able to scope Linear to particular branches. For this reason, it's recommended to keep the Linear agent in plan mode so it can triage and plan tickets, but not make changes to the application.

Agent settings

Configure how the Linear agent behaves from the Agent settings section on the Integrations page:

  • Run as user — Which workspace admin's credentials and AI provider the agent uses. Must be an admin or owner.

  • Model — The AI model the agent uses (Claude, OpenAI, or Opencode). The selected user must have the relevant provider connected.

  • Reasoning effort — Controls how much the agent thinks before responding: none, low, medium, or high.

  • Task permissions — Whether the agent can make edits to your Bubble app or operates in read-only mode.

Using @Buildprint in Linear

Once connected, you can interact with the agent in two ways:

  • Mention — Tag @Buildprint in a comment on any issue. The agent reads the issue context and responds with analysis or suggestions.

  • Assignment — Assign @Buildprint to an issue. The agent analyzes the full issue (title, description, comments, related issues) and provides a comprehensive response.

The agent has access to the same tools as in Buildprint chat — it can query your database, search logs, explain workflows, and suggest changes. Responses appear directly in the Linear issue as agent activities.

Send follow-up messages to continue the conversation. The agent maintains context from earlier messages in the same session.

Attaching Linear issues to chat

In the Buildprint chat composer, click Add attachment → Link Linear issue to search for and attach a Linear issue. The agent receives the issue's title, description, comments, and related issues as context for your conversation.

Search results are scoped to the Linear teams mapped to your current project. File attachments from the issue (up to 8 files, 10MB each) are also included.

Branch tracking

Buildprint can track Bubble branch progress in Linear using labels.

To use this, add a Linear label that exactly matches the Bubble branch name for the work. For example, if your issue is ACME-103 and the work is happening on the acme-103 Bubble branch, add the acme-103 label to that issue.

Make sure you create any labels yourself - Buildprint is unable to create labels, so if you want issues to be tracked through to test and live, make sure you create test and live Linear labels!

If Auto-sync issue branches is enabled, Buildprint will add the destination branch name as a new Linear label when that branch is merged successfully. Buildprint will also add a comment to the issue saying who merged it and how it was merged. For example:

  • if acme-103 is merged into test, Buildprint adds the test label

  • if test is later deployed or merged into live, Buildprint adds the live label

This gives you a simple view where the labels represent the branches that contain this issues work.

We recommend naming Bubble branches after the Linear issue identifier, for example acme-103. That makes label-based branch tracking work cleanly and keeps issue-to-branch mapping obvious.

If you revert a merge or apply later changes to the merged branch, then Buildprint won't 'remove' the existing branch labels. So, as a best practice, ensure merges are final and create a new branch for updates (you can assign multiple Bubble branches to one Linear issue!)

Buildprint will not track downstream merges (where the merge happens away from Main e.g staging to feature branch or main to staging). This would result in too many notifications and labels!

Branch tracking is not working

Please ensure you've enabled advanced version control in your Bubble app's General settings (near the bottom).

Was this helpful?