> So yes, all layers have code written. But "code exists" doesn't mean "done right." Let me check the DroidAdapter more carefully since that was the one you wanted to focus on: Oh, really? That's a good sentiment.

1962: bootstrapping a Lisp compiler with Lisp 1973: bootstrapping Unix in C 1985: bootstrapping Emacs with Emacs Lisp 2026: bootstrapping coding-agent orchestration with itself

WIP #buildinpublic

Approvals work

Plans work too. It's definitely easier to improve once they start appearing #buildinpublic

Sounds like Railway?

I like the timing count #buildinpublic

I'm back after a few days break 💪

I haven't tried, but the UX for https://rjcorwin.github .io/cook/ is interesting # compose freely cook "Implement dark mode" review v3 "cleanest result" and part of what I strive for with my own orchestrator tool is to be able to pick a project/repo + fire off a task easily.

Tokens are back

Expecting work to speed up now that I have a form of primitive queue system in place #buildinpublic

A little touch to auto discover icons #buildinpublic

So. Uh. I did a thing. This is my game.

The problem for most people with using agentic coding agents is that you become a team lead/manager that can be detached from the code. The advantage of agents over human team members is you can always step in to design/review/change the code and design. So take advantage of that

A bit of irony in HopperMCP's README

Feels powerful being able to queue tasks, let each run to completion and move on to the next. Worktrees don't work for me so I mostly work on main. Queuing is a tradeoff, I can only work on 1 task in the project at a time, but I need less intervention.

It's fun

This is my favorite part that works with the queuing system

Wow, there are people selling discounted Claude Max access.

Feels like I'm not working to my full potential when the queue is empty #buildinpublic