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. It keeps stable prompt prefixes so supported providers can reuse work, maintains a searchable code index, runs background jobs, tracks its own working notes, and resumes where you left off.

Wizolt is the former minacode, which began as the single-file nanocode. The project history remains continuous across those names.

Editing code and running tools in one interactive session.

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
# add your provider's url, key, and model to that file
wizolt

Full walkthrough: Getting started.

What it does

Working through a repository task in an interactive session.

Area	In short
Interaction	Follow-ups, streaming, keys — how you drive the agent.
Commands	The / command reference: status, models, sessions, MCP.
Tools	Read, search, navigate code; edit files; run commands; background jobs; optional provider-side web search.
Sessions	Your work is saved, named, and resumable with /sessions, -c, or --resume.
MCP	Connect external Model Context Protocol servers and use their tools.
Worker	Delegate bounded tasks to a second in-process session on its own provider, with context kept until reset.
Skills	Load reusable instruction packs on demand.
Configuration	Providers, runtime settings, and data location.
Compatibility catalog	How documented provider/model exceptions are selected, updated, and overridden.
Context	How the window is filled, summarized when it fills up, and reused by the provider’s cache.
Safety	What wizolt can reach, and how to keep that bounded.
Troubleshooting	What a symptom means and what to do about it.