we've run into this problem. when you're running 4-5 Codex/Claude Code sessions in parallel across worktrees, the port collision sucks. have to check out
Show HN: Coasts – Containerized Hosts for Agents
51–54 of 54 posts
Re: Show HN: Coasts – Containerized Hosts for Agents
#52This solves the parallel runtime problem well. The adjacent problem I’ve been focused on is what happens after the agent finishes in its isolated environment: how do you review what it actually changed before accepting the result? I’m interested in diff/commit/rollback at the filesystem level, so you can selectively keep some changes and discard others. Different problem, but they compose naturally.
I’m sorry I didn’t reply sooner. I’d love to hear about the diff/commit/rollback stuff you’re working on. Feel free to message me on discord or however you like (I’m pretty easy to find).
I wanna hear how they compose naturally.
Re: Show HN: Coasts – Containerized Hosts for Agents
#53[flagged]
Re: Show HN: Coasts – Containerized Hosts for Agents
#54What is the memory footprint? If running on a mac how does it do in terms of being able to run other things concurrently?