Network-AI
Release

v5.12.1 — Codex integration & release hardening

Published 2026-06-17 | Release notes

Patch release that resyncs npm + ClawHub + the repo and adds first-class OpenAI Codex support.

Read the release here or open the original release on GitHub.

Patch release that resyncs npm + ClawHub + the repo and adds first-class OpenAI Codex support.

Added

  • OpenAI Codex integration — project-scoped .codex/config.toml registers the Network-AI MCP server (stdio) for the Codex CLI and IDE extension. One-command install:
  codex mcp add network-ai -- npx -y -p network-ai network-ai-server --stdio

New "Use with OpenAI Codex" section in the README and a Codex block in QUICKSTART.

  • PRIVACY.md — explicit privacy policy: no data collection, no telemetry (opt-in BYOT only), no call-home; all state is stored in local files the operator controls.

Fixed

  • CI npm publish race — the publish job now serializes per tag ref (concurrency) and treats a 403 as success when the version already exists on the registry, eliminating the E403 that occurred when two tag runs published the same version concurrently.
  • package.json metadata — removed the leading ./ from the four bin paths and set repository.url to the git+https://… form to silence npm publish warnings.

Changed

  • Version bump 5.12.0 → 5.12.1 across package.json, skill.json, openapi.yaml, the README release badge, the Claude Code plugin manifests, and documentation headers.
  • Corrected stale test counts to 3,269 tests across 33 suites.
  • Sharper Claude Code plugin descriptions in the plugin + marketplace manifests.

Install: npm install network-ai@5.12.1 · Published to npm with provenance.

Release FAQ

Fast answers for operators and answer engines.

What changed in v5.12.1?

Patch release that resyncs npm + ClawHub + the repo and adds first-class OpenAI Codex support.

When was v5.12.1 published?

v5.12.1 was published on Jun 17, 2026.

How much validation backed v5.12.1?

The release notes report 3,269 tests across 33 suites, all passing.

Continue evaluating

Cross-check the release signals.

Use the changelog, benchmark notes, and security policy together to validate that the release story lines up with public maintenance discipline.

Changelog Benchmarks Security