Show HN: Omnara – Open-source alternative to Claude Managed Agents

My setup is Hermes on a beefy machine with running a swarm of pi.devs - connects to GH issues via bot app so I can call it @xxxx in the issue. It can create PR, run actions and all. If I want to see the code I just run kilo code in VS locally.

This setup is so plain and simple that it just works, and it works wonders. I feel like I’ve been running a dev team who actually communicates through issuess and keeps it up to date!

with a great related talk! https://ai.engineer/talks/UPwGaM2MKHY-log-is-agent

feels like everyone is converging on durable agents lately: pi durable, cloudflare agents on durable objects, vercel's durable harness

The two concepts of Durable Agents and Distributed Tools pair really well together.

- At work, I don't want to run agents on our overworked and unstable on-prem infra, but there is data we need to access there, so I build agents in the cloud and have on-prem services that listen for work.

- At home, I want to access my agents from the internet, but I don't want to punch holes in my network, so I build agents in the cloud and have at-home services that listen for work.

Of course, it's a bit slower than a single process with local tools, but it can still be a very productive user experience.

And then I think... we're not really inventing something new with Durable Agents and Distributed Tools, we're just moving closer to the event driven architectures that we already know. I can build a durable agent with Lambda Durable Functions and waitForCallback or Lambda Step Functions and waitForTaskToken. Or any pool of compute with a queue or two and persistent state.

So I guess my thought is... you don't need to learn a harness to build an agent. Use what you know. If a harness helps you conceptualize, use it.

I've built sth similar that acts as a mobile interface to your desktop setup via the multiplexer of your choice (herdr/tmux/zellij). https://github.com/AltanS/collie

There's also a typescript SDK to connect a durable agent/harness to the app, still experimental though.

been following you guys from distance over x. congrats on the launch! excited to see where this goes

Congratulations on the launch - looks interesting, and matches some thoughts I've had regarding herding LLMs in a sensible and secure manner.

What's the product? Can I buy anything right now?

A detailed I noted on permissions - looks like they're all prefixed with "always" - I think allow/deny/ask make more sense ?

Can you shed some light on orchestration? I don't want to babysit them. Do you have a concept of roles and hierarchies, like team lead, tester, engineer, etc?