Apfel vs Skrun

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.

Skrun is an open-source tool that wraps agentic skills — the discrete, reusable capabilities you build for AI agents (web search, data extraction, file transformation, API calls) — into deployable REST APIs with a single command. The idea is that skills you build for one agent context shouldn't be locked to that agent's runtime. With Skrun, you define a skill once with a standard function signature, and get a hosted endpoint with automatic request validation, retry logic, rate limiting, and an OpenAPI spec generated automatically. The project addresses a real architectural tension in the current AI tools ecosystem: agent skills are written in a dozen different formats (LangChain tools, MCP tools, function call JSON, OpenAI tool specs) and are essentially stranded assets — they only work within their specific orchestration framework. Skrun normalizes this by wrapping any skill definition format and exposing it as a framework-agnostic HTTP endpoint that any agent or pipeline can call. This appeared on Hacker News with a small but thoughtful discussion focused on the "skills as microservices" architectural pattern. Critics noted that adding HTTP round-trips to every tool call introduces latency; proponents argued that the composability and reusability benefits outweigh the cost. The early version focuses on stateless skills; stateful/conversational skill deployment is on the roadmap.