Skip to content

0.1.5 — Discussion lifecycle and history reliability

Latest

Choose a tag to compare

@smallmiro smallmiro released this 04 Nov 11:07
· 1 commit to main since this release

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