mio-code
mio-code is a terminal coding assistant maintained by HoshizukiMio. Run mio for the interactive TUI, mio -p for scripting, or mio agent stdio for editor integration through the Agent Client Protocol (ACP).
mio agent also starts the local ACP stdio server. It uses the configured models and accepts JSON-RPC messages from an editor or another ACP client.
When asked about its identity, Mio can name the application and the model ID selected for the current request.
Install and update
The scripts install the current stable build from mio-code Releases. Windows x86-64 requires PowerShell 5.1 or later. Linux x86-64, including WSL, requires glibc 2.35 or later, curl, gzip and GNU coreutils.
irm https://git.hoshizukimio.com/HoshizukiMio/mio-code/raw/branch/mio-code/cli/install.ps1 | iex
curl -fsSL https://git.hoshizukimio.com/HoshizukiMio/mio-code/raw/branch/mio-code/cli/install.sh | bash
Both installers verify the executable's SHA-256 and version before installing it in the current user's .local/bin directory. Set MIO_BIN_DIR to select another directory or set MIO_VERSION before running the command to install a particular release. On Windows the installer adds the directory to the user PATH. On Linux it prints a reminder if the directory is missing from PATH.
Run mio update --check to check the latest stable release, mio update to install it, or mio update --version 1.0.47 to install a specific version. Set [cli].auto_update = false in your configuration to disable background updates.
Build
Use the pinned Rust toolchain in rust-toolchain.toml, a C/C++ toolchain and CMake, and Protocol Buffers protoc 29.3. On Windows, use the MSVC x64 Developer PowerShell and set $env:PROTOC to the path to protoc.exe. On Linux, set PROTOC to the compiler path or install DotSlash to use bin/protoc. Linux builds may also require pkg-config, ALSA development headers, and Clang/libclang.
cargo build --locked --release --target x86_64-pc-windows-msvc -p hoshizukimio-mio-pager-bin
.\target\x86_64-pc-windows-msvc\release\mio.exe --version
cargo build --locked --release --target x86_64-unknown-linux-gnu -p hoshizukimio-mio-pager-bin
./target/x86_64-unknown-linux-gnu/release/mio --version
Install rg (ripgrep) on PATH for text search on Windows. To use an existing ripgrep binary for both bundling steps, set MIO_TOOLS_BUNDLE_RG_PATH and MIO_SHELL_BUNDLE_RG_PATH to its absolute path.
Configure your model
Create ~/.mio/config.toml (or $MIO_HOME/config.toml). Replace the model ID and URL with values from your provider.
[models]
default = "coding"
[model.coding]
model = "your-model-id"
base_url = "https://your-provider.example/v1"
api_backend = "chat_completions"
env_key = "MIO_API_KEY"
Set MIO_API_KEY in the environment if the provider requires a credential. For a keyless local provider, omit env_key. Supported api_backend values are chat_completions, responses, and messages. Model configuration covers shared providers, additional headers, and model selection.
mio models
mio
mio -p "Summarize this project"
Verify
Run python tests/smoke.py <path-to-mio> --tui against the built executable. The test uses local mock endpoints and a temporary MIO_HOME. Windows TUI verification uses pywinpty.
Source and license
mio-code is a modified fork of Grok Build, originally developed by SpaceXAI. SOURCE_REV records the upstream monorepo revision. See LICENSE, THIRD-PARTY-NOTICES, and third_party/NOTICE for licenses and attribution.