Apfel vs qmd

Apfel is a Swift CLI that does something Apple didn't: it exposes the on-device LLM baked into every Apple Intelligence-enabled Mac as a proper OpenAI-compatible local server running at localhost:11434. Any app that speaks to Ollama's API — LM Studio, Continue, OpenWebUI, your own scripts — can now route requests to Apple's FoundationModels framework without modification. The feature set is more complete than most indie wrappers: streaming responses, tool calling with MCP support, file attachments, an interactive chat mode, and a debug SwiftUI GUI for inspecting token flow. Inference is fully on-device with no API keys, no telemetry, and no cost beyond electricity. On an M-series Mac, it runs at native Apple Neural Engine speeds — typically 40-80 tokens/second depending on the model variant active. The catch is real: you need macOS 26 Tahoe (currently in beta) and Apple Intelligence enabled. But for the tens of millions of Apple Silicon Mac users who already qualify or will soon, this is the quiet unlock of a model they already own. The "your Mac already has a free LLM" framing is resonating — the repo hit 3,500 stars in days.

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.