How we built Linear Agent
linear.app · 1,668 words · saved by 2 readers
The product and engineering decisions we made so Linear Agent can handle complex tasks without becoming unpredictable.
Most software is designed to behave consistently. Good engineering has typically meant shrinking the space of possible outcomes until the same action reliably produces the same result. AI inverts that logic, at least somewhat. Much of Linear Agent’s value lies in doing work we didn’t anticipate in ways we never explicitly defined; script its behavior too tightly, and we’d dilute the flexibility that makes it useful. So rather than engineering a fixed path for Linear Agent, we defined the boundaries within which it could find its own. We drew those boundaries in the agent’s system prompt,…
saved by
related reading
- Arjun Virkarjunvirk.com
- Linear – The system for product developmentlinear.app
- Best practices for coding with agents · Cursorcursor.com
- Now – Updates from the Linear teamlinear.app
- A calmer interface for a product in motionlinear.app
- What we’ve learned building cloud agents · Cursorcursor.com
- Continually improving our agent harness · Cursorcursor.com
- Why We Built Our Own Background Agentbuilders.ramp.com
- Building Effective AI Agents \ Anthropicanthropic.com
- Building Effective AI Agents \ Anthropicanthropic.com
- Effective context engineering for AI agents \ Anthropicanthropic.com
- How we redesigned the Linear UI (part Ⅱ) - Linearlinear.app