AI Subscriptions Are Becoming Portable

OpenAgentd is a self-hosted AI-agent OS that runs entirely on the user’s machine. It provides a web cockpit, streaming chat, persistent editable memory, tool use, workspace file browsing, image viewing, local voice transcription, scheduling and multi-agent teams with lead-worker delegation. Agents can read and write files, run shell commands, search the web, generate media, manage todos and extend capabilities via skills or MCP servers. The tool is for users who want a local, inspectable alternative to cloud-only agent workspaces. It is notable now because privacy, long-running autonomy and multi-agent coordination are converging into desktop systems rather than isolated chat tabs.

pi-hosts is an MCP-style utility that gives the Pi coding agent structured, safer access to servers through named SSH targets. Instead of forcing an agent to rediscover hostnames, SSH syntax, OS details, package managers, service managers, or Docker status each time, pi-hosts exposes typed host tools with target resolution, cached facts, command risk checks, connection reuse, and JSONL audit logs. It is built for developers and operators who already use Pi for coding or infrastructure assistance and want remote server workflows to be faster, more repeatable, and easier to inspect. The recent Show HN launch makes it relevant to the growing ecosystem of agent-specific infrastructure tools around SSH, operations, and guarded execution.

Selvedge is a local MCP server that captures why AI agents change code, creating long-term memory for AI-coded codebases. Its official site describes an agent-callable system for Claude Code, Cursor and Copilot that logs reasoning into a SQLite file under a project-local .selvedge directory. That is valuable for teams using AI coding assistants because the final diff often shows what changed but not why the agent chose that path, rejected alternatives, or followed certain assumptions. Selvedge helps preserve design rationale, auditability and handoff context inside the repository workflow. It is notable now because agent-generated code is becoming common enough that codebases need memory for decisions, not just commits and comments.