Observed arrival · 2026-09-04
ModelSwap: One Plane for Keys and Models
A local-first control plane for switching AI-agent models, managing provider keys, tracking usage, and synchronizing encrypted configuration.
Field notes
The documented workflow combines provider and agent selection with direct edits to files such as config.toml and auth.json, while leaving hooks, statusLine, and MCP configuration untouched. The page also describes a browser-extension flow for creating keys on provider consoles and storing them in an encrypted local vault. Synchronization can use LAN peer-to-peer transport or user-managed storage, with encrypted payloads and one-time migration codes.
Observed signals
Read the marks
Editorial observations of this landing page, not a rating.
One card from the complete issue