Claude Desktop Buddy vs qmd

Claude Desktop Buddy is a lightweight software layer that exposes a Bluetooth Low Energy (BLE) API from the Claude desktop application, allowing makers and hardware developers to connect physical microcontrollers — like the ESP32 — directly to Claude. This means a device can react to Claude's state, surface permission prompts on physical buttons, display response status on small screens, or trigger real-world actions based on AI outputs. The project is aimed squarely at the maker community: developers building ambient computing prototypes, interactive art installations, or hardware-augmented AI interfaces. Instead of Claude being confined to a screen, Buddy turns it into a node that can communicate bidirectionally with the physical world. The BLE bridge is low-latency enough for interactive use and requires no cloud API key — it runs through the existing Claude desktop session. Built by an indie developer and launched on Product Hunt today, Claude Desktop Buddy is free and open-source. It's a small but creative use of Claude's desktop extension capabilities, and fills a gap that official Claude tooling doesn't touch: physical-world integration for hobbyists.

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.