[lukebuehler]

I think these kind of semi-coding agents--but hosted--are the future for enterprises. Claude Tag, Claude Cowork, now Work by OAI.

Agents-on-your-machine clearly have their place, but for many workflows this is too unruly. Hence, the "long-running agent running on shared infra" pattern.

I think this is where the ball is headed. I'm building towards an open source version of this[0]. Still just working on the core, but hopefully soon self-hosted versions can be built on top.

[0] https://github.com/smartcomputer-ai/lightspeed

[ianm218]

I came to the exact same conclusion recently. I am building something like lightspeed that can run on “pay per second” infra like fly.io sprites because I wanted to have an open claw style agent but not have to deal with paying for another VM.

[mtremsal]

Came to a similar decision 5 months ago and ended up building “seven” on Fly’s sprites: https://github.com/1to10partners/seven

Nowadays, depending on the project’s complexity I either run just 1 sprite, several sprites, or in one case 1 permanent “CTO” VM (with a dedicated GH App identity) that specs work that a fleet of worker sprites pull and implement.

[ianm218]

Do you still run your main dev loop through this? Curious

[lagrange77]

> I'm building towards an open source version of this

Interesting. So the main use case would be entities that run lightspeed on a beefy private cloud or on premise?

[lukebuehler]

yes, basically people that want to host powerful, long-running agent runs not on dedicated VMs (although lightspeed can use those too), but on an abstraction layer above.

My thesis is that the right abstraction is durable workflow engines. And AFAIK, OAI also uses Temporal for their complicated hosted agent infra.