Skip to content

Releases

0.1.5 — Discussion lifecycle and history reliability

Choose a tag to compare

@smallmiro smallmiro released this 04 Nov 11:07

Added

  • Add discussion_forget to explicitly release inactive output retained by the
    MCP process while preserving saved Codex history. Released cursors become
    invalid; read without a cursor to resume saved history while connected.
  • Ship a standalone authenticated remote app-server setup script and guide.
    The MCP connection continues to use local stdio.
  • Include this changelog in the npm package and require updates for every npm
    publication.

Fixed

  • Keep previously fetched history pages readable after disconnect, including
    concurrent reads that finish while the connection is closing.
  • Inherit reply model and effort from current persisted thread defaults and
    clear stale effort when the saved model changes without an effort value.
  • Reject local state release during active, pending, loading, or uncertain work,
    including submissions with unknown outcomes and observed external activity.

Documentation

  • Clarify delegated model selection, selection inheritance, and brief disclosure
    of the selected model and effort.
  • Add Skills CLI installation instructions and explain how to refresh copied
    skills separately from the npm package.

Update

npm install -g @mirolab/codex-discussion-mcp@0.1.5

Reconnect the MCP server after updating. Refresh separately copied skills independently.

Validation

Type checking, 121 tests, build, isolated package verification, package contents, documentation links, and JSON examples passed locally. No live inference was run for this release.

Full changelog

Publication verified

Published to npm with latest pointing to 0.1.5. Node.js 22 and 24 CI passed. The public tarball matched the successful workflow artifact byte for byte and passed registry SHA-512/SHA-1 checks, a fresh installation with an empty cache and no npm credentials, and fixture-backed MCP verification.

The OIDC attempt was rejected with E404; publication succeeded through the existing bootstrap workflow. OIDC publication remains unverified.

Publication and verification record

0.1.4 — Reliable startup reads

Choose a tag to compare

@smallmiro smallmiro released this 31 Oct 07:46
e744fb6

Fix immediate discussion reads during the Codex app-server startup window.

  • Keep locally owned running turns readable when rollout metadata is temporarily empty or current history is not available yet.
  • Match only the known startup errors; preserve unrelated failures, historical turn/cursor boundaries, and detection of work started by another client.
  • Preserve partial and final output without replaying inference. Cover both discussion start and reply.

The release candidate passed type checking, all 71 tests, the build, isolated npm artifact installation, and package-content checks. The runtime fix was also verified with Codex CLI 0.166.0 using live start/reply turns and persisted history after reconnecting.

Update a global installation with:

npm install -g @mirolab/codex-discussion-mcp@0.1.4

Update version-pinned npx configurations to 0.1.4 and reconnect the MCP server after upgrading. Refresh copied skills separately.

Fixes #13. Implementation: #14.

0.1.3 — Automatic update checks and notices

Choose a tag to compare

@smallmiro smallmiro released this 31 Oct 05:11
bacf133

Automatic npm version checks and portable update notices are now available.

  • Check public npm stable latest metadata with a 1500 ms network deadline and a persistent 24-hour user cache.
  • Expose additive update information through models_list without changing model catalog semantics.
  • Relay notices in the user's language once per newer version per session through the portable skill.
  • Disable checks with --no-update-check or CODEX_DISCUSSION_UPDATE_CHECK=0.
  • Registry/cache failures leave discussion tools usable. No automatic installation, configuration rewrite, inference or restart.

For a global npm installation:

npm install -g @mirolab/codex-discussion-mcp@0.1.3

For project-local installations, update the dependency in that project. For pinned npx configurations, update the configured version to 0.1.3. Reconnect the MCP server after updating. Refresh copied skills separately while preserving customizations.

Existing 0.1.2 processes need one manual update before they can report future updates.

Validation: 64 deterministic tests, type checking, build, packed installation verification and package contents checks. No paid inference.

Changes: #10. Release preparation: #11.

v0.1.2: Codex Discussion skill and user guide

Choose a tag to compare

@smallmiro smallmiro released this 31 Oct 04:29
75d2b75

What's new

  • Portable Codex Discussion skill and user manual. The npm package now includes skills/codex-discussion/ with its setup/tool references and docs/skills.md. The guides cover installation, invocation, model selection, complete result retrieval, and recovery. (#4)
  • Clear project selection and code review examples. The skill uses a user-specified directory or the calling agent's current directory, resolves relative paths against the caller, and passes an explicit absolute cwd. Code reviews request relevant source/tests and file-based evidence. Follow-ups retain the original project; another project starts a new discussion. (#6)
  • Codex CLI 0.166.0 compatibility evidence. The README and verification record document the existing live protocol checks. (#2)
  • Stronger package verification. Isolated installation verifies the shipped skill and manual. A regression test and atomic fixture snapshot writes prevent interrupted test runs from corrupting saved fixture history.

The MCP runtime API and dependency versions are unchanged. Automatic skill selection by a host is not guaranteed. Remote Codex connections remain a roadmap item.

Install or upgrade

npm install -g @mirolab/codex-discussion-mcp@0.1.2

Installing the package does not automatically install the skill into your agent. Follow the skill user manual, copying the complete skill directory including references. Update any existing installed skill copy separately.

Validation

Release preparation passed type checking, all 49 tests, the build, isolated tarball installation/MCP verification, Markdown/JSON checks, and independent review. This release does not claim new live inference or automatic host-selection tests; earlier observed host and Codex checks are recorded in the verification record.

npm publication completed through the existing bootstrap workflow after the OIDC attempt was rejected with E404. OIDC publication remains unverified.

The public registry's latest tag is 0.1.2. An anonymous public download matched the successful workflow artifact byte for byte by SHA-512. A fresh exact-version installation with empty npm cache/configuration passed executable and installed-guide checks; the downloaded public tarball independently passed MCP discovery and a fixture-based two-turn discussion.

sha512-2TJd1CuStfHNBxjg9e5wRV2kak0WvVn1M/ojSji4E0Eii8dulktXOgdF9EHP1HQWyiKThUjCiGfvc+RgvZ5OJw==

Source commit: 75d2b752fbea29581bd258fa3c5bab23bf5d170d. The same verified package is attached below. npm package · Release verification record

Full changelog: v0.1.1...v0.1.2

v0.1.1

Choose a tag to compare

@smallmiro smallmiro released this 25 Oct 11:28

This is the first GitHub Release of @mirolab/codex-discussion-mcp, a local stdio MCP server that lets coding agents discuss questions with Codex through codex app-server. The calling agent controls the discussion and chooses the model and reasoning effort for every turn.

0.1.1 contains no runtime behavior changes from 0.1.0. It republishes the package with English user documentation.

Install

Requires Node.js 22.14 or newer and an installed, authenticated Codex CLI.

npm install -g @mirolab/codex-discussion-mcp@0.1.1
codex-discussion-mcp --version

Register it with Claude Code:

claude mcp add --transport stdio --scope user codex-discussion -- codex-discussion-mcp

See the README for Antigravity CLI, Kiro CLI and other MCP hosts.

Highlights

These features shipped in 0.1.0 and are carried forward unchanged:

  • Dynamic model discovery: models_list reads the Codex model catalog and each model's supported reasoning efforts. Selections are validated against the catalog and another model is never substituted silently.
  • Per-turn model and effort: discussion_start and discussion_reply accept a model and effort for each turn. Changing the model without an effort selects the new model's default effort.
  • Asynchronous discussions: start and reply return immediately. discussion_read polls for public messages and progress with bounded waits and scoped pagination cursors.
  • Explicit outcomes: turns finish as completed, failed, interrupted or connectionLost. Inference is never replayed automatically after a timeout or connection loss.
  • Cancel and resume: discussion_cancel interrupts a specific turn, and persisted discussions can be read and continued after reconnecting.
  • Read-only and isolated: discussions run read-only, reuse the existing Codex login and provider configuration without reading credential files, and disable inherited MCP connections, apps and plugins. Reasoning items are never exposed.

Changes since 0.1.0

  • Translated the README and the shipped publishing guide (docs/publishing.md) to English.
  • Translated the design, verification and release records to English.
  • Added AGENTS.md, a contributor guide covering the repository map, commands, behavioral contracts and release rules.
  • Switched the live smoke test (npm run smoke) to English prompts.

Verification

Type checking, 48 tests, the build and packed-tarball installation verification (executable, MCP discovery, model selection and a two-turn discussion) passed on GitHub Actions, and that same tarball was published. The public npm tarball and the GitHub artifact have the same SHA-512, and a fresh install by name reports 0.1.1.

sha512-Tm58rb5HM+eN5VyBeIEXTOzb3uLymbl1wUyW1n9DH5zgFyQZz9nOM5FNUa+ZddveW6et3fldWCetpN3cYk0Vng==

This version was published with the bootstrap token workflow (run) because the npm Trusted Publisher for OIDC publishing is not configured yet. See the release record.

Full changelog: aa93894...v0.1.1