MemDock open-sourced as a shared memory and Skills workbench for Claude Code and Codex
11/09/2026 — 11/11, 12:17·2 sources (all)·2 reports (all)
Key takeaways
- A developer open-sourced MemDock, a desktop workbench for managing memory and Skills across Claude Code and Codex. It offers rule-file searc…
Background & analysis
On November 9, 2026, a developer posted on V2EX announcing MemDock, described as a desktop workbench that centrally manages the memories and Skills of the coding assistants Claude Code and Codex. In the post, the author explains that two kinds of friction emerge over long use of the two tools: test commands may long since have been replaced, yet new sessions still run on stale rules, and updating a Skill requires digging through directories to recall which tool it was originally installed into. MemDock was built to pull such memories and Skills, scattered across different locations, into a single workbench, and is offered in macOS and Windows builds.
According to the post, MemDock's "Memory Overview" lets users search CLAUDE.md, AGENTS.md and Claude Code's automatic memories globally or per project, as well as browse Codex's read-only memory store. Rule files support side-by-side editing and version rollback, and a project memory graph reveals how a rule is connected and jumps back to its source. For cases where the assistant was corrected in conversation but the rule file was never updated, MemDock extracts candidates worth adding and rules worth revising from recent conversations, on a weekly, daily-scheduled or manual basis. Extractions land first in "Pending Memories", where users review the old content, the new suggestion and the original dialogue before choosing to adopt, adopt with edits or discard, and only adopted items are written back to files. The "Skill Management" section lists Skills installed in Claude Code and Codex and supports copying them across the two tools; MemDock additionally provides bidirectional session conversion between them. As of now, no other accounts of MemDock have been published, so the project's status rests on this single announcement.
AI-generated from 1 reports · updated 4 days ago
Latest turnThis guide compares native memory mechanisms in Claude Code with third-party tools like Supermemory, claude-mem, and Lockstep. It helps developers identify missing memory gaps and choose between native auto-memory, project instructions, or external layers.
Related AI tools
- Heat index
- 25
- All sources
- 2
- All reports
- 2
- First seen
- 4 days ago
Reports on this story headlines open the original
This guide compares native memory mechanisms in Claude Code with third-party tools like Supermemory, claude-mem, and Lockstep. It helps developers identify missing memory gaps and choose between native auto-memory, project instructions, or external layers.
DEV Community · AIAI score 72
A developer has open-sourced MemDock, a desktop workbench that centralizes memory and Skill management for Claude Code and Codex. It supports searching and rolling back rule files, extracting memory candidates from recent conversations for review, copying Skills between the two tools, and converting sessions in both directions, with macOS and Windows builds.
V2EXAI score 56
Other stories people are talking about
- Heat index 71Shared memory for Claude Code and Codex: pull it on demand, don't inject it1 sources
- Heat index 98NewDeveloper shares Claude Code context control and subagent model routing1 sources
- Heat index 84Developers Discuss Boundaries and Challenges of Claude Opus 5.5 in Multi-Round Code Reviews1 sources
- Heat index 96NewClaude and Kimi take down a simulated wind farm in test1 sources
- Heat index 73Developer Builds 50-Floor Tower Defense Web Game with Claude1 sources
How is heat calculated?About the methodHide
Heat counts how many independent sources covered a story in the last 48 hours: one source counts once no matter how many posts it published, decaying with a 24-hour half-life. What ranks first is what many people are talking about.
This page aggregates public feeds. Headlines and summaries are machine-organized and remain the property of the original authors; verify important facts at the source. If you believe a headline or summary infringes your rights, email the contact address in the footer with the page URL and basis of your claim, and we will remove or replace it after review.
- Surge
- Discussion rising fast
- New
- First report within 6 hours
- Rising
- Still gathering discussion

