AI tool comparison
Apfel vs Kontext CLI
Which one should you ship with? Here is the side-by-side panel verdict, pricing read, reviewer split, and community vote comparison.
Developer Tools
Apfel
Tap the free AI already built into your Mac
75%
Panel ship
—
Community
Free
Entry
Apfel is a Swift 6.3 command-line tool that cracks open the on-device language model Apple ships with every Apple Silicon Mac running macOS 26 (Tahoe). Instead of requiring a Claude, OpenAI, or Gemini subscription, Apfel routes through Apple's FoundationModels framework and gives you three interfaces from a single brew install: a pipe-friendly CLI, an interactive chat with context management, and an OpenAI-compatible local HTTP server built on Hummingbird. Under the hood, every token is generated on your Neural Engine and GPU — nothing leaves your machine. The model is roughly 3B parameters with a 4,096-token context window, fast enough for scripting, summarisation, and quick Q&A without latency you'd notice. Pipe-friendly stdin/stdout, JSON output mode, and proper exit codes make it trivially composable with jq, xargs, and shell scripts. The OpenAI-compatible server mode is the killer feature for developers: point any tool that speaks the OpenAI API at localhost and it just works — locally, for free, with zero cold-start. The project is MIT-licensed, started by a solo developer on March 24, 2026, and hit 513 HN points within days of the Show HN post.
Developer Tools / Security
Kontext CLI
Stop giving your AI agent long-lived API keys — ephemeral credentials that expire on session end
50%
Panel ship
—
Community
Free
Entry
Kontext CLI is a Go binary that wraps AI coding agents — currently Claude Code — with enterprise-grade credential management. Instead of storing long-lived API keys in .env files your agent can read and potentially leak, you declare what credentials your project needs in a .env.kontext file using placeholders like {{kontext:github}}. When you run 'kontext start', it authenticates via OIDC, exchanges placeholders for short-lived scoped tokens via RFC 8693 token exchange, injects them into the agent's environment, and streams every tool call to an audit dashboard. When the session ends, credentials expire automatically. The .env.kontext file is safe to commit — no secrets, just declarations. Written in Go with zero runtime dependencies. Solves a real but underappreciated security gap: AI agents with access to long-lived credentials are high-value targets for prompt injection and confused deputy attacks.
Reviewer scorecard
“The OpenAI-compatible server is a genuine unlock — I swapped my local dev config from Ollama to Apfel in two minutes and everything just worked. For Apple Silicon owners who want zero-latency local AI without model downloads, this is the move.”
“The credential problem with AI agents is real and underappreciated. When your agent has a GitHub token, Stripe key, and database connection in its environment, a single prompt injection can exfiltrate all of them. Kontext's ephemeral model — short-lived, scoped, auto-expired — is exactly how this should work. MIT license, native Go binary, no Docker required.”
“A 3B-parameter model with a 4K context window is impressive for on-device, but it's nowhere near Claude or GPT-5.5 quality. If your task needs real reasoning or long context, you're back to paying for API credits anyway. This is a neat party trick, not a replacement.”
“The OIDC approach introduces a dependency that has to be up and authenticated for your agent to start at all. The threat model — your agent leaking long-lived keys — is real but theoretical for most solo developers. Prompt injection attacks that exfiltrate .env files are possible but not common in practice yet. For indie builders, you're adding complexity to a problem you probably don't have.”
“Apfel is the first glimpse of a world where capable on-device AI comes pre-installed, not downloaded. As Apple's model improves with each macOS release, tools like Apfel will inherit the upgrade for free. The distribution moat Apple is quietly building here is enormous.”
“As coding agents get more autonomous — running overnight, spawning sub-agents, executing across multiple services — the credential model needs to evolve. Kontext is early infrastructure for what will eventually be mandatory: agent-scoped, time-bounded access. The .env.kontext file being safely committable to the repo is the real unlock for teams sharing configurations without sharing secrets.”
“I used it to batch-summarise 40 draft posts overnight with a simple shell loop — no API bill, no rate limits, no internet required. For content workflows that need a cheap first pass, it's already practical.”
“A developer security tool requiring understanding of OIDC, token exchange, and system keyring storage to use correctly. It's solving a real problem, but not one most creators encounter. The README will feel overwhelming if you're not a security engineer. The payoff is real, but so is the setup cost.”
Weekly AI Tool Verdicts
Get the next comparison in your inbox
New AI tools ship daily. We compare them before you waste an afternoon.