Topic

Daemon and Process Architecture

Design choices about whether software runs as a per-client subprocess or as a single long-lived shared daemon, and the resource, concurrency and failure consequences of each.

Current clusters

build1 publisher

Registering an MCP server over stdio hands every agent session its own lock

The per-session spawn is what stdio means, so the fix is one loopback daemon per machine. That same consolidation makes a single restart blind every open session, which is where the design work went.

Publishers:dev.to

Reality

Evidence52
Adoption14
Hype gap−18
Incentives30
Confidence55