wastedcode/memex

Overview

wastedcode/memex (Pebblebed) is a daemonized wiki runtime written in Go, using Linux mount-namespace isolation and a job queue. It is a Tier 3 specialized implementation in the comprehensive report — infrastructure-grade wiki operation.

Key Facts

• Language: Go (daemon architecture, filesystem isolation)
• Runtime: daemonized wiki with job queue
• Isolation: Linux mount namespaces for safety
• Origin: Pebblebed org (same group that funded Cognee’s seed)

Features

Core Architecture

• Go daemon — always-on wiki runtime service with compiled binary, no runtime dependencies
• Linux mount namespaces — filesystem isolation for safety, each wiki runs in its own namespace
• Job queue — per-wiki async processing with serial writes, parallel wikis
• Three core operations — Ingest, Query, Lint (same core as Karpathy’s concept)

Ingest & Processing

• CLI-first — memex serve, memex create, memex ingest, memex query, memex lint
• Multi-format ingest — markdown, PDFs, HTML, images, plain text
• Async jobs — --async flag for non-blocking operations
• OAuth login — memex login <wiki> authenticates Claude

Search & Retrieval

• Query — searches wiki, answers with citations

Quality & Governance

• Filesystem isolation — mount namespaces prevent cross-contamination
• Audit log — memex logs <wiki> tracks all operations
• Tool whitelist — .tools/allowed-tools.txt controls what Claude can do
• Wiki conventions — .claude.md extends system prompt with domain-specific behavior

MCP / Tools

• MCP server integration — Notion, Google Drive, any app with API via .tools/mcp.json
• Model config — memex config <wiki> --model opus

Integration

• Agent-driven — Claude Code or other agents drive the job queue
• CLI interface — command-line control of the daemon

Data & Storage

• No vector DB — pure markdown files, no embeddings
• File-based — wiki content as markdown files
• Job queue — persistent queue for processing history

Relationships

• llm-wiki — (type: belongs-to) daemonized, always-on implementation
• agent-memory-systems — (type: belongs-to) runtime memory service
• cognee — (type: sibling-of) Pebblebed-adjacent; Cognee is the graph engine, memex is the runtime
• claude-code — (type: operates-with) agent drives the job queue

Implications

wastedcode/memex represents the “wiki as a long-running service” end of the spectrum — opposite of this vault’s static-file approach, but relevant for the user’s automation goal (always-on ingest).

External Links

• Repository: https://github.com/wastedcode/memex

Não confunda com

Este projeto compartilha o nome “memex” com outros dois do ecossistema, mas são coisas diferentes:

• ai-memex-cli — é uma CLI dual-vault com destilação de sessão, não um daemon.
• memex-zero-rag — foca em zero-hallucination/quarantena, não em runtime isolado em Go.

Sources