Wizard is a fast, lean terminal coding agent written in Rust: a single ~60MB binary with nearly all of Claude Code's features and some it doesn't have, minus the bloat. Model-agnostic: run any local GGUF (managed for you) or OpenAI, Anthropic, xAI, OpenRouter, and Groq, and switch live. Self-extending: hit a wall and it writes its own skills, tools, MCP servers, and subagents, or rebuilds its own binary. One line installs it; everything it learns is plain, editable TOML you own.
No reviews yetBe the first to leave a review for Wizard: self-extending coding agent
A built-in way to share or sync the TOML config and generated skills across machines would be huge, even just a simple signed bundle you can pull with one command. Working across laptop and workbox is the main thing stopping me from going all in on this.
Report
Maker
@englsarpolpe3b Thanks for the feedback! I will start working on implementing that today. One of the things I was envisioning in Wizard is that after wizard self extends, you can ask it to make a GitHub Repo of your version of wizard and people could reproduce your version of wizard with an easy one line command or something.
How does the self-extending bit actually work in practice when it rebuilds its own binary - does that risk breaking anything mid-session or is there some kind of snapshot/rollback if the new build fails?
A built-in way to share or sync the TOML config and generated skills across machines would be huge, even just a simple signed bundle you can pull with one command. Working across laptop and workbox is the main thing stopping me from going all in on this.
@englsarpolpe3b Thanks for the feedback! I will start working on implementing that today. One of the things I was envisioning in Wizard is that after wizard self extends, you can ask it to make a GitHub Repo of your version of wizard and people could reproduce your version of wizard with an easy one line command or something.
@englsarpolpe3b Now added in v0.7.0 which was shipped today
How does the self-extending bit actually work in practice when it rebuilds its own binary - does that risk breaking anything mid-session or is there some kind of snapshot/rollback if the new build fails?