Adrien Griveau

Our philosophy with Linear has been to avoid pushing features too hard. Different companies and teams need different things at different times. The downside is that people sometimes don't know the feature exists and might add new tool for something @linear already could do for them, often with no additional cost. No matter if you're a team or solo builder: + You can keep team docs, project specs, and PRDs in Linear, and have your agent update and maintain them through MCP. Agent context between your agents. Loops can also automate the updating the documents from code, or other sources. + Linear Agent can write code directly from Linear or Slack. Just say “Linear, work on this.” You can connect it to internal tools through MCP, too. It's like Shopify river agent, but you don't have to build it and lot of the usage is included in the pla + Triage, Loops, and Linear cloud coding agent can work as a software factory. A service reports an issue, it lands to team triage, you can set up a Loop automation to investigate, + You can store personal and team skills in Linear. Ask your agent to save a workflow as a skill, then use it again. A Loop can keep those skills up to date across Linear and git. + Project update/Pulse creates one updates feed for your whole company. You can then monitor or get your agent to summarize important things to you + Customer feedback. A database of customer quotes can live in Linear as customer requests, linked to the issues and projects they shaped. + Request intake/forms. Linear Asks takes requests from Slack, emails or web, and turns them into issues. + You can review code in Linear, alongside the issue and the context behind the change.

New on the blog: — Room for ambition A late-night conversation at a startup office in Finland has stayed with me for almost twenty years. Some thoughts on ambition, getting good at something, and the people around you. karrisaarinen.com/posts/room…

Linear is becoming the place to drive more work forward in your orgs. A customer shared this chart showing dramatically faster & automatic bug resolution after enabling Loops + @linear Cloud Coding Agent (claude/codex/open): > Their 95th-percentile time from bug report or customer request to a fix in production dropped from 9 weeks to 3 days over three months. Some use other use cases for Loops: - cleaning up deprecated code - investigating and fixing bugs - routing customer requests to whoever is on call - monitoring security vulnerabilities - checking up on important projects or customer themes