I Watched an AI File a Bug Report, Fix the Code, and Run the Tests. I Didn't Touch the Keyboard.

I want to tell you about a moment that genuinely shifted how I think about software. I gave an AI agent one instruction. One sentence. And then I watched it think. It read my project files. Then it read more files — imports, type definitions, the test suite. It made a plan. It wrote code. It ran the tests. Two of them failed. It read the error messages, understood why they failed, revised the code, and ran the tests again. They passed. It opened a summary of everything it had done. I had typed eleven words. That's not autocomplete. That's not a fancy search engine. That's something that didn't have a good name until recently. We're calling it an agent and understanding what's actually happening under the hood changes how you build with AI entirely. The moment the definition clicked for me Most people encounter AI as a question-answer machine. You ask, it answers, done. One turn. Stateless. Agents are different. They operate in a loop: Observe — read the current state of the world (file