We are no longer just traces. Now we support logs + traces. console.logs/prints just get captured alongside traces and shown inline. It's a great way to add random context as your agent runs without creating spans. You can also just send logs from random services :)

Very excited to ship a major overhaul to Loop. It is now capable of running in the background, finding issues in your traces automatically, and sending you useful alerts. Loop is architected as a single agent which has access to a broad set of tools and skills, all exposed through our MCP. The stuff we shipped today are not new features. They are effectively emergent behaviors that solve a bunch of important use cases. This architecture has a number of advantages: * Features compose (eg "find issues on traces that cost more than $5", "create a dataset of compaction issues") * You can chat with anything, eg ask for more details on a pattern it found * You can recreate 100% of Loop's features with your own agent, using our MCP The last bullet is especially important to us. We do not want you to feel like you have to use our agent to access these features. Instead, we want to prove its value by building a great user experience and dealing with orchestration for you. Take it for a spin. We'd love your feedback!