Cumulative since 0.2.0 (P1-P7): adds P8 cowork inbox push which
delivers a symmetric, at-next-UserPromptSubmit, ephemeral handoff
channel between Claude Code and Codex on top of a per-project
JSONL inbox. This release is the first time mempal has been
validated end-to-end with real Claude Code + Codex TUI traffic on
both directions.
P8 surface
- mempal_cowork_push — 9th MCP tool, send a <= 8 KB handoff to partner
- mempal cowork-drain — drain inbox, canonical plain or codex-
hook-json envelope, graceful degrade
- mempal cowork-status — read-only view of both inboxes at cwd
- mempal cowork-install-hooks — install / self-heal hook artifacts for
Claude Code (script + settings.json) and
optionally Codex (~/.codex/hooks.json)
- MEMORY_PROTOCOL Rule 10 COWORK PUSH (SEND / READ / PERSIST triad)
Process
- 4 rounds of spec/design review + 2 plan review rounds absorbed
BEFORE first implementation commit (425094d).
- 3 rounds of code-review feedback + 2 E2E-surfaced findings absorbed
AFTER implementation: round-3 (28e749e), Claude settings.json
registration (181fa32), codex_hooks feature-flag warning (56de1bf).
- Post-tag Codex package-hygiene review caught maintainer files in
the crate tarball; package.exclude landed in e5437fc and this tag
was rewritten to point at that commit (tag was never pushed).
- Bidirectional E2E traced live this release cycle.
Known limitations (cross-system, documented in README / usage /
AGENTS / CLAUDE, not mempal bugs):
1. install-hooks writes two Claude-side artifacts (script +
settings.json entry). Claude Code does not auto-discover bare
hook scripts.
2. Codex runtime is gated behind the `codex_hooks` feature flag,
currently "under development" and false-by-default in shipped
codex-cli. install-hooks warns + prints activation command.
3. Codex TUI caches config at process start; must be restarted
after flag or hooks.json changes.
4. Claude Code spawns mempal MCP server at client startup; upgrade
mempal binary => restart Claude Code for new tools to show up.
5. mempal_cowork_push is scoped to the Claude <-> Codex pair;
generic MCP clients without a recognized ClientInfo.name cannot
push (caller identity is required for self-push rejection and
InboxMessage.from).
Verification
- cargo test --workspace PASS
- cargo test --workspace --all-features PASS
- cargo clippy --workspace --all-targets --all-features
-- -D warnings PASS
- cargo fmt --all --check PASS
- cargo package --allow-dirty --locked PASS
(67 files, 673.2 KiB / 187.0 KiB compressed; no maintainer
files leak into the crate tarball)
Packaging advisory
- cargo warns Cargo.lock contains yanked core2 v0.4.0 via
jieba-rs -> include-flate -> libflate. Transitive dev-chain
dependency, not user-actionable today, will reassess when
jieba-rs publishes an update.
Non-goals this release: no cargo publish, no git push origin,
no upstream Codex PR to stabilize the codex_hooks feature flag.