Agentic Coding with Discipline and Skill
I’ve been practicing the art and science of agentic coding for about two years now. That might sound silly because “agentic coding” is a relatively recent term. True, I wasn’t using this particular phrase back then, but I was using an AI coding agent.
It was an open source agent I built myself called Kaguya. I built it as a ChatGPT plugin that gave it access to my local drive, allowing it to write files, read files, edit files, and run code—Bash, Python, JavaScript—on its own.
Back then, it was a strange idea. When I first spoke about it publicly, people thought it was really funny that I gave AI so much access to my local drive. But I did it through a container, so it was pretty secure.
Since then, I’ve joined Sourcegraph and have been working on different agentic coding experiences. I was the one who introduced the concept of agentic coding to Cody, an AI coding assistant.
I’ve used agentic coding extensively for all of these projects. For example, I built much of Kaguya using Kaguya itself. I’ve made hundreds of commits and read and written thousands of lines of code at least, and so I feel like I’m qualified to speak on this topic.
