Building the Bucket Linear Agent

Summary

We’re on a mission to enable developers to ship quality features faster. A key part is making the work around building those features frictionless, and one way we’re doing that is by deeply integrating with the tools you use.Recently, we shipped Bucket MCP, so you can flag features directly from your code editor. As well as Bucketbot for GitHub to automatically clean up flags for you. We’d also started work on a Linear integration when they announced their Agents platform. So we jumped at the chance to join their beta.Linear for Agents turns AI into teammates, so you can assign an agent to issues, mention them in comments, and collaborate on projects together. For Bucket, that means we could build an agent to create and manage feature flags for you from within Linear. So we did.The resulting agent can create a feature key on Bucket from a comment on an issue in Linear. And if you want to change who can access that feature, it can do that for you, too. The goal with the Bucket agent was to create an experience that feels native to working in Linear, complementing its workflows and interaction patterns. Here’s how we built it, and the lessons we learned that you can apply when building your own Linear agent.How Linear Agents workAgents are designed to work much like other users in a Linear workspace. You can @-mention them, as well as assign them issues, they can create and reply to comments, and collaborate on projects and documents. Agents can be used for internal use only or used by others in their workspaces via the Linear integrations directory. To create an agent, you make a new Application on Linear like you would for any OAuth app. But in the configuration, make sure to enable webhooks as well as Inbox notifications. This will notify your webhook when events happen relevant to the app's user. The name you set is what folks will use to interact with your agent, so set something that’s short and memorable. We kept it simple: @bucket.Depending on your agent’s fun...