congrats on the launch. curious how you're handling the visually verify the feature looks good part specifically, since that's usually the hardest bit to make reliable compared to the API/CLI checks. are your agents driving a real browser instance for that, or is it screenshot diffing against some baseline been messing around with phi browser lately for a similar problem, it exposes mcp so an agent can drive an actua…
Launch HN: Hoplite (YC S26) – Effortlessly deploy cloud coding agents
71–73 of 73 posts
Re: Launch HN: Hoplite (YC S26) – Effortlessly deploy cloud coding agents
#72At the risk of replicating the classic Dropbox post (why would you need this when you could just use rsync?)… I have a dev box with 96 GB of RAM, 2x4 TB NVMe drives, and an unbelievably beefy AMD CPU. This box costs me less than $150 per month and is so hyperlocal that I can log into it and use it as a remote desktop, while also using it as an always-on server that I can use to run T3 code and tmux and so forth. I ca…
Re: the dev box, it works very well for individuals and small sized teams, but starts to become an operational burden past a certain size. Our ideal customer is one who has a ton of engineers and wants great multiplayer/observability, as the case for Hoplite becomes a lot clearer -- "Run through project setup once, then onboard all engineers with one email (and they can bring their entire local setup with one CLI com…
My take is that some of your architecture decisions are fundamentally incompatible with [what I believe to be the state of] most enterprise codebases.
And that’s fine if you have a very specific client base and are focused on fellow startups.
Re: Launch HN: Hoplite (YC S26) – Effortlessly deploy cloud coding agents
#73I spent a weekend auditing the network calls that three popular open-source coding agents make. Two of them send your file contents to external endpoints by default with zero sandboxing. No confirmation prompt, no allowlist, nothing. If you're running these on anything with proprietary code you're essentially uploading your source to a third party and hoping their privacy policy holds.
OpenCode is the worst offender here — the default config pulls from a remote provider URL and there's no way to even see what's being sent without packet inspection. You can lock it down but it requires manually editing YAML configs that aren't documented anywhere obvious. Aider at least respects .gitignore and keeps everything local unless you explicitly configure a remote endpoint.
The frustrating part is the actual coding capabilities are decent on several of these. Multi-file edits, git integration, context-aware suggestions — all solid. But none of that matters if the tool is silently exfiltrating your code. Audit the network layer before you evaluate anything else.