mplorentz on Nostr: I wrote about the broad strokes in this note: ...

I wrote about the broad strokes in this note:

quoting nevent1q…m7tp

Against my better judgement I have now homebrewed my own AI agent orchestration harness. I'm running a bunch of different pi.dev harnesses in tmux with a watchdog agent that can restart or send them messages. Each persona (planner, coder, tester, reviewer) has its own prompt and handoff protocol to move work to the next agent. All the tasks and plans are tracked in a beads database. It's a lot like Steve Yegge's gas town but it works much better with my theory that passing work through different models and personas produces much higher quality output. It also works much better with local models and doesn't have a ton of bugs. And it's all running on my old gaming pc with limited permissions to my repos and no credentials for production services.

Since Cursor killed off my previous workflow (pair with a really fast agent to work on a big feature, maybe have a couple easy side quests going elsewhere) I have been trying to switch to a "slow productivity" model of development. By which I mean minimizing context switching and being fully present to review one piece of work at a time. This means I want my AI pipeline to produce the highest quality work even if it takes a long time. And I also don't have a thousand dollars to spend on tokens each month, so I can't just send codex or claude code off to spin for hours on every task. Right now I'm using a combination of GLM 5.1, Deepseek v4 Pro, Deepseek v4 flash, and Qwen 3.6 37B A3B (last one running locally). What are you using for orchestration?