Skip to content

Memex and Codex #151

Description

@smoochy

Heya,

I want to share some experience from my try-outs with memex. In my personal use, I do use github, VSC, Codex Extension in VSC on a Windows computer.

I have memex installed successfully. The MCP is available in the Codex VSC Extension. When interacting with codex, I see the Used Memex when Codex begins to work. So this connection is correct.

I have added this to my AGENTS.md:

## Memex MCP Usage

For every new request anywhere under `D:\Hold\VS Code`, use the Memex MCP
server as the persistent workspace memory when the `mcp__memex__` tools are
available.

- Call `memex_recall` before repo exploration, code changes, debugging,
  planning, or documentation work. Use a focused query when the task mentions a
  specific stack, service, repo, tool, or prior decision; otherwise call it
  without a query to load the index.
- Read relevant cards with `memex_read` before relying on remembered project
  facts. Treat missing cards as "no stored memory", not as evidence that no
  prior decision exists.
- Do not run retro after every assistant response. Run retro only at the end of
  a substantive task when the session produced durable, reusable knowledge, such
  as an architecture decision, corrected assumption, user preference, setup
  gotcha, root cause, operational path, workflow rule, or recurring project
  pattern. Do not write cards for routine command output, obvious facts, or
  transient chat context.
- Before creating a new card, search existing cards with `memex_recall` using
  focused keywords and likely synonyms. Read likely matches with `memex_read`
  and prefer updating, correcting, linking, or superseding an existing card over
  creating a duplicate.
- Use `memex_organize` periodically, and after larger knowledge changes, to
  find orphaned cards, hubs, weakly linked topics, and possible contradictions.
  Archive outdated or superseded cards with `memex_archive`.
- When write/update/retro tools are available, keep card changes atomic and
  theme-aware: choose a short noun-phrase title, a kebab-case slug, a useful
  category, precise tags, and `[[wikilinks]]` to related projects, decisions,
  concepts, and previous cards.
- If the Memex tools are unavailable, state that briefly and continue with the
  best local context instead of pretending memory was checked.

I can also ask Codex to manually create an entry for Memex. This is then being created in the ~.memex\cards folder and is instantly being pushed to my private memex-cards GH repo.

But, during conversations, or at the end, memex never proactively adds any card. Even though it ran into a blocker in the 1st iteration of a workflow and only managed to solve it in the 2nd iteration. So I would assume the learnings should be kept. But this is not the case.

If I ask Codex why it didn't pro-actively add a memex card it only apooligzes that it should have done it and of course it is something useful to keep.

So I am a bit puzzled what else I could try.

Kind Regards,
smoo

Metadata

Metadata

Assignees

No one assigned

    Labels

    questionFurther information is requested

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions