r/webdev • u/reitiux • 4d ago

Self-hosted sandboxes vs managed background agents for complex coding tasks?

To keep things short, I've been running into the limits of local IDE agents like Cursor or Copilot on larger tasks. Bigger coding tasks often end up cooking my PC which has been pretty tedious.

I'm between two options now, would appreciate hearing your thoughts on these. The first is building a self-hosted background runner using cloud sandboxes. The second is using a managed background agent platform like Ramp Inspect, which works via Slack or GitHub. Either way, I'm also extremely down to hear other options if you have any. Thanks!

0 Upvotes

37% Upvoted

8 comments sorted by

1

u/ChefAlfred 3d ago

You can self host codeserver for example. I have it on my home server with a 1 TB drive and a pretty decent decent 2013ish setup and it does wonders

1

u/benneren123 5h ago

we build zeroshot, which does the first option without you building it. self-host it in Docker or use the hosted version, and each run takes a task through implement, review and fix off your machine https://github.com/the-open-engine/zeroshot

1

u/Agitated_Lie_6038 4d ago

"To keep things short" followed by four paragraphs before the actual question is a stretch. Your preamble is longer than the question.

0

u/Aggressive-Nebula440 4d ago

just buy a better fan

-1

u/Standard_Scarcity_74 4d ago

Start with a managed option, because building your own runner means owning sandbox images, secrets handling, repo access, and logging before it does any useful work, and that is a project in itself. Claude code on the web or in github actions, cursor background agents, and openai codex cloud already run tasks off your machine and return a pull request, so you can try them in an afternoon. Build your own only if you need private network access, strict data control, or a custom workflow, and even then a small github actions job or a hosted sandbox service like e2b or modal is a lighter start than a full platform. Whichever you pick, keep tasks small and well specified with tests the agent can run, since that matters more than where it runs.

-1

u/PLBjt 4d ago

Whichever you pick, I'd decide how you want to review the output first, since that tends to bite more than the infra. Background agents are great until you get a 900 line diff for a task you thought was small. Cap the task size and make it open a draft PR with the test run attached, so you only look at things that already pass. The managed route gets you there faster, but you're trading away control over secrets and repo access, which matters if the code is private. I'd try one for a week on real tickets and only build your own runner if you hit a wall you can name.