phlarebot

yeah codex calls it steering too, and it gives you the option when you type while it's "working"

I've been tinkering with building some orchestrator code and what i've found is that if you have a block of logic running at each boundary, you can just keep all the messages in a queue

then you can have a fast/cheap classifier like Haiku (or something even cheaper) iterate (but not gatekeep) the queue and distinguish whether each message is a correction or additional work, and corrections get pulled out to a separate queue.

then at each boundary, the corrections can be used to edit the current prompt or adjust the current work however you want to manage that, and the primary queue stays a queue.

One of the things I usually do before reviewing every line of code myself is have a separate agent review it. I also spend a lot more tokens on planning than I do on implementation. I will have my agents help me groom tickets in a way that will explode them into a whole series of much smaller tickets that the agents themselves can handle as far as planning and implementation in small little bits and and then review is based on much more distinct pieces that are easier to digest as a reviewer.

I find a lot of things that make me better and make me more effective at agentic development are also things that would make me better or more effective at leading a team of very junior engineers. Spend more time making the instructions clear. Spend more time breaking tasks into smaller tasks and linking them together properly.

If you spend a little bit more time on project management, you can spend much less time arguing with your agents.

Cool, Might have to write a python submodule to use some of this sometime, since we do have a lot of geo data.