wizolt¶
A terminal coding agent
wizolt works in your terminal: you describe a task, and it reads code, edits files, runs commands, and reports back. Review changes as it works, add a follow-up at any time, and resume where you left off when you return.
Wizolt is the former minacode, which began as the single-file nanocode. The project history remains continuous across those names.
A long session with background jobs, edits, and the live status bar.¶
Use at your own risk
wizolt edits files and runs shell commands in the directory where you start it. It has no sandbox of its own. Run it inside a container, VM, or another isolated environment when you need isolation. See Safety.
Install and run¶
uv tool install wizolt
wizolt --init-config # write ~/.wizolt/config.toml and secrets.toml
# add your provider's url and model to config.toml, its key to secrets.toml
wizolt
Full walkthrough: Getting started.
What it does¶
Working through a repository task in an interactive session.¶
Area |
In short |
|---|---|
Follow-ups, streaming, keys — how you drive the agent. |
|
The |
|
Read, search, navigate code; edit files; run commands; background jobs; optional provider-side web search. |
|
Your work is saved, named, and resumable with |
|
Connect external Model Context Protocol servers and use their tools. |
|
Run parallel agents and switch between their separate conversations. |
|
Load reusable instruction packs on demand, or point the agent at one with |
|
Customize wizolt with Python, or enable the built-in pet. |
|
Automatically run your checks, formatters and cleanup commands. |
|
Themes, statusbar layouts, dividers and sweep animations. |
|
Providers, runtime settings, and data location. |
|
Check provider compatibility and update it. |
|
Keep long tasks going and understand token usage. |
|
What wizolt can reach, and how to keep that bounded. |
|
What a symptom means and what to do about it. |