Thanks for the feedback. I've made a couple of updates:
- Starting with 0.4.0, the reviewer gets the diff of the earlier chunk for any file the current chunk touches again. Also, if a new chunk weakens or removes a test or assertion from an earlier chunk, the reviewer will block it unless the plan says to do so.
- About read-only: The reviewer's tools were already limited by the SDK (no shell or write tools). However, it was still finding MCP servers from my Claude config. I have now blocked those. The docs now explain what is enforced by the system and what is just a prompt instruction.
- lets you configure different models for planner, coder, and reviewer roles. (e.g., using Claude as an adversarial reviewer against Codex)
- breaks your plan up into reasonable-sized chunks of work with clearly defined success criteria
- runs each chunk of work through a coder / read-only reviewer loop. Once both agents are satisfied, neal moves on to the next chunk. Once everything is complete there is a final pass through the coder / reviewer loop to ensure the implementation satisfies the entire plan.
- resets the coder's context with each chunk of work to prevent context drift, leaving the reviewer's context long-running.
It uses a local LLM to translate Claude's output.
https://github.com/navels/neal
neal is a CLI I wrote while trying to use an LLM coding agent (in this case, Codex GPT-5.4) to work autonomously on a migration of our large frontend codebase. A few things came up during that project that guided the development of neal:1. Telling an agent to "keep working unless blocked" doesn't actually work over long stretches of time.2. Large projects should be broken up into smaller chunks...
https://github.com/navels/neal
neal is a CLI I wrote while trying to use an LLM coding agent (in this case, Codex GPT-5.4) to work autonomously on a migration of our large frontend codebase. A few things came up during that project that guided the development of neal:1. Telling an agent to "keep working unless blocked" doesn't actually work over long stretches of time.2. Large projects should be broken up into smaller chunks...
Enabling developer mode will soon become mandatory for running userscripts via Tampermonkey.
Not a big deal for me, I have extension dev mode on all the time, but ymmv.
Some discussion here: https://groups.google.com/a/chromium.org/g/chromium-extensio...
There’s some dispute over how and why Sholes and Glidden arrived at the QWERTY layout. Some historians have argued that it solved a jamming problem by spacing out the most common letters in English; others, particularly more recent historians, hold that it was designed specifically to help telegraphists avoid common errors when transcribing Morse code. Regardless, after around 30 test models, Sholes and Glidden settled on QWERTY—and changed the world.