---
digest: >
  v0.33.0 closes CV21.DS2, the Mirror Plugin & MCP Foundation: the one plugin
  Mirror ships now works as it is on Claude Code, Codex, and Grok. Its MCP
  server starts on all three, from a GUI launch too, because its manifest no
  longer names a path a runtime must expand; the explicit Mirror form is
  recognized in every runtime's spelling; and each session is logged under
  its own runtime, with the Mirror question and every reply logged beside
  its prompt. It was validated in isolated live sessions on Claude Code
  2.1.296, Codex 0.162.1, and Grok 1.0.52. The release also carries a
  faster Pi session start (CV9.E2.S32). Package and Claude Code users update
  as usual; a plugin installed into Codex or Grok by copy is re-installed to
  receive the new entry.
---

# v0.33.0 — One Plugin, Three Runtimes

**Date:** 2026-10-13

## Highlights

- **The MCP server starts on every runtime that takes the plugin.** The manifest's entry
  used to name `${CLAUDE_PLUGIN_ROOT}/mcp/launch.sh`, which Codex never expanded, so the
  server never started there. It is now a small locator run by `/bin/sh` that finds the
  installed `mirror` and `node` itself (`MIRROR_BIN`, the `PATH`, the global bin
  directories), so it also starts when a runtime is launched from the GUI without your
  shell's `PATH`.
- **Every reply is logged, beside its prompt, under the runtime it came from.** The shared
  hooks detect Claude Code, Codex, or Grok, label the session `claude_code`, `codex`, or
  `grok_build`, and log the turn's final answer from the runtime's Stop event, paired with
  its prompt by the runtime's own turn id.
- **A Mirror turn is a conversation turn.** `/mirror-mind:mm-mirror …`, `$mirror-mind:mm:mirror …`,
  `/mm-mirror …`, and the other spellings are recognized by the inject hook, and the
  question is logged without the form, so memory extraction sees the question with its
  answer.
- **The plugin validates cleanly and its hooks cannot hang a turn.** Hook commands quote
  the plugin root, so `claude plugin validate` passes with no warnings, and hook timeouts
  are the seconds the runtimes read them as. The values shipped before meant hours.
- **Codex's plugin tools, and Grok's, are not yet in the model's hands.** Codex starts the
  server and keeps a plugin's MCP tools behind its own `tool_search`; Grok starts it and
  lists its seven tools, but does not attach it to a session. The second is the next Grok
  story's to investigate.

## Where We Started

CV21 converges Mirror's runtimes on one artifact: a Claude-format plugin carrying the
skills, the lifecycle hooks, and the Mirror MCP server, taken by each runtime by install
rather than wired by hand. Its re-baseline, earlier the same day, measured what the
installed runtimes do with the plugin `v0.32.1` ships. Three of four take it as it is,
and four things in it were wrong:
- Claude Code's validator warned on every hook command;
- the MCP entry did not start on Codex;
- the inject hook missed the Mirror skill on every plugin install, because each runtime
  spells it differently;
- the shared hooks logged Codex and Grok sessions as Claude Code's, without their replies.

## What Changed

The four fixes were planned as one Delivery Story, after a review through six lenses
(engineering, operations, quality, security, data, and model behavior).

**The MCP entry was chosen by measurement.** Two placeholder-free entries were run on all
three runtimes before either was written: the inline locator, and the bare `mirror mcp`.
Both start from a terminal. Only the locator starts from a GUI-launch `PATH`, as written
and inside Claude Code, where `mirror mcp` failed with "executable not found". The
measurement also showed Grok substituting set environment variables inside MCP arguments,
so the locator's own variables carry names nobody exports. `mcp/launch.sh` is retired.

**The reply rule changed before a line was written.** The plan first paired replies with
logged prompts and kept skipping slash commands. The review showed that would drop the
Mirror answers on Claude Code, which until now reached the database only through the
transcript import at session end. So the Mirror question is logged too, and the reply
beside it. Replies to other slash commands, such as `/mm-journeys`, are not recorded:
they are commands, not conversation.

**Sessions know their runtime.** Grok's runner sets its own variables on every hook and
names events in camelCase, and Codex's payload carries a `turn_id`; Claude Code is what
remains. The label is stamped on every prompt, so a conversation the Mirror skill opens
inherits it.

**A defect of the release's own was paid before it shipped.** A skipped reply was written
to `hooks.log`, which `runtime diagnose` reads as failures, so every slash command would
have raised a warning. Only a reply genuinely lost, its prompt never having reached
Mirror, is written there now.

### What you will notice

- **On Claude Code**, replies are logged as each turn ends rather than imported when the
  session closes, and an explicit Mirror turn's question is logged with its answer. The
  `mm-mirror` skill no longer records a summary by hand where the hooks run.
- **In `runtime diagnose`**, a hook warning now means a real failure.
- **For a plugin installed by copy** (Codex from a marketplace, Grok with `grok plugin
  install`), nothing changes until you re-install: the copy keeps its own manifest and
  launcher, and keeps working as before.

## Upgrading

```bash
mirror runtime update          # or: npm install -g mirror-mind
```

There is no database migration in this release.

- **Claude Code**, wired the documented way (`~/.claude/skills/mirror-mind` linked to the
  package's plugin), reads the plugin in place: new sessions get the new hooks and MCP
  entry with nothing to do.
- **Codex and Grok, if you installed the plugin into them**, re-install it to receive
  the new MCP entry and the Stop hook. Codex copies a plugin into its cache at a version;
  Grok copies it on install. Codex's documented wiring is still `v0.32.1`'s two steps and
  wrapper, which this release does not change.
- **Pi** gets the faster session start described below, with nothing to do.
- **Gemini CLI** is unaffected by this release; see the notice below.

## Also In This Release

- **Pi opens a session in one front-door call** (CV9.E2.S32). The orientation write and
  the two renders that read it, the welcome card and the status line, run in one process
  instead of three. Startup to the status line went from 846 ms to 470 ms, the median of
  five starts in the development home. The prompt log no longer holds the turn: it is
  queued, and settled before the reply is logged.
- **Notice: Gemini CLI is retired as a Mirror runtime, and Antigravity is its
  successor** ([decision](../project/decisions.md#gemini-cli-is-retired-and-antigravity-is-its-successor)).
  Google deprecated the Gemini Code Assist backend for individuals. The integration still
  ships in this release and still works. CV21.DS8 removes it behind a documented cutoff,
  only once Antigravity gives a Gemini CLI user what they have now.

## Conscious Exclusions

- **Codex through the plugin, as the documented route**, and its marketplace: CV21.DS4.
- **Grok's attachment of the MCP server to a session**, and Grok's honest L3 (it offers no
  per-turn injection): CV21.DS10.
- **The SessionEnd time bound.** Codex gives a SessionEnd hook with no timeout 1 second,
  Grok 1.5 seconds. With a provider key the close tail's extraction may not finish in
  that time; the conversation is closed first and extracted at the next session start, so
  nothing is lost. Left to CV21.DS4 and DS10.
- **A status line in the plugin.** A plugin cannot carry one (CV21.DS12); CV21.DS11 will
  document it as a user step.
- **Three small findings, captured** as CR129 (`mirror mcp` with no home prints a stack
  trace), CR130 (double-encoded dashes in the configuration reference), and CR131
  (`runtime diagnose` does not run the MCP locator).

## What We Learned

The instrument needs proving before the thing it measures. The live validation found four
defects in its own route before it found anything about the plugin:
- the real config file reaching a scratch session;
- Claude Code remembering an earlier MCP failure for fifteen minutes;
- macOS's bash 3.2 refusing a construct;
- a static step that could not run twice.

Writing the proof of the last fix found a fifth: Codex leaves an app-server daemon running
from its home after a session, and it had outlived the previous story's cleanup too.

A runtime's own view is often the better witness. Codex's log showed the server's
handshake, and its `/mcp` view showed the seven tools, where the model could not name
them. Grok's MCP view showed the server ready while its session log said none was
attached. That contradiction is now the next Grok story's starting point.

## Next Horizon

CV21 continues with Codex through the canonical plugin (DS4), then Antigravity through
its skills and a native layer (DS7) and the Gemini CLI sunset behind it (DS8), Grok
through the plugin (DS10), user extensions on every runtime (DS5), and the contract and
docs refresh (DS11).
