ripped_britches

Self hosted definitely does not need to mean you use your own hardware

If I operate forgejo on a hetzner instance I a self hosting my own forge despite it not being my hardware

Whoever the author of this repo is - they have made the personal agent runtime so that it can be self hosted. The runtime itself is the thing that you can self host.

No defense contractor CEO in history has ever built a company this large, this fast. I don't think anyone is even thinking about firing Dario.

Cool! Would love any feedback. Feel free to put up an issue on the repo.

lol I was going to say this too! I think the inverse is true: nobody wants to install a PWA

I’m all-in on agents but this is a “you’re holding it wrong” situation.

If you want to give your agents a DB for their own work as a scratchpad or something that’s great. They can not only go to town, but also analyze their own work and iterate on it.

If you are talking about a production base, agents should not be hitting it directly under any circumstances. There needs to be an API layer with defined usage patterns, rate limits, etc.

This is basically the same as saying “databases weren’t designed for interns to run live inline migrations in prod”. Yeah of course they aren’t.

At this point we should make a GitHub repo with a huge list of unsolved “dry lab” problems and spin up a harness to try and solve them all every new release.

I mean better that than false negative right? It’s obviously an unsolved problem.

This is the break right now, we will smile back on these times

Mockups for what type of work? Web or mobile UI?

How does the inference work correctly if the payloads are encrypted?