pi-autoresearch vs qmd

pi-autoresearch extends the pi terminal agent with an autonomous optimization loop: the agent writes a change, runs a benchmark, uses Median Absolute Deviation (MAD) to filter out statistical noise, and either commits or reverts — then loops. No human in the loop. The cycle repeats until a time limit or convergence criterion is met. The technique was popularized by Karpathy's autoresearch concept for ML training, but pi-autoresearch generalizes it to any benchmarkable target. Shopify's engineering team ran it against their Liquid template engine and reported 53% faster parse/render with 61% fewer allocations after an overnight run — changes their team had been unable to land manually in months. The MAD-based noise filtering is the key innovation: it prevents the agent from chasing benchmark noise and reverting valid improvements. The project has spawned an ecosystem: pi-autoresearch-studio adds a visual timeline of accepted/rejected edits, openclaw-autoresearch ports the concept to Claw Code, and autoloop generalizes it to any agent that supports a run/test interface. At 3,500 stars, it's one of the most-forked pi extensions.

qmd is a lightweight local search engine built by Tobi Luetke, CEO of Shopify, for indexing and querying personal knowledge bases, documentation, and meeting notes — entirely offline. It combines three retrieval approaches in a single pipeline: BM25 full-text search for exact keyword matches, vector semantic search via ONNX-based embeddings, and LLM re-ranking using GGUF models through node-llama-cpp. All three stages run locally with no cloud dependency. The tool ships in multiple deployment modes: a CLI for ad-hoc queries, a Node.js library for programmatic use, an HTTP service for local API access, and — most useful for AI workflows — a native MCP server that lets Claude Code, Cursor, and similar editors query your local knowledge base directly during coding sessions. The hybrid retrieval approach means it handles both "find the exact error message from last week's standup notes" and "what was our decision about the auth architecture" equally well. What makes this notable beyond its technical approach is provenance: Luetke shipped it as a personal tool he actually uses, not a startup product. The GitHub history shows active iteration and he's been talking about it on X. It's a credible signal of where pragmatic AI-augmented knowledge management is heading for technical users who prefer local-first tools.