5 ms·

Makes sense. It took me some experimentations with a few open source libraries and docker-compose to arrive at my setup. My setup also requires me to access age

Makes sense. It took me some experimentations with a few open source libraries and docker-compose to arrive at my setup. My setup also requires me to access agents via a terminal app on my phone so it's nice to have a web app like your offering. Are you offering browser access to the agents in your setup?

BenceRed 2mo ago
Yes, agents have a persistent Chromium session they use via the agent-browser CLI. Typical workflow would involve starting the preview, seeding data, then the agent going through the old and new UX flows for a before + after view. We've also got some optimisations around saving the aforementioned flows in a QA library, so that they can be replayed without needing an agent to run through it all again.
greatsage_sh 1mo ago
If browser access is the actual blocker: OpenCode (open-source coding agent, github.com/anomalyco/opencode) ships its own web UI -- `opencode serve` gets you a browser tab into the agent without needing Hoplite's hosted layer at all, so it slots into a self-hosted docker-compose setup like yours instead of replacing it. I got tired of re-doing that setup on every new box, so I packaged it as a one-click Railway template -- a cloud dev box that runs OpenCode's web UI with state persisting between sessions, so you can drive it from your phone's browser instead of a terminal app. Full disclosure: I maintain it and get a kickback if you deploy through it: https://railway.com/deploy/opencode-webui-workspace?referralCode=Z1xivh&utm_medium=integration&utm_source=template&utm_campaign=generic https://railway.com/deploy/opencode-webui-workspace?referral... It doesn't give you Hoplite's per-thread VMs, PR automation, or QA tooling -- it's just the agent plus a browser, self-hosted. But if that's literally the missing 20%, it's a much smaller lift than what you already built.
- scottydelta 1mo ago
  And why would I go from my self hosted infra on a dedicated server to a dependency on Railway? My setup already works and what you are suggesting is weaker than my setup.

BenceRed 2mo ago

Yes, agents have a persistent Chromium session they use via the agent-browser CLI. Typical workflow would involve starting the preview, seeding data, then the agent going through the old and new UX flows for a before + after view. We've also got some optimisations around saving the aforementioned flows in a QA library, so that they can be replayed without needing an agent to run through it all again.

greatsage_sh 1mo ago

If browser access is the actual blocker: OpenCode (open-source coding agent, github.com/anomalyco/opencode) ships its own web UI -- `opencode serve` gets you a browser tab into the agent without needing Hoplite's hosted layer at all, so it slots into a self-hosted docker-compose setup like yours instead of replacing it. I got tired of re-doing that setup on every new box, so I packaged it as a one-click Railway template -- a cloud dev box that runs OpenCode's web UI with state persisting between sessions, so you can drive it from your phone's browser instead of a terminal app. Full disclosure: I maintain it and get a kickback if you deploy through it: https://railway.com/deploy/opencode-webui-workspace?referralCode=Z1xivh&utm_medium=integration&utm_source=template&utm_campaign=generic https://railway.com/deploy/opencode-webui-workspace?referral... It doesn't give you Hoplite's per-thread VMs, PR automation, or QA tooling -- it's just the agent plus a browser, self-hosted. But if that's literally the missing 20%, it's a much smaller lift than what you already built.

scottydelta 1mo ago
And why would I go from my self hosted infra on a dedicated server to a dependency on Railway? My setup already works and what you are suggesting is weaker than my setup.