Ona best practices

Sustained over ten weeks, Ona has more than doubled our team’s throughput (PRs merged per week, p < 0.001). As mission control for software engineering agents, Ona is designed to bring more productivity, convenience, parallelism, and security to software engineers.

Ona Agents are purpose-built to utilize the security guarantees and isolation, as well as human-agent interaction, afforded by Ona Environments. This produces a power-tool for individuals and enterprise-level organizations alike; handling real-world requirements towards tooling, compliance and process.

This document describes how we at Ona use Ona. For weeks Ona’s contributed 75% of our code changes (SLOC changed). Consider this a “best practice guide”, rather than a handbook one must follow. Start with these tips and make them your own; experiment and find out what works for you.

Acknowledgments

This collection of best practices is the work of many. It is months of joint practice, experience, reports, and mistakes. I'm grateful to all the engineers at Ona, our design partners, better users, and customers who have so generously shared their experience with us.

Thank you Matthew Boyle for contributing directly to this post.