61–70 of 87 posts
Last time I tried to let AI build such extension, it told me that VSCode did not expose extension API to monitor AI chat.
I think when you say “ditch localhost” you’re telling me to ditch my fast, instant-response laptop which I own and can peg the CPU of 24/7 for $0, in favour of a tiny cloud VM that I rent forever.
Your infra to run agents and builds for me is compared in my mind to a shell script an agent wrote a year ago and I reviewed once, that fires up my dev server and a local psql (5-10mb ram) on a dynamically allocated port hashed off the name of my current worktree, which it does so it doesn’t clash with other parallel work.
When the internet slows or dies I rarely notice.
As a cost conscious person who likes it when letters appear as I type, I think I might not be your ICP.
Am I being an asshole? Maybe. Am I going out of my way to tell you what goes on in the minds of people like me when we see offerings like this? Also maybe.
Hello gents, some quick feedback. I think when you say “ditch localhost” you’re telling me to ditch my fast, instant-response laptop which I own and can peg the CPU of 24/7 for $0, in favour of a tiny cloud VM that I rent forever. Your infra to run agents and builds for me is compared in my mind to a shell script an agent wrote a year ago and I reviewed once, that fires up my dev server and a local psql (5-10mb ram)…
It's not me for either currently but that doesn't mean it's not useful.
Although there's a ton of other providers with their own more or less managed/opinionated flavor of agentic sandboxes.
We cataloged a bunch here
https://engine.build/lab/agent-sandboxes
I'll also add boxes.dev to that list.
But yeah overall your tone was asshole flavored lol. Maybe being a bit of a hater too.
Maybe I’m naive but the longest single workflow I ran was maybe 15 minutes. How do you steer agents to run “overnight”? And what is the quality of such execution?
It's meant for the implementation of well defined tasks/specs while orchestrating a review/fix/verify loop.
Every day I have implementations running for hours non stop, it's simply the time it takes to get a proper and well reviewed implementation with LLMs imo.
I might use this if it supported any old cloud or VPS, and was at most $10/mo. The fact that you have decided that this platform should only live in your own custom cloud is unappealing to me. Or, open source it and let us run it on our own VPS and keep your expensive cloud for those who want to pay. As it stands would never consider it.
Thanks a ton for the feedback. Yeah, this is something we'll try to solve in the long term. One of the things that makes this work really smoothly for setup and speed is the ability to have a template box that you can instantly snapshot and fork (disk and RAM) to spin up new machines. There aren't many sandbox providers that do that well for running a full app and development environment, but I'm sure there will be m…
I really like the pricing model and focus on not shafting people by auto-sleeping when an agent is done working. I’ve been working on an [OSS TUI]( https://github.com/prettysmartdev/awman ) for managing agent execution and workflows in containers (local or remotely) and would love to collaborate if you’re interested.
Nice, love the idea of having containers that can work on either local or remote. We may end up reaching out once we start thinking about that. And thanks re: pricing model. It's a start, and we still have a lot of optimizations to go there to make this as cheap as possible, but we think it's a good base to build upon to make agents as efficient as possible compute-wise.
I really like the pricing model and focus on not shafting people by auto-sleeping when an agent is done working. I’ve been working on an [OSS TUI]( https://github.com/prettysmartdev/awman ) for managing agent execution and workflows in containers (local or remotely) and would love to collaborate if you’re interested.
Earlier quoted context omitted.
Nice, love the idea of having containers that can work on either local or remote. We may end up reaching out once we start thinking about that. And thanks re: pricing model. It's a start, and we still have a lot of optimizations to go there to make this as cheap as possible, but we think it's a good base to build upon to make agents as efficient as possible compute-wise.
Please do, interested to add Boxes as a runtime for awman, then workflows could execute in the cloud transparently.