Reported issues for memex by pragneshbagary
Pod holds 7 of 7 GitHub reports that passed its relevance review. This can include external user reports, maintainer-confirmed bugs, and concrete feature gaps. Treat them as evidence to inspect, not a count of distinct defects.
Back to memex by pragneshbagary.
Most discussed
Migrate to mcp 2.x and drop the <2.0 pin
memex/server.py is built on FastMCP, which mcp 2.0.0 removed. #39 capped the dependency at mcp>=1.0,<2.0 so installs would work again, but that holds the project on 1.x, and 1.9.4 is the end of that line.
Upstream this looks like a rename rather than a redesign: mcp.server.fastmcp became mcp.server.mcpserver, and FastMCP became MCPServer. Python floor is still 3.10, so the support matrix does not move.
Worth deciding as part of the work: whether to jump straight to mcp>=2.0 or
Read the thread · 2026-08-03 · open · 0 comments
docs: README has stale references and missing CLI flags
Issues
Stale content
- Line 97 references
.claude/memex.mdbut install now writes to.claude/CLAUDE.local.md(changed in #32)
Missing content
memex listsection does not document the--sinceand--untildate filtering flagsmemex version/--versionflag is not mentionedmcp-name: memextag required for MCP registry listing is not present
Read the thread · 2026-06-25 · closed · 0 comments
fix(install): .claude/memex.md is not auto-loaded by Claude Code
Bug
memex install writes instructions to .claude/memex.md, but Claude Code does not automatically load this file. Only the following locations are recognised:
CLAUDE.md/CLAUDE.local.md(project root).claude/CLAUDE.md/.claude/CLAUDE.local.md.claude/rules/*.md
This means the memex instructions are silently ignored — Claude never sees them.
Fix
Change install() to write to .claude/CLAUDE.local.md instead. This file is:
- Auto-loaded by Claude Code ✓
- Person
Read the thread · 2026-06-23 · closed · 0 comments
Pinned entries: always load certain memories regardless of recency
Add the ability to pin a memory entry so it always appears in mem_load regardless of recency or keyword relevance. Useful for permanent warnings like Redis must be running or project conventions you never want Claude to forget.
Implementation:
- Add a pinned boolean column to the entries table with a migration for existing DBs (follow the gotchas to warnings migration pattern already in init_db() in memex/server.py)
- Add mem_pin(entry_id) and mem_unpin(entry_id) MCP tools in memex/server.py
Read the thread · 2026-06-18 · open · 0 comments
Add mem_update MCP tool — edit entries without losing id or timestamp
Currently correcting a memory entry requires mem_delete + mem_save, which changes the entry's id and loses its original timestamp.
A mem_update(entry_id, ...) tool that patches only the fields you supply in-place would fix this — untouched fields, the original id, and the original timestamp are all preserved.
Read the thread · 2026-06-18 · closed · 0 comments
Add Cursor support
Cursor supports MCP but uses a different config file path than Claude Code.
memex install --cursor should write the MCP server entry to Cursor's config location so Cursor users can use memex without manual setup.
Read the thread · 2026-06-15 · open · 0 comments
Auto-save at session end via Claude Code hooks
Right now Claude has to be told to call `mem_save`, either by the user or by the CLAUDE.md instructions. It's easy to forget.
Claude Code supports hooks that fire at specific session events — including when the session stops. A hook that automatically triggers `mem_save` at session end would mean zero manual effort.
Proposed behaviour
- `memex install` writes a `stop` hook to `.claude/settings.json` alongside the MCP entry
Read the thread · 2026-06-15 · closed · 0 comments
Most recent
The remaining reports are on the project's issue tracker.