Launching today
Termi Protocol
Watch your AI coding agents build, live in 3D
159 followers
Watch your AI coding agents build, live in 3D
159 followers
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
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.
Termi Protocol
@grace_lee26
Thank you for the valuable feedback, I really appreciate it.
I completely agree with your point. The 3D view is only the first layer, but the real value comes when visibility helps the user make better decisions.
Commands run, files touched, checkpoint reasons, approval history, pause, rewind, and comparing agents are exactly the kind of things we want to make stronger as Termi evolves.
Really appreciate you taking the time to share this. It helps us shape the product in the right direction.
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?
@noctis06 you actually think it's a practical way of checking if your agent is doing legible work or not, or you just kidding?
Termi Protocol
@noctis06 Thank you for the valuable feedback and thoughtful question.
Termi connects to your existing agent sessions. You do not need to restart them or go through an extra wrapping process. It basically attaches to the sessions you already have running and gives them a body inside the 3D room.
The visualization also runs fully local. Your file activity, command activity, and agent workflow are not sent to a hosted backend for rendering.
Termi Protocol
@thys_beesman
Thank you, I really appreciate that.
Yes, that is one of the main reasons I built it. Agents often work with a kind of hive-mind psychology, especially when multiple sessions are active at the same time. In a normal terminal, it is easy to miss when one of them gets stuck, repeats the same action, or runs into an error.
In Termi, the visual layer helps make those moments obvious. For example, if an agent hits a possible error, a red warning appears above its head and the robot starts shaking, so you can immediately notice that something needs attention.
On the technical side, it also notifies you when an error happens. You can then check the history section to see where it happened, what caused it, and decide how to intervene.
So the goal is not to replace terminal logs, but to make problems easier to catch and supervise before they disappear inside a long wall of text.
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?
Termi Protocol
@andrewzakonov
Exactly, that is the idea.
When a project grows, managing agents through terminal logs becomes harder. With Termi, I wanted to make the process more fun, but also make real problems easier to see.
For example, if an agent hits a bug or has an issue with the file it is running, the robot can shake, make a small alert sound, and show a red warning above its head. Then the issue is added to the history section, where you can see what happened and why.
So the goal is not only to show what the agent is doing, but to make its state and problems easier to understand.
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?
Termi Protocol
@julia_shtogren
Thank you Julia, great question.
Right now, Termi is connected to real agent activity and visualizes things like reading files, writing code, running commands, and permission states.
It is not just decorative. When something goes wrong, the user gets a negative sound alert, a red warning appears above the agent, and the agent shakes. Then the history section explains what happened and why.
At this stage, the 3D layer is mainly for visibility and awareness, but our goal is to turn it step by step into a stronger control layer where users can better pause, review, compare, and guide their agents.
the little office setup is weirdly charming, watching my agent pace around the room while it ran tests actually made debugging feel less painful. would love a way to peek at the full command output without losing the 3d view though
Termi Protocol
@blahgeputc93775
Thank you for the great feedback, I really appreciate it.
And yes, that exact feature is already in Termi. The Command Center on the right side is built for this. You can keep the 3D project scene in the center, while checking the full command output and agent details without leaving the room view.
The bottom section also lets you inspect your other Termis and follow what each one is doing. I tried to design it so the visual layer stays fun, but the technical details are always one step away when you need them.