
1. Create your account
Sign up at app.ona.com. You get free credits to start running agents right away, no setup required.Want to run Ona in your own VPC? Get in touch to set up a self-hosted deployment on AWS or GCP.
2. Optimize your environment
Ona needs a configured environment to run your tests and tools reliably. You can set this up manually, or let Ona do it — it will analyze your repository and generate adevcontainer.json and automations.yaml tailored to your codebase.
Open in Ona →
View the full prompt
View the full prompt
3. Create your first project

4. Start your first environment

5. Talk to Ona
Once your environment is running, you have a session with Ona Agent. Describe what you want to build, fix, or explore and Ona will get to work. Click any of the examples below to open them directly in Ona:Explore a codebase
”Explain the architecture of this codebase”
Open in Ona →
Fix failing tests
”Fix the failing tests in the auth module”
Open in Ona →
Add a feature
”Add a new API endpoint for user preferences, following the patterns in the existing code”
Open in Ona →
Review pull requests
”Review the open pull requests and leave detailed code review comments”
Open in Ona →
Pick up a Linear ticket
”Pick up the next ticket assigned to me in Linear and start working on it”
Open in Ona →
Implement a Jira ticket
”Look at PROJ-142 in Jira and implement what’s described”
Open in Ona →
6. Run agents in the background

10x engineer
Daily, picks your top Linear issue, implements it, runs tests, and opens a draft PR.
Use template →
Scan recent commits for bugs
Scans recent commits for likely bugs and proposes minimal fixes in a draft PR.
Use template →
Sentry error triage and fix
Finds the top unresolved Sentry error, traces it to source, applies a fix, and opens a PR.
Use template →
Draft weekly release notes
Drafts release notes from the week’s merged PRs, grouped by category with summaries.
Use template →
CVE mitigation and dependency updates
Scans for CVEs or outdated dependencies, updates them, runs tests, and opens a PR with the fix.
Use template →
Daily standup generator
Pulls Linear sprint data and git activity to post a formatted daily standup update.
Use template →
Tips
- Be specific. Describe the exact symptom and location, not just “fix the bug.” See be very explicit.
- Plan first. For complex tasks, ask Ona to plan before implementing. See structure your prompts.
- Commit often. Ask Ona to commit working changes as checkpoints. See commit early, commit often.