nowfound

Alternatives

Products that do what Agentspace – long-running YOLO agent sessions in Docker does

Hi HN, I built agentspace because I kept seeing tmux recommended for keeping Claude Code sessions alive over SSH. I find multiplexers painful because they subtly change shell behavior in ways I always forget. They also do not offer a standardized way to run highly permissive agents in a safe way. I also tried worktrees, but it just feels awkward to manage work in that way. Docker can help with all of this, so I thought up a workflow and used some shell aliases to automate spawning Claude/Codex agents into docker containers. I ended up creating a cli to wrap all these methods and would…

  1. 1

    The fastest workflow for developing with AI

    26d ago · agent-manager.dev

  2. 2

    One workspace for Claude, Codex, Gemini and your stack

    May 2026

  3. 3
    Replicas239

    Run Claude Code and Codex in the cloud

    Jun 2026

  4. 4
    Mngr153

    Run 100s of Claude agents in parallel

    Apr 2026

  5. 5

    Your AI agents team, terminals, notes: one infinite canvas

    Jul 2026 · agentgrid.sh

  6. 6
    Boxes.dev112

    Run Claude Code and Codex in your own cloud environment

    Jun 2026

  7. 7
    Vibespace101

    Workspace for multi-agent collaboration

    May 2026

  8. 8
    Orca89

    Your control center for parallel AI agents

    Apr 2026

  9. 9

    Run Claude Code agents in terminal with a visual editor

    Feb 2026

  10. 10AS

    Hi HN, AgentBox is an SDK for running coding agents (Claude Code, Codex, OpenCode) inside sandboxes (Docker, E2B, Modal, Daytona, Vercel). One API. Swap the agent or the sandbox and your code doesn't change. Think of it as what the AI SDK did for LLMs, but for agent + runtime. Most wrappers call agents in non interactive mode (claude --print, codex exec). AgentBox instead boots each agent's native server inside the sandbox (Codex app-server over JSON-RPC, OpenCode serve over HTTP/SSE, Claude Code's SDK WebSocket transport) and drives it from the host, behaving like an interactive…

    Apr 2026 · github.com

  11. 11SR

    Hello all, I'm a software developer. Over the last few months more and more of my work has turned into using coding agents instead of typing the whole code myself. Usually a few claude sessions at once, sometimes codex, one per feature or per revealed bug. I ran them in a split terminal for a few weeks, and quickly spotted two main problems. The first is that I couldn't easily tell which agent was stuck waiting on me and which was still working, so I'd cycle through sessions and checking on them. The second one: agents sharing a single branch step on each other. Two of them could be editing…

    Jul 2026 · shikigami.dev

  12. 12RA

    Hi HN folks, I have been building AI agents for quite some time now. The shift has gone from LLM + Tools → LLM Workflows → Agent + Tools + Memory, and now we are finally seeing true agency emerge: agents as systems composed of tools, command-line access, fine-grained system capabilities, and memory. This way of building agents is powerful, and I believe it is here to stay. But the real question is: are the systems powering these agents ready for that future? I do not think so. Using Docker for a single agent is not going to scale well, because agents need to be lightweight and fast. LLMs…

    Mar 2026 · github.com

  13. 13OA

    I spend a lot of time in Claude Code and Codex with my friend. We kept losing the context behind changes because every agent session lived on one person's laptop, and by the time code made it into a PR, all the reasoning was gone. We tried commits, PRs, and docs, but they only really capture the end result, so we built a tool to keep all of our agent sessions in one searchable place. Now we (and our agents) can check out anyone's session and ask things like "what was Alex working on yesterday?" It's also quite helpful in recovering the context behind a change days or weeks later. Ocean works…

    Aug 2026 · ocean.mosaic.inc

  14. 14CR

    Hey HN, Over the past 10 months I've been using Claude Code heavily, and one limitation kept coming up: you can really only run one coding agent at a time. While one agent is refactoring something, the rest of the repo is basically blocked unless you start manually juggling branches and working directories. The core issue is that AI coding agents operate directly in your filesystem. If two agents run in the same working directory they quickly start stepping on each other’s changes. Git worktrees turned out to be a surprisingly good primitive for solving this. So I built ChatML, a Desktop app…

    Mar 2026 · github.com

  15. 15OD

    Hello HN! I built OpenCodeSpace https://github.com/ngramai/opencodespace — a CLI tool that lets you launch disposable, self-hosted VS Code environments in one command. It’s like a self-hosted Code Spaces, but: - Works locally with Docker or remotely on Fly.io (AWS, GCE coming soon) - Auto-configured with Claude Code, OpenAI, Gemini CLI - Designed for YOLO mode development: temporary, parallel, throwaway sessions As Claude Code and Gemini CLI became core to my dev workflow, I kept needing a way to run them in parallel, in clean, isolated environments in full YOLO mode…

    2025

  16. 16

    A cloud computer for you and your agents

    5d ago · matrix-os.com

  17. 17

    Claude Code, Codex, and OpenCode in one Windows workspace

    6d ago

  18. 18OA

    I've been running Claude Code and Codex together every day. At some point I figured out you can use tmux to let them talk to each other, so I started doing that. Once they could coordinate, I kept adding more agents. Before long I had a whole team working together. But any time I rebooted my machine, the whole thing was gone. Not just the tabs. The way they were wired up, what each one was doing, all of it. Nothing I'd found treats your agent setup as a topology, as something with a shape you can save and bring back. So I built OpenRig, a multi-agent harness. A harness wraps a model. A "rig"…

    Apr 2026 · github.com

  19. 19WC

    A friend and I built this as a side project to help us collaborate on files with our agents. Claude / Codex kept outputting .md and .html files which are great until we needed to share them, so we built this small website to help with that. Agent can either use an HTTP + Skill or an MCP which also uses MCP Apps to add widgets to Claude Desktop / Mobile chat. Would love any feedback and hopefully this helps someone else as it did us!

    Jun 2026 · workplane.co

  20. 20
    Faro3

    The file manager for servers, buckets, and AI agents

    27d ago · github.com

  21. 21IB

    The main goal of this was to be able to not just run multiple Claude Code sessions at once, but actually manage them and keep track of what I was doing. Sometimes this is multiple attempts on the same task, sometimes I work several tasks at once. Really I was just sick of twiddling my thumbs waiting for the coding agent to finish, and I wanted it to be easy to work on/review/test another change while I waited.

    2025 · github.com

  22. 22IV

    Coding agent management is all the rage right now, and many tools are being created to fill the gap. As a power user for all tools I've used since I've started my software engineering career, I've always taken the time to test multiple tools thoroughly before deciding on one, and an agentic manager was no different. I've tested many tools, but ultimately landed on Agent of Empires (AoE for short). Why ? Because it's fast, the development is active and it's feature complete, and easy to contribute to. So I did (contribute). In my day to day workflow for my job, I need the ability to start…

    May 2026 · github.com

  23. 23RC

    Claude Code's --dangerously-skip-permissions flag lets agents run without interruption, but it needs a sandboxed environment to be safe. dangerously is an open source tool that spins up an isolated container and runs Claude Code inside it — file system changes are restricted to your project directory. The new version detects your docker-compose.yml and spins up your full service stack alongside Claude Code, so the agent can test against real dependencies — databases, queues, whatever your app needs. npm install -g dangerously

    Apr 2026 · github.com

  24. 24MA

    This weekend I built a multi-agent coding system which, quite unexpectedly, beat Claude Code on Stanford's Terminal Bench! The architecture is straightforward, consisting of an orchestrator agent that deploys explorer & coder subagents to complete complex terminal based tasks, utilising an intelligent context sharing mechanism along the way which makes it all work. The repo has a lot of technical details, and all the code and prompts for you to play around with if you'd like! I had a lot of fun making this, I hope you have fun reading the README, using it yourself, or even extending it! As…

    2025 · github.com

Ranked by how close each launch is in meaning, then by votes. Refine with a description →