Skip to content

fix(gate): allow interactive Codex memory writes - #128

Merged
docwilde merged 1 commit into
mainfrom
release/0.62.22
Oct 13, 2026
Merged

docwilde merged 1 commit into
mainfrom
release/0.62.22

Conversation

@docwilde

@docwilde docwilde commented Oct 13, 2026 •

Copy link
Copy Markdown
Owner

LORE treated Codex shell commands with piped stdin as detached callers because its write gate recognized only Claude markers. A normal memory write was staged instead of applied, and gated CLI operations could fail with untrusted_write.

Recognize either non-empty CODEX_THREAD_ID or CODEX_SESSION_ID as an interactive caller in the native CLI and Python compatibility gate. Hook checks keep precedence, and source provenance defaults to the detected engine while explicit LORE_ENGINE overrides still win. MCP and agent bridge calls retain the proposal path; engine labels alone do not grant write authority.

Includes release 0.62.22 with synchronized native and plugin versions and a changelog entry.

Validation:

  • Reproduced the failure before the fix.
  • Fresh detached checkout: 200 native tests, all 40 Python test files, 11 native/Python interoperability tests, and the native launcher checks passed.
  • GitHub CI: Python 3.12, native Linux, and native macOS checks passed.

Recognize non-empty CODEX_THREAD_ID and CODEX_SESSION_ID as interactive CLI callers after hook and harness checks. Infer memory source provenance from the caller markers while preserving explicit LORE_ENGINE overrides.

Cover memory add, replace, remove, config writes, hook precedence, empty markers, and the MCP model gate. Release 0.62.22 updates both plugin manifests, the marketplace, and native package metadata.
@docwilde
docwilde merged commit 71f9698 into main Oct 13, 2026
3 checks passed
@docwilde
docwilde deleted the release/0.62.22 branch October 13, 2026 00:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant