Save Claude, codex, Grok and OpenCode sessions to an infinite canvas

Hi HN, I’m Michael, I built AgentGrid with my friend Souren because we were tired of losing our coding sessions and couldn't keep track of what was actually being built across our

Hi HN, I’m Michael, I built AgentGrid with my friend Souren because we were tired of losing our coding sessions and couldn't keep track of what was actually being built across our many projects. Our approach was to use an infinite canvas desktop app for the TUIs we already know and love, mainly claude + codex. We drew inspiration from Figma and Railway. Overtime we added image nodes, notes, terminals, coding editors, source control, etc. I wasn't sure about it at first. It took me a month

What happened

Read agentgrid.sh's account next to the product docs, not instead of them. Names and figures in the lede are the ones we can stand behind; everything else below is how teams usually absorb a story like this. If a number, ship date, or quote is not in the source excerpt, it is not in this briefing. That is deliberate — day-one coverage is where invented specifics do the most damage.

Hi HN, I’m Michael, I built AgentGrid with my friend Souren because we were tired of losing our coding sessions and couldn't keep track of what was actually being built across our Our approach was to use an infinite canvas desktop app for the TUIs we already know and love, mainly claude + codex.

How it works

Under the hood this is a systems change, not a press-release adjective. Ask what surface area moved — API, policy, hardware, model behavior, or go-to-market — and which of those you actually ship against. A useful working question: if you had to draw the before/after on a whiteboard, which box would you erase? That is the mechanism. Everything else is packaging.

Overtime we added image nodes, notes, terminals, coding editors, source control, etc. It took me a month 5 minutes of high-signal tech — free, weekday mornings.

Why it matters

If you build on or compete with the parties named in Show HN: Save Claude, codex, Grok and OpenCode sessions to an infinite canvas, the practical hit is on roadmap sequencing and risk reviews this quarter, not on a vague 'future of the industry'. Put one owner on the story, give them a day to read the primary material, and decide whether this is a this-sprint item, a this-quarter item, or noise.

Treat this as a briefing, not a replacement for the primary source. If the change touches your stack, verify release notes and rollout status before acting.

Who is affected

Incumbents, customers, and adjacent open-source projects do not feel this equally. Map the change to your own stack: what you operate, what you buy, and what you will have to explain to a security, legal, or finance review. Partners and resellers often feel it before the end user does — check those contracts before you assume nothing moved.

Run your coding agents in one visual workspace.Orchestrate Claude Code, Codex, Cursor, and six more harnesses. Review.Your software factory, visible.Move work through a clear loop: make a plan, delegate implementation, then inspect the diff and decide what happens next.Plan work in a note or master conversationDelegat

What to watch next

Treat the next two weeks as a verification window. Watch the vendor's own changelog, any regulator or standards follow-up, and whether a competitor ships a matching capability. Do not change production on day-one coverage alone. If nothing new is published in that window, the story was smaller than the headline.

Cross-check this section against agentgrid.sh and the official docs before you brief stakeholders on Show HN: Save Claude, codex, Grok and OpenCode sessions to an infinite canvas.

A 3–5 minute news post is a briefing, not a runbook. Keep agentgrid.sh and the vendor's primary page in another tab, quote only what they printed, and write down the single decision this story forces (upgrade, wait, or ignore) before you Slack it to the rest of the team. If you need more than that decision, you want the primary docs or a later engineering deep-dive — not another recap of Show HN: Save Claude, codex, Grok and OpenCode sessions to an infinite canvas.