Skip to content

chore: drop orphaned codex memories MCP crate#24555

Merged
jif-oai merged 1 commit into
mainfrom
jif/drop
May 26, 2026
Merged

chore: drop orphaned codex memories MCP crate#24555
jif-oai merged 1 commit into
mainfrom
jif/drop

Conversation

@jif-oai
Copy link
Copy Markdown
Collaborator

@jif-oai jif-oai commented May 26, 2026

Why

The memory read-tool surface had two implementations: the app-server extension path under ext/memories, and an unused codex-memories-mcp workspace crate under memories/mcp. The MCP crate no longer has reverse dependents, so keeping it around preserves duplicate backend, schema, and tool code that is not part of the live app-server memory path.

Dropping the orphaned crate makes the remaining memory crate split clearer: memories/read owns read-path prompt/citation helpers, memories/write owns the write pipeline, and ext/memories owns the app-server extension integration.

What changed

  • Removed the memories/mcp crate and its Bazel/Cargo metadata.
  • Removed memories/mcp from the Rust workspace and lockfile.
  • Updated memories/README.md so it only lists the remaining reusable memory crates.

Verification

  • cargo metadata --format-version 1 --no-deps succeeds.

@jif-oai jif-oai changed the title chore: drop codex memories MCP chore: drop orphaned codex memories MCP crate May 26, 2026
@jif-oai jif-oai merged commit d579daf into main May 26, 2026
44 of 45 checks passed
@jif-oai jif-oai deleted the jif/drop branch May 26, 2026 09:29
@github-actions github-actions Bot locked and limited conversation to collaborators May 26, 2026
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant