Between life and the constant changes in AI engineering, this post has been nearly a month in the making. Things change, and we adapt so quickly that it is hard to sit down and think through what is actually going on. Here is what my current stack and setup look like.
The Agent Runtime
A year ago, I would not have given agent runtimes much thought. Once you start kicking off more tasks, including tasks that run in the background, you need a good way to manage the agents. cmux was the first tool I tried that clearly felt better than managing a bunch of tabs in a terminal (or worse, many Zed instances).
When I started writing this post, Solo was my daily agent runtime. I still think Solo is quite good, and the less comfortable you are in the terminal, the more likely Solo is the right fit for you.
I recently switched to Herdr, and I have been enjoying it quite a bit. I like having a single tool that I can use in a variety of ways, and being able to use it via SSH is great. It fixes most of my grievances with tmux, and with BetterTouchTool, you can even make the prefix key slightly less annoying. I haven’t used its orchestration features much, but Herdr also supports a Solo-like workflow. Hopefully, this is the last switch in a while (or at least until we see what Superlogical is up to).
The Harness
Pi is still the harness I reach for and recommend, except when using something from Anthropic. Hopefully, they get their heads out of their asses at some point.
Herdr + Pi is a very flexible combination. You can run them just about anywhere with just about any model. Both have strong extension stories, so even if you have a very specific workflow in mind, you can likely modify one or both to meet your goals.
Models
I want to keep driving home the need to use multiple models. I don’t know whether there will ever be a time when you should go all in on a single model, but that time is definitely not today. I have been primarily using OpenAI’s Sol and Luna options. The recent pricing changes on Luna have made it almost free.
While I have not enjoyed using Opus 4.x much this year, I have found Fable quite good. It has become a mainstay despite requiring me to use Claude Code.
OpenCode Go continues to be a fantastic way to get access to a variety of other models. For $10 a month, you get access to Kimi, GLM, and more.
Background Agents
I have spent a good chunk of my professional time setting up a customized version of OpenInspect. OpenInspect is a framework for background agents. The initial setup is simple but a bit tedious. The real work is figuring out a dependable workflow that ensures tickets are completed accurately without requiring a lot of follow-up work from developers. Spending more time up front on tickets helps a lot, but this is a place where solid guardrails, including specs, validation rules, and skills, will pay huge dividends.
I see some version of background agents as the future. I recently started setting up Amp’s Orbs for KickoffLabs. It is too early to report on Orbs, but I am confident that sitting at a computer and hacking prompts into a CLI does not have a long shelf life. We will spend more of our time and effort putting these systems in place to build confidence that what comes out of the factory or loop meets both end users’ expectations and our own.
So far, most of the completed tasks have been simple one-offs, but I hope better guardrails will let us take on more complex work with less human intervention.
Skills
Skills still feel vastly underutilized. Prompt > Read > Reprompt undersells the power these models have given us.
I started 2026 using SuperPowers. SuperPowers was the first skills-based “workflow” that stuck for me. However, I started to feel like I was fighting against it at times. The brainstorming-to-spec step sometimes did not go far or deep enough. Then I would be working on a quick bug fix, and SuperPowers would want to write a spec first.
I eventually turned my attention to Matt Pocock’s skills. They were a breath of fresh air. Grill Me was great and always went plenty deep. The skills were only invoked when I explicitly asked for them.
However, I found that they lacked some of the discipline I enjoyed with SuperPowers.
So a few weeks ago, I started working on my own “fork” of Matt’s skills with some of the discipline you get from SuperPowers. I recommend starting with SuperPowers or Matt’s skills first, but if either of these issues resonates with you, check out tracer.
The tracer workflow:
- Draft a quick
overview.mdabout a project (or feature) I wish existed. - Feed the overview to Interview Me (brainstorm/grill-me) and answer every question it can throw at me.
- Have these questions and answers formatted into a spec.
- Have this spec turned into tickets.
- Have something orchestrate the tickets into code.
Depending on the type and scale of the work, I may look over the code, review it with quorum, or just move on to the next task.
Yap, Muv, and Lewp all started this way.
Resources
- Matt Pocock
- Building Great Agent Skills: The Missing Manual.
- Grill Me. The batch update has made this indispensable skill even better. During a grilling session, each passing question gets you closer to shared understanding. Often, you spend the last 50% or more saying “yes” or “agreed” over and over. Batch mode lets you answer those questions in bulk, and dictation makes it even faster. On the odd chance something goes off the rails, you can quickly address that item without waiting through turn after turn.
- Teach. Have your agent teach you about any topic you choose.
- SuperPowers - If you want a coding workflow that just works, start here.
- Impeccable. This has been great at catching contrast issues, minimizing the use of some common AI slop, and more.
Tools
Here are some other tools that have been in my rotation:
- Solo - I wrote about why I started using Solo.
- Herdr - It took me so long to write this post that I switched my agent runtime in the middle of it. You get dedicated workspaces, sessions, SSH support, and more, all built in. Like I said at the top, if you do not like the terminal, stick with something like Solo. However, if you liked the organization and orchestration in Solo but wanted something a little more flexible and terminal-first (especially over SSH), you will be very happy with Herdr.
- Claude Design - Before Fable, I mostly used Claude for code reviews. I find Claude Design extremely frustrating to use. It screams vibe-coded and throws up all over the place, but it’s the best visual tool I have used to date.
- Fluid Voice - I have changed my voice-to-text tool with each issue, and this one is no different. Fluid does a great job of cleaning up what you say, has a nice long-hold + click option for recording more with a single key, and optionally shows you a real-time preview.
- sideshow - A sneaky good feature of Solo is its scratchpads, which store context outside your repo. After switching away from Solo, I needed to fill that gap. I had sideshow bookmarked, and it has done the job nicely. Solo’s scratchpads currently support only Markdown, while sideshow supports a variety of formats and images that you can easily share with the outside world.
Prediction
In the first issue, I suggested Google was the sleeping giant I expected to make a big play this year. I am going to back off that prediction. Nothing Google has shipped has stuck with me. I wonder if this is just evolution at its finest.
You’ve made yourself indispensable.
Aaron Burr, Hamilton
My new bet is Cloudflare. They are staying out of the model game while continuing to build and ship useful services with great AI workflows. I see a future in which Cloudflare is the glue that connects your services and applications to any model. It feels like we are going to wake up in a year or two and realize everything is running directly on Cloudflare instead of just routing through it. Cloudflare is making itself indispensable.
Next?
My guess is the next few months will involve a lot of Fable and Sol. I am committed to experimenting elsewhere. My goal is to someday have access to great models that are not tied to a massive corporation, without the risk of a government cutting off that access. Still, it is hard to ignore the massive leap made in the past month.