AgentGrid

Team this is awesome, congrats on the launch!

The restart-anxiety story is very relatable, that's the actual reason most people give up on managing multiple agents. Curious about the depth of that persistence though - when you reopen the canvas, does it just restore the pane layout and terminal history, or does it actually resume an in-flight agent task that was mid-tool-call when the restart happened?

very nice - our users love it. you’re clearly onto something. agentic coding requires different tools and AgentGrid is it!!

Such a cool idea, congrats on the launch Michael! 💯

Incredible product mate.

Huge fan. I’ve been using it for the last month and a half - completely swapped out my use of an IDE. I went from Cursor, to Zed, now using canvas based Claude code/codex sessions in Agent Grid and really loving it.As a product designer turned design engineer/builder - it’s really working for my spatial memory re: managing the various agent threads I’ve got running across various products. Maybe the best part? You can close it, and all your workspaces and the sessions/nodes are right where you left them. Can’t tell you how much anxiety I had of my IDE crashing and losing all the tabs/terminals I had open. 🤣Excited to see where Michael and Souren take this.

This makes too much sense. Too much work happening for it to just be in a linear thread!

@Michael Yagudaev that "suck having to go back to single terminal session" bit resonates, once you've had parallel context it's hard to go back to one linear thread of thought. @Souren Khetcho the bash-hunt-for-info framing helps too, sounds less like separate agents and more like one team with shared eyes on the same canvas. does the shared context layer show which agent found what, or does it get flattened once it's fed back in?

been waiting for something like this.agentgrid could become the default way to run multiple agents. v excited to see what's next.

Hey Product Hunt! 👋 Michael here, maker of AgentGrid.The true origin: my co-founder Souren built AgentGrid to replicate himself. He was running so many coding agents there was no sane way to manage them all. It took him a MONTH to convince me to use it.What converted me was restart anxiety. Every system update meant losing all my Claude Code sessions. AgentGrid saves your entire workspace: every agent, every session, mapped visually on a 2D canvas. Restart, reopen, everything's exactly where you left it. I haven't lost a session since, and honestly we don't talk about that feature enough.Once I was in, the rest clicked: an infinite canvas where your agents are panes you can watch. You spawn role-based workers (builder, QA, reviewer, devops…), and an orchestrator agent runs the loop: build → review → fix → validate, while you steer and take the final review. Terminals, browsers, code, git and notes live on the same canvas, so "what is my AI doing?" is a glance, not an interrogation.The part I love most: AgentGrid launched itself. The gallery images above, the outreach research, and the first draft of this comment were produced by an orchestrator and its workers running on the canvas. While I slept.Works with Claude Code and Codex today, on macOS, Linux and Windows. It's free during early access: grab it at https://agentgrid.sh. And if you show up today and tell us what to build next, you're a founding user in our book: your feedback goes straight onto the roadmap, and there's a founding-user role waiting in our Discord.I'll be here all day. Tell me what's confusing, what's missing, and what you'd want your agent team to do first. Honest teardowns especially welcome. 🙏