The Termi Protocol is a 3D simulation of AI agent workflows. Give your coding agents a face, a desk and a living room. Watch them read, write and run commands live in 3D, like a game. You run the agents; we visualize the process.
Hi Product Hunt 👋
I built The Termi Protocol because I run coding agents all day, and staring at scrolling terminal logs never really showed me what they were actually doing.
So I gave them a body.
Termi is a 3D room where your real CLI agents like Claude Code, Codex, Gemini, and five more live and work. You can watch each one walk to its desk, read files, write code, and run commands as a little robot in real time.
It is not a chat app. It is not an IDE. You keep using the agents you already use. Termi simply turns the whole process into something you can see, steer, and control.
A few things I am proud of:
Claude and Codex can work on the same repo. File locks keep them from colliding, and an idle agent can pick up a peer’s work.
Checkpoints let you rewind any step, almost like time travel for your code.
On-device memory remembers what each agent did and why. It is fully searchable and does not need an API key.
Nothing risky happens without your one-tap approval.
And yes, there is a pet that grows with your coding days.
Termi runs on macOS and Windows. It is local-first, pay once, and yours for life. Founding backers get it for $6.99.
I would love your honest feedback, especially on the watch-it-work experience.
Happy to answer anything in the comments. 🙏
The state I can never eyeball fast in scrolling logs is idle-waiting-on-approval versus stuck-in-a-retry-loop. They throw off similar output volume but mean opposite things, and I usually notice the difference three minutes too late. If the room made those two visually distinct at a glance, an agent standing still at the desk versus pacing and redoing, that's the thing that would earn the screen space over an 8 hour session for me. Does the body reflect that an agent is actually blocked, or just that it's between commands?
Everyone is asking how the room shows agent state - the state I care most about is mine. Running several agents, the biggest silent time sink is agents sitting blocked on my approval while I look somewhere else. The room shows their work; the killer view would be my inbox: one glance at everything currently waiting on me, oldest first. Is there anything like that today, or is approval surfaced per agent only? Congrats on the launch!
Love that you went with a 3D live view instead of just streaming logs or a diff feed. Watching an agent actually "build" in space is such a fun way to make something abstract feel tangible, way easier to stay engaged than staring at a terminal.
the question that decides whether this is a toy or a tool: how tightly is the 3d scene wired to real telemetry? like the agent walks to the desk on a file write and stands at the whiteboard while planning? and can i act from inside the scene, click the agent that has been pacing in circles for ten minutes and see its last three tool calls? if watching becomes steering, this goes from cute to genuinely useful for multi agent runs.
The watch-it-work idea is strongest when the room has a hard mapping to operational state, not just animation. For coding agents I would want every visible action to answer one of four questions: what file/process is currently owned, what decision is waiting for approval, what checkpoint can I roll back to, and what changed since the last human review.
A useful test case would be two agents touching adjacent files during a refactor. If the 3D room can show lock ownership, blocked/waiting state, command output risk, and the exact diff/checkpoint boundary without opening a terminal first, then it becomes a control surface. If I still need to read the raw logs to know whether to pause or approve, the room is mostly a pleasant monitor.
Eric, I'm the exact target here, a solo dev running Claude Code all day, so "logs never showed me what they were actually doing" hits home :)
Honest question: does the 3D actually change how you steer the agents, or is it delight on top? For one agent, watching a robot walk to its desk risks becoming visual noise after 8 hours. Where it'd be indispensable is the multi-agent case, does the room really encode state (this one holds a lock, this one's blocked) so you see a collision before it lands? That's the line between the product and a beautiful skin.
Congrats on the launch! ;)
The visualization angle is interesting if it helps debug handoffs, not just make agents look fun. I'd be curious whether command/log events can be replayed later, because that would make it much more useful for reviewing failed runs.
Hello Eric. Congrats on the launch, very fun idea! How exactly can I control the agents if I just see them in 3D? These checkpoints are saved in local cache or inside the Termi server? Thanks let's connect :)!
Exactly the answer I was hoping for — attaching to running sessions and keeping the render local is what makes it usable day to day. On the attach mechanism: does Termi tap the session by reading the PTY/terminal output, or hook into the agent process directly? And if I have two or three agents going at once (say Claude Code plus Codex), do they share one room or spawn separate ones?
Congrats on the launch. The local-first angle is the part I’d trust most here. For AI coding agents, visibility is useful only if it helps me make a decision: pause, approve, rewind, or compare what two agents changed.
One small suggestion: make the “why this step happened” trail as important as the 3D view. Commands run, files touched, checkpoint reason, and approval history would turn this from a fun visualization into a review tool I could actually rely on.
The idea is really fun! Now I wonder - how deep it is connected with real activity of agents. Will it help to get visual signal that something is going wrong and can user control agents through those 3D models, or they are working only one side, just visualising the process?
That's interesting. Does it work with any agent that exposes terminal output, or only specific ones?
Giving agents a desk and a living room is delightfully absurd and weirdly useful at the same time - watching the process beats reading a wall of logs for spotting when an agent gets stuck in a loop. I live in Claude Code all day, so yes, I want to see my agent pacing around its office. Congrats on the launch!
Congrats with a launch!
So we're not all confused here, it's just a fun project, you are not suggesting it as a serious workflow, right?
watching agents work in 3d is genuinely fun. i stared at agent logs for years and they never showed intent. does the view hint at why, not just what?
Very creative. I'm curious does visualizing the workflow actually help you catch bugs or inefficiencies that you'd normally miss in terminal logs?
the living room touch is genuinely clever, makes coding sessions feel less sterile than the usual terminal wall. nice execution on making agent work feel like something you'd actually want to watch.
Giving CLI agents a literal body in a 3D room is a clever way to make what Claude Code / Codex are actually doing legible instead of scrolling terminal logs. The practical thing I'd want to know: does Termi attach to my existing agent sessions (reading the terminal/process I already have running), or does it need to launch and wrap the agents itself? And does the visualization run fully local, or does it stream my file/command activity to a hosted backend to render the room?
About Termi Protocol on Product Hunt
“Watch your AI coding agents build, live in 3D”
Termi Protocol launched on Product Hunt on July 4th, 2026 and earned 186 upvotes and 40 comments, placing #5 on the daily leaderboard. The Termi Protocol is a 3D simulation of AI agent workflows. Give your coding agents a face, a desk and a living room. Watch them read, write and run commands live in 3D, like a game. You run the agents; we visualize the process.
Termi Protocol was featured in Productivity (656.2k followers), Artificial Intelligence (473.7k followers) and Games (98.7k followers) on Product Hunt. Together, these topics include over 279.5k products, making this a competitive space to launch in.
Who hunted Termi Protocol?
Termi Protocol was hunted by Eric Omer Ercan. A “hunter” on Product Hunt is the community member who submits a product to the platform — uploading the images, the link, and tagging the makers behind it. Hunters typically write the first comment explaining why a product is worth attention, and their followers are notified the moment they post. Around 79% of featured launches on Product Hunt are self-hunted by their makers, but a well-known hunter still acts as a signal of quality to the rest of the community. See the full all-time top hunters leaderboard to discover who is shaping the Product Hunt ecosystem.
Want to see how Termi Protocol stacked up against nearby launches in real time? Check out the live launch dashboard for upvote speed charts, proximity comparisons, and more analytics.
Eric Omer Ercan