Karri Saarinen, the CEO of Linear, declared issue tracking dead in March. His argument was reasonable. Issue trackers were built for a world where coordination between humans was the bottleneck, and when agents can interpret context directly, that translation step is friction. It was a clean thesis from a designer who had spent his career making the category better.Then OpenAI open-sourced Symphony, and Linear became the literal control plane for the most ambitious autonomous-coding system ever shipped. Some internal teams saw a 500% increase in landed pull requests. The thing Saarinen had just eulogized was now the substrate that made all of it work.He was right about the user experience and wrong about the infrastructure. The translation step is going away. The state machine, the assignee field, the audit history, the dependency graph, those are staying. They are quietly becoming the most strategic infrastructure in the enterprise software stack, and that repricing extends to every boring tool you own.Here’s what’s inside:The five properties that make a tool agent infrastructure. Why Symphony looks obvious in retrospect, and a diagnostic you can run on every system in your stack.Why your UX choice was actually a data choice. How Linear’s design discipline accidentally produced the cleanest agent substrate on the market, and what that means for tool selection from here.The Atlassian repricing. The MCP server, the Anthropic partnership, the acquisition rumor, and why the market is treating Jira’s installed base as a strategic AI asset.Which of your tools are next. CRMs, ERPs, service desks, calendars, spreadsheets: five yes-or-no questions that tell you which ones become agent infrastructure and which ones get wrapped.What to do about it. Three prompts that score your stack, spec out an MCP server for anything you build, and produce the migration brief your leadership team is missing.It started with a bug tracker in 1998. The accident is the whole story.