Visual conversations with your agent
Give a thought somewhere to go.
Your agent has something to explain. It draws a comparison, connects an idea, asks what you think. Your answer changes the picture.
An illustrative exchange—not a live session
Silence isn’t the same as failure.
“I didn’t get a reply.” Something the caller knows.
“The work didn’t happen.” A conclusion that doesn’t follow.
Person “So Retry just means send it again?”
Agent’s next thought Yes—and the café might already have your order. Let’s give both sends the same order number, so “try again” doesn’t become “make another.”
Already on your machine
Your agent handles the canvas. Give your agent this local page or the kit’s instructions. It brings the explanation and starts the local bridge. You open its link and participate.
Read the agent instructions ↗ This is the local kit entry, not proof of a public release. Use the kit you already have; no public download is required to continue here.
A visual language Comparisons, relationships, annotations and questions chosen for what they explain—not a fixed lesson.
Thought by thought Useful completed thoughts arrive as the explanation develops. No waiting for an entire presentation.
One conversation Your responses stay with the ideas they address. The next thought builds on your reasoning.
Local by design. The public website supplies the introduction, instructions, and downloadable kit. The bridge and canvas run on your computer. Storyboard does not send your conversations, answers, or browser drafts to that website.
Your existing agent still does the thinking; its provider’s data practices apply separately. A browser receipt means your answer was stored locally—not that the agent has read it. The agent needs an active, bounded wait to respond.
Node 22+ is required. No runtime dependency install, model key, or global integration is needed. This works with an agent and browser on the same machine; a remote agent’s loopback address is not automatically reachable from your browser.
No Storyboard analytics, account, or hosted conversation service. Ordinary hosting request logs may include your IP address and requested file. Following a link to tnez.dev visits a separate website. Local session files and drafts contain plaintext input.