Ona
@ona_hq
Followers
12K
Following
2K
Media
418
Statuses
2K
Moving beyond the IDE, the mission control for your personal team of autonomous SWE agents.
🌎
Joined July 2018
hello world
Gitpod is now @ona_hq. Same people, different name, bigger ambition. Today, we're launching the mission control for your personal team of autonomous SWE agents.
3
5
21
I'm hiring for senior Go engineers to join us at @ona_hq! If you are: - AI native; using tools like Cursor, Claude code and Ona daily. - Are excited about building AI agents and the mission control platform that they will run on, entirely in Go. - Have 3-5 years of production Go
14
32
190
This is especially true if you overseeing many SWE agents in parallel. As an example, this week I was laying the foundations for a new feature in @ona_hq. Most days I had 3-4 agents running in their separate environment implementing different aspects of the feature.
1
1
0
trying to switch away from cursor for remote ssh, so needed a program to port forward over ssh. i used @ona_hq to build exactly that: kport, a small tui program that lets me do port forwarding over ssh, powered by go and bubblegum. i did not write a single line of code :)
1
2
11
You could say we're moving beyond the IDE
Until now, programming was a "single-threaded" activity. As a dev, I'd get "in the zone" and get it done. AI agents change this: you can now kick off parallel coding tasks. I see more devs do this... and this feels like brand new territory. We'll need to learn. A lot!
0
0
4
This is a @jacksbridger and @ScalingDevTools appreciation post. I have loved the podcast for ages, and is a real privilege to be on it discussing @ona_hq with you and @csweichel. Episode should be released this week I’m told! Can’t wait for you all to hear it.
1
3
17
0
2
8
Watch the full Latent Space episode with the @ona_hq founders and swyx here: https://t.co/1N4uPcx5e9
0
0
1
"It's not dangerous to skip permissions, so you can just remove 'dangerous' because it's not dangerous" - Swyx In this episode of the Latent Space podcast: @csweichel and @jolandgraf cover how agent sandboxing means you can safely run agents like claude code with
1
0
3
Here is how to set up a team of AI agents to work on your project without disrupting anything. This is the top 1 upgrade you can do to your development environment: Start using dev containers to isolate agents and run them in parallel in their own cloud containers. Let me show
14
37
191
Will we ever stop using IDEs? - @swyx Here's what @csweichel had to say about how coding agents are fundamentally re-shaping the UX of developer tools on the @latentspacepod Link for the full episode in the comments
4
1
8
Ona is live on Product Hunt ! Got questions or feedback on Ona? Swing by and let us know 👇
2
0
9
See: https://t.co/1tuD9P77dz for more tips on working with Ona Agents
ona.com
Best practices for using Ona environments, agents, and guardrails effectively in your development workflow.
0
0
0
Sometimes explaining what you want to an agent takes longer than doing it. Now, in Ona you can execute shell commands in any conversation with the ! prefix. Commands execute in isolated environments fully-configured with Dev Container so when you type !npm test it runs against
2
1
2
See our documentation for more: https://t.co/68Q5MwQNhX
ona.com
Use slash commands in Ona Agent to standardize common prompts across your organization
0
0
2
Encode your team's best practices into reusable slash commands that work across your entire organization. Useful for things like: - Automating standards for PRs and commits - Capturing your best reviewer's approach Every command runs in an fully-configured and isolated
2
1
2
See our best practices guide for more tips: https://t.co/lIqPQw9J4G
ona.com
Best practices for using Ona environments, agents, and guardrails effectively in your development workflow.
0
0
0
As agents become autonomous you need a way to monitor progress without watching every detail. That’s why Ona Agents manage from todo lists: - See the plan at a glance - Quickly spot when an agent might need steering - Add, remove, or modify todos mid-task So that you can
1
0
3