I think this is the first week in which I do not have spent any time on feature development on the coding part of LazerBunny. I was using my coding agent, router and controller every day and things just worked. A pleasant surprise to be honest. Instead of rushing into working on the rest of the stack I only implement a single feature for the brain.
Sometimes it is important to call a project "good enough" and start using it for some time, instead of continuing to constantly iterating on it. And this week I did that with the coding part of LazerBunny. (There is obviously still a long list of todos, but none of them are show stoppers.)
This week was one of the most random, unfocused weeks I spent working on LazerBunny and so many things moved forward in a meaningful way. The goal never was to get everything "done", but good enough to use it on a daily basis and validate design decisions and figure out potential adjustments that need to be made.
It is rare for me to quote Mike Tyson, be he was onto something with this. Here is the thing with coding agents: you will not tell a coding agent to do something in one sentence and then something usable falls out. I mean… there is a chance - depending on your prompt. If you tell it to copy something that exists millions of times on GitHub. But anything even remotely more involved than that, things will be a bit more tricky, especially if you are dealing with an existing system and not one shot-ing a Tetris clone.
Building out a small fleet of coding and research agents for LazerBunny means I regularly have requests to LLMs running, which are hosted on various hardware in my local network. This is not a big deal most of the time, but things get a little bit more interesting when multiple agents compete for the limited local resources. I spent some time this week to look into potential solutions.