Launching today
Your AI coding agents, visible on one persistent infinite canvas. Spawn role-based workers (builder, QA, reviewer, devops) and an orchestrator runs the build, review, fix, validate loop while you steer. Terminals, browsers, notes and git live beside your agents, so checking on your AI is a glance, not an interrogation. Your whole workspace persists across restarts: every agent, session and pane restored where you left it. Works with Claude Code and Codex, locally. macOS, Linux and Windows.
Free Options
Launch Team / Built With
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. 🙏
PageAI
@michael_yagudaev congrats on the launch, this looks awesome guys!
@dan_mindru thanks so much Dan :). I am legit excited to see how you use it and what you build with it
@michael_yagudaev @dan_mindru Awesome to see you here Dan!!
@michael_yagudaev congrats on the launch. Great product!
@nicklaunches thank you so much Nick ❤️. Can't wait to see what you create :)
Composio
Great launch. A lovely UI. I'm so excited to try this out
What's the maximum number of agents you've seen something running in parallel? Do you have any resources for how we can start maximising our agent usage while not lowering the quality due to the human being the limiter?
@shawn_esquivel great questions :). About 300+ for me, we are improving performance now as TUI is terrible rendering pref. Once we do that next week it should be 1000+. MacOS has a 511 file description limit you can increase too with a quick bash command.
Typically, I let the agent decide how many parallel tasks to do, claude & codex are really good at that.
The challenge is making the review process breezy for you, I typically have agents review each other and leave screenshots. Triage the PRs with low LOC count for quick win merges for human review and get those shipped to real customers.
I'll be creating more resources as we go and will talk to you guys at Composio on itegration ideas :)
the infinite canvas framing for multiple agent terminals is a good fit for how messy multi-agent work actually looks in practice. when two agents on the same canvas need to reference each other's output (one's notes inform the other's next terminal command), is that a manual copy-paste between panes or is there some shared context layer connecting them
@omri_ben_shoham1 AgentGrid exposes tools to agents so they can use such tools to query and feed their context. Think of how agents could use bash to hunt down information. On AgentGrid, they can find the info, connect to it, and truly collaborate
@omri_ben_shoham1 exactly :). Creative process is messy and you need space to think. I literally don't know how to build without AG anymore. Broke it a few times early on and it suck having to go back to single terminal session 🤮
@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?
@Souren @omri_ben_shoham1 Thanks Omri :). It depends what you mean "what agent found what". You can visually see what agents have access to with connections and can search through them.
We are working on better organization and sorting now too to make it easier.
You can ask a single master agent for a status update. It will connect to all other masters and look at where things are. We've been thinking about even an ai-boss agent. Souren has a really cool protoype he can show you :)
Souren here! The co-founder who built this to replicate himself LOL
The honest version: I was running so many coding agents at once that I lost track of what was building what. Terminal tabs everywhere. No idea which agent was stuck, which was done, which was quietly burning tokens on the wrong file. I didn't need a better chatbot, I needed to SEE my team.
So I built the canvas. Agents as panes you can watch. A builder here, a QA there, an orchestrator keeping the loop moving, my terminals and browsers sitting right next to them. And the whole workspace survives restarts, which is the feature that finally converted Michael after a month of me pestering him haha
The wildest part for me: My job was mostly reviewing PRs and saying "ship it".
It's free during early access: https://agentgrid.sh
I want your brutal take. What's confusing, what's missing, and what's the first thing you'd have your agent team build? I'm in the comments all day.
@souren LFG 🚀🚀🚀
honestly the persistence is the part that sold me, having every agent and pane restored where you left it is the kind of detail that makes you actually trust the tool instead of fighting it the next morning.
@kesleralya91117 exactly what sold me too, the fear of restarting my machine with every apple reset. I also love just having the mental reset sometimes and need to clear the deck like that.
Any ideas on how we can make the persistence more front and center on the landing page? That is a big thing we've been hearing from a LOT of early users.
One user even asked to prevent the Mac from restarting on system updates if there are working sessions. Like overnight tasks you leave (will look into this more after launch)
The infinite canvas makes juggling multiple agents feel way less chaotic than switching tabs. Restoration across restarts works exactly as advertised, came back and everything was right where I left it.
@naimej1tx I am so happy that you found AgentGrid useful!
@naimej1tx Thanks so much Naime ❤️. Can't wait to see what you create :). Any weekend project ideas? :)