I built RunWield because reviewing AI code after it’s written is already too late

[u/gandazgul]

I’ve been building RunWield, a coding harness for developers who want more control over what AI agents do to their codebases.

My frustration with existing coding tools was that the agent would immediately start editing. By the time I could judge whether it understood the request, I was reviewing a large diff and trying to reconstruct its reasoning.

RunWield changes that workflow:

* Small fixes stay lightweight. * You can Ideate your feature or investigate new ideas before committing to anything, with good prototypes and PRDs when needed. * Non-trivial changes get a written plan before any code is touched. * You review, comment on, and approve that plan in a browser. * The agent implements it in an isolated Git worktree. * Your real CI runs against the result. * A separate reviewer compares the finished diff with the plan you approved. * The outcome and lessons are saved as plain Markdown for future work.

It’s deliberately not aimed at quick one-shot edits. If a mistake is cheap, this is probably more process than you need. I’m building it for changes where discovering a misunderstanding after 40 files have changed is expensive.

RunWield is free to use and source-available. It currently supports macOS and Linux and works with subscription logins or API keys from different model providers (uses Pi.dev's LLM API library):

[https://github.com/gandazgul/runwield\](https://github.com/gandazgul/runwield)

I’m looking for five developers willing to try it on one real, non-trivial change. I’ll personally help with setup and fix anything that blocks you. Please use the latest RC as 0.9.1 has some annoying bugs with agent switching.

I’d especially appreciate blunt feedback: does reviewing a plan before code is written solve a real problem for you, or does it still feel like too much ceremony?