Whiteboard in vix AI coding agent

Added: 2026-05-19

[00:00:01]Hey everyone, let me introduce you to Vix, an AI coding agent. And for today's video, I want to show you its whitebot capabilities.

[00:00:10]You see, in Vix, you have two elements.

[00:00:12]You have a TUI, that's what you see right now on your screen, and you have a demon that's running in the background.

[00:00:19]The demon is running all the harness, the tools, the communication with the server. And in addition to all of this, it's also running a web server. Here you have the homepage of the web server with some server metrics and the list of con connected session. And for each of these sessions, you can start a whiteboard. So in that case, I can add a different element for example an API that will talk to a service.

[00:00:52]Uh you can actually change the colors that will talk to a database. Let's link them together and then you can just start a discussion with Vix.

[00:01:04]>> Hello, I'm Vix, your AI coding assistant, and I'm here to answer any questions you have about your codebase.

[00:01:10]How can I help you today?

[00:01:12]>> Hey Vix, can you tell me about what you see on the whiteboard?

[00:01:19]>> Sure. On the whiteboard, there's a simple three-part architecture diagram.

[00:01:24]On the left, there's a blue API rectangle, which connects to a red service box in the middle, and that in turn connects to a green database cylinder on the right. It looks like a generic request flow, an API forwarding calls to a service that reads and writes to a database. Want me to tie it to something specific in your project?

[00:01:44]>> Yeah, I want to use this architecture for a website. Uh the website I'm expecting around 10,000 visitor per months. Uh can you give me some feedback around that?

[00:01:56]For 10,000 visitors a month, that's roughly a few hundred a day, which is very modest traffic. This three tier setup is honestly more than enough. You could even run all three components on a single small server and be fine. the main >> I'll stop the conversation here because I think you understand uh the gist of it. Uh but basically because this whiteboard is run on the demon it has access to your codebase and you can actually ask question about it. You can literally talk to your codebase. So let's see uh what we can do with it.

[00:02:38]Hello, I'm Vix, your AI coding assistant, and I'm here to answer any questions you have about your codebase.

[00:02:45]How can I help you today?

[00:02:47]>> Hey, Vicks. Uh, can you tell me about how the communication between the TUI and the demand is working? Update the whiteboard with your findings afterwards.

[00:03:03]Sure. Let me dig into how the TUI talks to the Damon.

[00:03:15]So now what's happening is that the whiteboard is asking the demon to do the exploration phase. You will read different files, map them together, try to understand the structure and then it will send back this information to the whiteboard that will put everything in shape and will draw the different element. So now we will wait for it to uh finalize the whole thing.

[00:03:46]Okay, I've explored the codebase and have a clear understanding of how the TUI and Damon communicate. The communication primarily happens over a Unix domain socket using new line delimited JSON for all messages. There are two main modes, a oneshot RPC for stateless queries and a persistent birectional session for interactive agent sessions. I'll update the whiteboard with a diagram and some key code snippets to illustrate this.

[00:04:17]Right? So as you can see uh basically VIX explore the codebase understood what was happening draw the result on the whiteboard. It's uh in that case that's pretty simple. I wanted to keep things simple so uh everyone can understand and it also added uh the relevant code of like how things are happening right and then you can literally continue the conversation right like you can ask follow-up questions and dig into subject if you want now I want to show you uh one last thing is that in VIX we have uh different mode right so we have the chat mode but we also have the plan mode just like in different um other AI coding agent. I won't go too deep here but uh in VIX you can actually modify and tweak these workflows. So for example instead of having uh exploration plan and implementation you can add a step in the middle that would review the plan automatically like with a a model. Um what you could do also because you have this flexibility you can add another step to generate a whiteboard. So in that case uh let's say that I want to add a slash command to u get the session ID right so now what will be happening is that it's a pretty regular workflow plan uh where you will explore to understand like how to do uh the the implementation that I'm requesting and then you will come up with a plan And then when I will review the plan, I will be able to generate a whiteboard. So let's wait for it to cook.

[00:06:20]Cool. So now the plan is done. Uh as you can see it says okay we will add this slash session ID slash command. um user have no way to discover the current session ID. So let's add this uh the architecture is quite simple number of files just one and there's literally just two step the implementation and just the verify and then in the plan review box you can see that you have the accept the modify the reject just like in any other uh AI coding agent but in addition you have the whiteboard and the whiteboard we will select this one it will basically uh start to um generate the whiteboard scenes for the plan. So, let's wait for it to come back to us.

[00:07:16]Cool. So, now we have the result. And what's cool is that we can ask Vix directly to walk us through the plan.

[00:07:25]>> Hello, I'm Vix, your AI coding assistant. I've put together a plan and I'm ready to walk you through it. Where would you like to start?

[00:07:35]>> Hey, Vix, can you walk me through the plan?

[00:07:39]>> Sure thing. The plan adds a new slash command called session- ID to the TUI.

[00:07:46]The first scene shows where it slots into the command dispatcher in session.go, go sitting right between the existing clear and skills branches following the same pattern as every other built-in command. The second scene shows what the handler actually does when triggered. It reads the session's ID field, emits a stream chunk carrying that ID back to the client, and then fires an agent done event to close out the turn.

[00:08:15]I will stop here again uh for the sake of uh having a short video but you get the the whole point. So hopefully uh you found it interesting. VIX is still early. It's a small project but it's real and it works. So if you want to try it, the link is in the description. The next video I will probably cover the workflow in more depth. And if this resonated, drop a comment. I genuinely want to know if you find it interesting.

[00:08:46]See you.