Skip to main content
Codex gets two Nika surfaces: the MCP oracle and the first-party plugin. Binary first (brew install supernovae-st/tap/nika · other paths):

What it writes

~/.codex/config.toml — TOML, not JSON. The writer edits only the [mcp_servers.nika] table and keeps your comments and unrelated tables intact; re-running prints · current (idempotent). The same block by hand:

The plugin (skill + commands)

Then nika init in the repo — the agent-teaching surface (AGENTS.md, rules, the repo skill) is what makes the oracle useful (agents guide).

Keep it fresh

Two things move, on the same release train — the plugin never updates the binary, and brew never updates the plugin:
nika doctor answers “is my suite coherent?” — from v0.107 it names any kit lagging or leading the binary’s train, with the exact fix per client. Drift is advisory (warn · exit 0), so it never breaks automation.

Verify

Codex’s MCP server list shows nika with the nine nika_* tools (the oracle’s contract). Then prove the loop end-to-end: integrate in 10 minutes.