A Karpathy-style LLM wiki your agents maintain
CLI ToolFreeI shipped a wiki layer for AI agents that uses markdown + git as the source of truth, with a bleve (BM25) + SQLite index on top. No vector or graph db yet.It runs locally in ~/.wuphf/wiki/ and you can git clone it out if you want to take your knowledge with you.The shape is the one Ka
Capabilities6 decomposed
agent-maintained markdown wiki with git-backed persistence
Medium confidenceEnables AI agents to autonomously read, write, and update markdown documents stored in a git repository, with automatic commit tracking and version history. Agents interact with wiki content through a CLI interface that abstracts git operations, allowing them to append notes, create new pages, and maintain structured knowledge without direct git command execution. The system treats the git repository as a distributed knowledge store that persists agent learnings across sessions.
Uses git as the underlying persistence layer for agent knowledge, enabling version control and distributed collaboration without requiring a separate database. Agents interact through a CLI abstraction that hides git complexity while preserving full commit history and rollback capability.
Simpler than vector-database RAG systems for agent memory because it leverages existing git infrastructure and produces human-readable, auditable knowledge artifacts instead of opaque embeddings.
cli-based wiki read/write operations for agents
Medium confidenceProvides a command-line interface that agents can invoke to perform wiki operations (read page, append content, create new page, list pages) without directly manipulating git or markdown files. The CLI abstracts file I/O and git operations into simple commands, allowing agents to treat the wiki as a queryable knowledge store. Commands likely include patterns like `wiki read <page>`, `wiki append <page> <content>`, `wiki create <page> <title>`, enabling agents to integrate wiki operations into their reasoning loops.
Exposes wiki operations as simple CLI commands that agents can invoke via subprocess calls, avoiding the need for agents to understand git or markdown internals. This design prioritizes simplicity and composability over performance.
More accessible than direct API integrations because agents can use standard shell invocation patterns, but slower than in-process library calls due to process overhead.
git-backed version control and commit history for wiki pages
Medium confidenceAutomatically commits wiki changes to git with descriptive commit messages, preserving a full audit trail of agent edits. Each wiki operation (create, append, update) triggers a git commit that captures the change, agent identifier, timestamp, and context. This enables rollback, blame tracking, and historical analysis of how agent knowledge evolved over time. The system likely uses git hooks or post-write commit logic to ensure every meaningful change is persisted to the repository.
Treats git commits as a first-class mechanism for tracking agent knowledge changes, with automatic commit generation on every wiki write. This preserves full provenance and enables historical analysis without requiring a separate audit log system.
More transparent than database-backed audit logs because the entire history is human-readable and can be inspected with standard git tools, but requires git infrastructure and expertise.
markdown-based knowledge representation and formatting
Medium confidenceStores all agent-generated knowledge in markdown format, enabling human-readable documentation that agents can parse and generate. The system leverages markdown's structure (headers, lists, code blocks, links) to organize information hierarchically, allowing agents to append notes to existing sections or create new pages with consistent formatting. Markdown is chosen for its simplicity, version-control friendliness, and compatibility with standard documentation tools.
Uses markdown as the primary knowledge representation format, making agent-generated content directly readable and editable by humans without requiring specialized tools or database access. This design prioritizes transparency and auditability.
More human-friendly than JSON or database records because markdown is widely understood and can be edited in any text editor, but less structured than typed schemas or knowledge graphs.
multi-agent knowledge sharing and collaborative wiki updates
Medium confidenceEnables multiple agents to read from and write to the same wiki repository, allowing them to discover and build upon each other's findings. Agents can reference pages created by other agents, append observations to shared pages, and create new pages that synthesize insights from multiple sources. The git-backed storage ensures that all agents see a consistent view of the wiki (subject to git fetch/pull operations) and that changes are tracked across the agent network.
Leverages git's distributed model to enable agents to share and build upon each other's knowledge without requiring a central coordinator or message broker. Agents interact asynchronously through the shared wiki repository.
Simpler than message-passing or RPC-based agent communication because it uses git as the coordination mechanism, but less real-time than direct agent-to-agent communication.
karpathy-style structured knowledge organization
Medium confidenceOrganizes wiki content following principles inspired by Andrej Karpathy's approach to knowledge documentation — emphasizing clarity, hierarchical structure, and progressive refinement. The system likely uses markdown headers, sections, and cross-references to create a navigable knowledge graph where agents can append findings to existing sections or create new pages that link to related content. This design encourages agents to build cumulative, well-organized knowledge rather than scattered notes.
Applies Karpathy's documentation philosophy to agent-generated knowledge, emphasizing clarity, structure, and progressive refinement. This design treats the wiki as a living document that agents continuously improve rather than a dump of raw findings.
More organized and human-friendly than unstructured agent logs or raw notes, but requires more discipline from agents and may slow down rapid knowledge capture.
Capabilities are decomposed by AI analysis. Each maps to specific user intents and improves with match feedback.
Related Artifactssharing capabilities
Artifacts that share capabilities with A Karpathy-style LLM wiki your agents maintain, ranked by overlap. Discovered automatically through the match graph.
Agent Kernel – Three Markdown files that make any AI agent stateful
Show HN: Agent Kernel – Three Markdown files that make any AI agent stateful
LLM Wiki Compiler Inspired by Karpathy
Show HN: LLM Wiki Compiler Inspired by Karpathy
planning-with-files
Claude Code skill implementing Manus-style persistent markdown planning — the workflow pattern behind the $2B acquisition.
Mintlify
AI documentation platform — markdown to beautiful docs, AI search, API playground, analytics.
@zereight/mcp-gitlab
GitLab MCP server for projects, merge requests, issues, pipelines, wiki, releases, and more
Awesome AI Coding Tools
Curated list of AI-powered developer tools.
Best For
- ✓Teams building long-running AI agents that need persistent memory
- ✓Researchers documenting LLM behavior and decision patterns
- ✓Developers prototyping multi-agent systems with knowledge sharing
- ✓Organizations wanting human-auditable agent reasoning trails
- ✓Developers building CLI-first agent architectures
- ✓Teams using shell-based orchestration or bash scripts to coordinate agents
- ✓Researchers prototyping agent behavior without building custom integrations
- ✓Agents running in containerized or sandboxed environments with CLI access
Known Limitations
- ⚠No built-in conflict resolution for concurrent agent writes to the same wiki page — requires external locking or sequential access patterns
- ⚠Git commit granularity is at the page/document level, not fine-grained diffs of agent edits within a page
- ⚠Markdown-only format limits structured data storage — no native support for schemas or typed knowledge graphs
- ⚠No built-in search or indexing across wiki pages — requires external tools like ripgrep or elasticsearch for semantic search
- ⚠Scaling to thousands of pages may cause git repository bloat and slow clone/fetch operations
- ⚠CLI invocation adds latency per operation (typically 100-500ms per command due to process spawning)
Requirements
Input / Output
UnfragileRank
UnfragileRank is computed from adoption signals, documentation quality, ecosystem connectivity, match graph feedback, and freshness. No artifact can pay for a higher rank.
About
Show HN: A Karpathy-style LLM wiki your agents maintain (Markdown and Git)
Categories
Alternatives to A Karpathy-style LLM wiki your agents maintain
Search the Supabase docs for up-to-date guidance and troubleshoot errors quickly. Manage organizations, projects, databases, and Edge Functions, including migrations, SQL, logs, advisors, keys, and type generation, in one flow. Create and manage development branches to iterate safely, confirm costs
Compare →Are you the builder of A Karpathy-style LLM wiki your agents maintain?
Claim this artifact to get a verified badge, access match analytics, see which intents users search for, and manage your listing.
Get the weekly brief
New tools, rising stars, and what's actually worth your time. No spam.
Data Sources
Looking for something else?
Search →