BenceRed

5 ms·

1.
by BenceRed 1mo ago
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,
2.
by BenceRed 1mo ago
We're going to be investing pretty heavily in evals/benchmarks over the next couple of weeks, so that should give us a much better understanding of how our custom harness stacks up to the official ones.
3.
by BenceRed 2mo ago
We use 'phalanx' internally!
4.
by BenceRed 2mo ago
In general, we've found that over the past couple of years agent harnesses have gotten much less restrictive, allowing the agent freedom to choose its own way of doing things. It seems like the project agnostic vs. specific harnesses w
5.
by BenceRed 2mo ago
We've observed this pattern as well, and have counteracted it by keeping the tasks very finely scoped. For example, "The test(api) check has failed. Fix it, then immediately commit and push." -- or -- "The following comm
6.
by BenceRed 2mo ago
I think for use cases like that, we'd offer on-prem deployments (similar to Factory), potentially coupled with a FDE. Still need to do a lot more research into the enterprise space.
7.
by BenceRed 2mo ago
Agreed, we're working with a designer and are going to be fixing this very soon. Our main focus has been on making sure the product itself looks and feels very good to use -- probably not the best approach from a marketing POV.
8.
by BenceRed 2mo ago
Agreed that at the moment it's a very difficult problem, but one we're looking to solve! I think it becomes a no-brainer for most people if we're able to give each agent a replica of their production stack. What does your cur
9.
by 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'v
10.
by BenceRed 2mo ago
exe.dev works quite well for giving an agent a computer and managing it remotely, but seems to require a fair bit more configuration to achieve parity with what we offer out of the box. Namely automations, PR autofix, visual QA, and general
11.
by BenceRed 2mo ago
This is still something we're working on making seamless. The current approach is to install our MCP server and ask the local agent to start up a new thread on Hoplite when you want to transition to the cloud, but it doesn't carry
12.
by BenceRed 2mo ago
That setup is pretty much what we're trying to offer with Hoplite! Using us means losing freedom and control with regards to infrastructure, however we think that's a tradeoff people would want to make in exchange for easier onboa
13.
by BenceRed 2mo ago
Modal just released some features that would allow users to bring custom Docker images, and I'm working on getting your exact use case supported! Aiming to get it out by the end of the week. Noted the pricing feedback! We're still
14.
by BenceRed 2mo ago
This one: https://www.daytona.io . Their platform was OSS for a long time but they decided to go closed source recently.
15.
by BenceRed 2mo ago
You can do either. If you don't want to migrate over fully, I'd recommend setting up an automation to fix Sentry/PostHog issues as they come in. You can get a good feel for the platform and how it fits into your workflows tha
16.
by BenceRed 2mo ago
Modal has a lot of small niceties that made them easy to implement, such as filesystem snapshots and programmatic build images. But I did see that AWS recently launched Lambda MicroVMs, and since we're an AWS house we may transition to
17.
by BenceRed 2mo ago
Agreed. Per-thread VMs are quite similar to how local agents use worktrees to avoid cross contamination, but with the added benefit of being able to easily scale up/down compute requirements on demand.
18.
by BenceRed 2mo ago
Agreed 100%. We've been working with a designer on a complete redesign of our landing page to avoid that vibey-smell.
19.
by BenceRed 2mo ago
At the moment we're using Daytona as a redundant fallback in case Modal experiences an outage, but they have very stringent limits on how many resources we can consume concurrently. We're evaluating adding a second provider to hel
20.
by BenceRed 2mo ago
Thank you! Regarding models, as you said we're not locked into a specific provider, and are able to offer open weight models like Kimi K3 and GLM 5.2 Our pricing is higher than other providers because we do not upcharge on token or san
21.
by BenceRed 2mo ago
Yeah, luckily they're in quite a different domain to us -- hopefully shouldn't have too much trouble winning the SEO battle
22.
Launch HN: Hoplite (YC S26) – Effortlessly deploy cloud coding agents(hoplite.sh)
81 points by BenceRed 2mo ago|70 comments