Turning Agent Autonomy into Productivity with Chris Weichel

A common challenge in software development is creating and maintaining robust development environments. The rise of AI agents has amplified this complexity by adding new demands around permission controls, environment isolation, and resource management. ONA is a platform for AI native software development and engineering agents. The platform combines autonomous agents with secure, standardized environments with a focus on giving enterprises control, security, and productivity so they can scale AI native engineering without scaling risk. Chris Vyckel has more than two decades of experience spanning software engineering and human computer interaction. He is currently the chief technology officer at ONA, formerly Gitpod, where he leads the engineering team behind the company's cloud native development platform. Chris joins the podcast with Kevin Ball to talk about ONA, the impact of coding with parallel agents, the future of IDEs, choosing agent friendly languages, code review as a new bottleneck in the software development life cycle, and much more. Kevin Ball or Kay Ball is the vice president of engineering at Mento and an independent coach for engineers and engineering leaders. He cofounded and served as CTO for two companies, founded the San Diego JavaScript meetup, and organizes the AI in action discussion group through Latent Space. Check out the show notes to follow Kay Ball on Twitter or LinkedIn, or visit his website, kayball.llc. Chris, welcome to the show. Kevin, thank you for having me. Yeah. Excited to dig in. Let's maybe start with you a little bit. So can you give us the TLDR on your background, how you got to where you are today, and a little bit about ONA? Yeah. So my name is Chris. I'm the CTO and cofounder of ONA. And how we got here is I've been writing software basically since I can read. That's a very long time, and I've been doing that professionally for more than twenty five years at this point. And throughout my entire career, I've been in essentially dev tools and tooling space, a lot in automotive, large enterprises, at some point did a PhD in human computer interaction on tooling for, digital fabrication as it so was. And ONA, really, at this point is the culmination of all these years and, like, trying to solve a problem that I've seen show up repeatedly. And with AI, we got a whole set of tools to help solve things that we couldn't even have dreamed of just a few years ago. So let's talk a little bit about that problem set. So what is the core problem driving Ono? What are you solving for folks? Very fundamentally, it is reducing the time between having an idea and making it reality. I mean, that's the job of any good tool. But where we started, where we came from is essentially ONA environments. And it's the idea that if you wanna write software, certainly in a professional context, you'll be spending a lot of time setting up a deaf environment. So instead of writing …