我如何构建了一个调试工具，并且使用这个工具的代理发现了其中的错误。
这个故事可能永远不会发生，尽管我已经酝酿了很久一个调试器的想法。没有任何触发因素。但有一天，一个足够强大的触发因素出现了，我决定放下其他项目，专心构建调试器，以便不再经历这样的痛苦。
一点背景故事：我正在为人工智能解决方案开发者构建一个平台，让任何人都可以在一个舒适的环境中开展自己的创业项目。为了实现这一目标，还有很多工作要做。
我应该提到，我整个项目的构建原则是使用自主编码。不是“随意编码”——那是那些刚刚嗅到“可能性”的业余者的做法——而是真正的自主编码，具有明确结构化的工作流程，代理在我设定的规则和构建的边界内别无选择。原则上，我没有手动编写这个项目的任何一行代码。
于是，我在进行日常工作，修复Prompt Studio工具中的错误。我甚至现在都不记得那个错误到底是什么——它顽固地抵抗着我和我的Opus的共同努力。但这件事拖得太久了，以至于我感到的不仅仅是疲惫，还有愤怒。就在那时，我意识到：如果我不是在进行这种无效的挣扎，而是早早构建了那个调试器，我现在就能解决这个错误。但我还是继续坚持，直到我赢了。
不用说，我的项目被搁置，我开始构建调试器。由于这个想法已经酝酿了很久，第一个Python原型——六个模块——很快就被构建成了平台的内置调试子系统。接下来是测试它的时刻。我告诉代理：“使用Revizor自检。”在接下来的三分半钟里，发生了以下事情：
代理启动了Revizor，激活了其中的所有跟踪点，发现了几个错误（4或5个，我不太记得了），修复了它们，并使用Revizor自己的工具运行了199个测试——全部通过！我惊呆了，无法用语言形容。
就在那时，我明白了：平台的第一个产品不应该是Prompt Studio，而应该是Revizor。我用Go重写了它，并开始使用这个二进制文件，淘汰了作为原型的旧子系统。
随着时间的推移，Revizor获得了扩展其功能的工具。现在，在代理的指导下，它可以检查代码中的跟踪点，添加或移除它们——这一切都在瞬间完成。代理们形容使用Revizor就像是“X光视力”。以下是其中一个真实的评论：
Revizor今天节省了多少时间？
● 大约15-20分钟。trace_search“提升”在2秒内显示了5个跟踪点的完整链，确认提升工作正常——如果没有它，我需要翻阅代码和日志，添加临时的print()语句，重启服务器。但真正的价值不在于节省的分钟数，而在于确定性：我不是在猜测它是否有效。我看到了。
不要相信代理：它总是夸大任何任务所需的时间。但它所说的有价值之处在于——“我不是在猜测，我看到了。”如果我在与导致我构建这个调试器的错误斗争时就拥有了这个调试器，调试工作将会快得多。
现在我无法想象没有它的工作。我邀请你免费试用：有一个免费的社区版，无限制的14天试用期，以及——最重要的，对于我所有产品始终适用——周日无限制，专为那些在周末进行激情项目或开源工作的人设计。
使用任何主要提供商（目前有六个选项）登录以下载它。
关于安全性：平台不收集或存储任何个人数据——仅仅是你的内部ID和你认证提供商的哈希，以便下次识别你。Revizor本身不会从你的机器发送任何信息，除了每日许可证检查的ping和周日无限制的时间同步。企业许可证则完全保持沉默。
试试Revizor：https://ais-platform.dev/revizor
查看原文
This story might never have happened, even though I'd been carrying the idea for a debugger for a long time. There was no trigger. But one day a trigger appeared that was strong enough that I set the project aside to build the debugger and never suffer like that again.<p>A bit of backstory: I'm building a Platform for AI-solution developers, so anyone can come in and work on their own startups in a comfortable environment. There's a lot of work ahead to make that happen.<p>I should mention that I'm building this entire project on principle using agentic coding. Not "vibe-coding" - that's for amateurs who've caught a whiff of "possibilities" - but genuine agentic coding, with a clearly structured workflow where the agent has no choice but to play by the rules I've set, within the boundaries I've built. On principle, I haven't written a single line of this project by hand.<p>So there I was, doing routine work, fixing bugs in the Prompt Studio tool. I don't even remember now what exactly that bug was - it stubbornly resisted the combined efforts of me and my Opus. But it dragged on so long that I was feeling anger by that point, not just fatigue. And that's when it hit me: if instead of this unproductive slog I'd just gone and built that debugger already, I'd have beaten this bug by now. But I kept going, and kept going, until I won.<p>Needless to say, my project got pushed aside and I started building the debugger. Since the idea had been maturing for a long time, the first Python prototype - six modules - was soon built into the Platform as a built-in debugging subsystem. Then came the time to test it in action. I told the agent: "Use Revizor to check itself." Over the next three and a half minutes, this happened:<p>The agent launched Revizor, activated all the trace points in it, found several bugs (4 or 5, I don't remember exactly), fixed them, and used Revizor's own tools to run 199 tests - all green! I was so stunned I can't describe it.<p>That's when I understood: the Platform's first product shouldn't be Prompt Studio - it should be Revizor. I rewrote it in Go and started using the binary, retiring the old subsystem that had served as the prototype.<p>Over time, Revizor gained tools that expanded what it could do. Now, under the agent's direction, it can check code for trace points, add them or remove them - all in a fraction of a second. Agents describe using Revizor as "X-ray vision." Here's a real comment from one:<p>How much time did Revizor save today?<p>● Roughly 15-20 minutes. trace_search "elevation" showed the full chain of 5 trace points in 2 seconds, confirming elevation works correctly - without it, I'd have needed to dig through code and logs, add temporary print() statements, restart the server. But the real value isn't the minutes - it's the certainty: I wasn't guessing whether it worked. I saw it.<p>Don't trust the agent: it always exaggerates how much time any task supposedly took. But there's value in what it said - "I wasn't guessing - I saw it." If I'd already had this debugger back when I was wrestling with the bug that led me to build it, the debugging would have finished many times faster.<p>Now I can't imagine my work without it. I invite you to try it for free: there's a free Community tier, an unlimited 14-day trial, and - most important, and always true for all my products - Sunday Unlimited, made for people working on weekend passion projects or open-source work.<p>Sign in with any major provider (six options so far) to download it.<p>On security: the Platform doesn't collect or store any personal data - only your internal ID and a hash of your auth provider, to recognize you next time. Revizor itself sends nothing from your machine except a daily license-check ping and a time sync for Sunday Unlimited. Enterprise licenses give complete silence.<p>Try Revizor: https://ais-platform.dev/revizor