Show HN: Mex 0.8.0 – team memory for coding agents Mex 0.8.0, an open-source tool for team memory in coding agents, introduces a setup command that prepares a code graph and wiki, installs official Claude Code and Codex skills, and protects local stores from Git. The tool uses Tree-sitter and SQLite to build a deterministic code graph indexing symbols across TypeScript, TSX, JavaScript, JSX, Python, and Rust, enabling agents to document knowledge in Markdown and route context by task. A living wiki for your codebase, maintained by your AI coding agents. English | 简体中文 /mex-memory/mex/blob/main/README.zh-CN.md | Español /mex-memory/mex/blob/main/README.es.md | Português Brasil /mex-memory/mex/blob/main/README.pt-BR.md mex maps your code, turns what agents learn into structured Markdown, and keeps that knowledge connected to the implementation it describes. Every coding session starts with relevant architectural context instead of another full-repository scan. New in v0.8.0: mex setup now prepares the Graph and Wiki end to end, installs the official Claude Code and Codex skills, protects local stores from Git, and automatically launches the first available agent you selected. 💬 Join the mex community on Discord — discuss ideas, get help, share feedback, and contribute to the project. npx mex-agent setup Architecture, conventions, edge cases, and past decisions are scattered across source code, pull requests, chat histories, and individual contributors. AI coding agents rediscover that knowledge every session. A giant instruction file helps at first, but eventually floods the context window, becomes stale, and drifts away from the implementation. mex creates a living, repo-local wiki that grows as agents work: - agents document what they learn in readable Markdown - a deterministic code graph connects that knowledge to exact symbols - task-aware routing loads only the context needed for the current job - drift checks identify knowledge affected by code changes - completed work adds decisions, patterns, and current project state back into the wiki The code remains the source of truth. The wiki becomes its maintained explanation. | Ordinary project documentation | The mex living wiki | |---|---| | Written once and gradually forgotten | Grows from real coding work | | Disconnected from the implementation | Claims can point to exact code symbols | | Loaded as one giant instruction file | Context is routed by task | | Refactors silently invalidate docs | Changed, moved, and missing symbols are detected | | Every agent rediscovers the architecture | Agents inherit previous discoveries and decisions | | Knowledge disappears between sessions | Decisions and reusable patterns persist in the repository | mex builds a deterministic local code graph using Tree-sitter and SQLite. It indexes symbols and relationships across TypeScript, TSX, JavaScript, JSX, Python, and Rust, including framework-aware Express route-to-handler relationships. mex graph rebuild Graph reads never rebuild implicitly. Use mex graph status for a read-only freshness check, mex graph refresh to explicitly republish a compatible index, and mex graph rebuild for an isolated full rebuild. The legacy bare mex graph command remains a safe rebuild alias. During setup, your coding agent uses the graph to understand the project and populate a structured Markdown wiki: .mex/ ├── AGENTS.md ├── ROUTER.md ├── context/ │ ├── architecture.md │ ├── stack.md │ ├── setup.md │ ├── decisions.md │ └── conventions.md ├── patterns/ │ ├── INDEX.md │ └── ... └── events/ └── decisions.jsonl These remain ordinary Markdown files: readable, reviewable, version-controlled, and editable by humans or agents. Agents begin with a small anchor file instead of loading the entire wiki. The anchor points to ROUTER.md , which selects the architecture notes, decisions, conventions, and task patterns relevant to the current job. Agent task ↓ Small always-loaded anchor ↓ ROUTER.md ↓ Relevant wiki pages ↓ Compact code-graph neighborhood ↓ Targeted source expansion Editable source: docs/diagrams/context-routing.excalidraw /mex-memory/mex/blob/main/docs/diagrams/context-routing.excalidraw After meaningful work, the agent updates project state, records decisions, and captures reusable patterns. mex checks that the wiki still agrees with the repository: mex check mex sync mex check validates paths, commands, dependencies, links, indexes, staleness, tool configuration, and grounded code symbols without spending AI tokens. When repairs are needed, mex sync gives the agent targeted context instead of asking it to rediscover the whole project. Editable source: docs/diagrams/drift-sync.excalidraw /mex-memory/mex/blob/main/docs/diagrams/drift-sync.excalidraw Wiki pages can connect important claims to exact graph nodes. A behavioral claim can be grounded through frontmatter: --- grounds to: - node: "function:a3f8...c21" fingerprint: "mh:64:9f2a..." --- Load-bearing symbol references can also be navigable inline: Authentication is enforced by requireSession mex://function:a3f8...c21 . When that function changes, moves, or disappears, mex can identify the affected knowledge. Confident renames and moves are durably rebound during sync; ambiguous changes are surfaced for the agent to resolve. This lets agents read broadly to understand a behavior while grounding only the few symbols that actually support what they write. The graph is also a compact agent-retrieval layer: mex graph scope "trace the authentication flow" Instead of returning a repository-sized source dump, mex prioritizes the declarations and real execution flows most likely to answer the task under a hard estimated-token budget. The default response is source-backed and uses deterministic meta , source , flow , and summary JSONL records. Returned source is already read. When the summary is ok , an agent can answer directly even if lower-priority optional context was truncated. Exact expansion remains available when a declaration is missing or the summary recommends a follow-up: mex graph get