Agent Lightning vs qmd

Agent Lightning is Microsoft's open-source framework for training, fine-tuning, and optimizing AI agents without rewriting your existing code. The core idea: add lightweight emit() calls (or enable auto-tracing) to capture prompts, tool calls, and reward signals as structured spans. Those spans flow into LightningStore, which feeds a pluggable Trainer that can run reinforcement learning, automatic prompt optimization, supervised fine-tuning, or custom algorithms — your choice. What makes it notable is genuine framework agnosticism. Whether your agents are built on LangChain, AutoGen, CrewAI, OpenAI's Agent SDK, or plain Python with OpenAI, Agent Lightning bolts on without architectural changes. You can target specific agents within a multi-agent system and leave others untouched. With 16.8k GitHub stars and a Discord community, Microsoft is positioning this as the training layer that sits beneath whatever orchestration framework developers already use. That's a smart wedge: rather than competing with LangChain or AutoGen for framework mindshare, it becomes the optimization pass that makes all of them better.

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.