# MaxiMind Code — releases and how updates reach users

Public copy: `https://maximind.dev/docs/code-releases.md`. Newest first.

## How versions work

- Every release is a signed, immutable file named by version (`maximind-code-<version>-macos-arm64.tar.gz`). The install command and `maximind update` always take the newest one listed in the signed `manifest.json`.
- **Users are told automatically.** Each time `maximind` starts it checks the release list at most once a day (4-second limit, silent if offline) and prints a line in the first screen: `Update: MaxiMind Code X is available (you have Y). Run: maximind update`. `maximind doctor` and `maximind update --check` show the same.
- **Ordinary update:** the user runs `maximind update` (about 30 seconds; history and settings are kept; `maximind rollback` undoes it).
- **Forced update:** when a release changes the wire protocol or the tool format, the server answers old clients with `426` and the message "this MaxiMind Code version is no longer supported; run maximind update". Only then is updating mandatory. Model catalogue changes never need an update.
- **Re-running the installer** (`curl … | sh`) is the same as `maximind update` for someone who cannot remember the command.

To announce a release to people, point them at this page; the "What to do" line under each version is the only instruction they need.

## Versions

### 1.0.10 — 2026-09-18
- Fix: the project boundary lets MaxiMind MCP tools (`maximind__…`) through to the server. Replaces 1.0.9.
- What to do: `maximind update`.

### 1.0.9 — 2026-09-18
- Fix: MaxiMind MCP tools list correctly (adapter path). Replaces 1.0.8.
- What to do: `maximind update`.

### 1.0.8 — 2026-09-18
- Fix: the MaxiMind MCP server now loads (settings written where the runtime reads them). Replaces 1.0.7.
- What to do: `maximind update`.

### 1.0.7 — 2026-09-18
- New: MaxiMind tools inside the terminal (`youtube_transcript`, `video_info`, `web_read`, `transcribe_url`, `speak`) through a bundled MCP server; your approved MaxiMind skills appear in `/skills` automatically.
- What to do: `maximind update`, then `maximind login` if you were still on the owner key (tools need a device sign-in).

### 1.0.6 — 2026-09-18
- New home: `https://maximind.dev`. New installs and updates use it; existing installs keep working on `maximind.macsvff.uk`, which stays alive (both names are the same server).
- What to do: nothing required. `maximind update` moves this computer to the new name.

### 1.0.5 — 2026-09-18
- New: the first screen announces a newer version (daily check); this page.
- What to do: `maximind update` (optional; nothing breaks if you wait).

### 1.0.4 — 2026-09-18
- Security: patch edits (GPT-family models) checked structurally; `su` refused on any line.
- What to do: `maximind update` (recommended).

### 1.0.3 — 2026-09-18
- Security: command filter matches any letter case; `su` behind `env`/`exec`/paths; stricter patch headers. Slot wait bounded.
- What to do: `maximind update` (recommended).

### 1.0.2 — 2026-09-18
- A third simultaneous window waits up to three minutes for a free account slot instead of failing.
- What to do: `maximind update` if you use several windows.

### 1.0.1 — 2026-09-18
- Security: `apply_patch` confined to the project; unknown tools refused.
- What to do: `maximind update` (recommended).

### 1.0.0 — 2026-09-18
- First release: macOS 13+ on Apple Silicon. Windows not available.