Open-source maintainer publicly corrects confident but flawed isolation advice within a day

A developer maintaining safari-mcp, an MCP server for AI agents on macOS, gave a user technically accurate but contextually wrong advice about session isolation across multiple agents. The maintainer confidently recommended HTTP transport as the solution for preventing agents from interfering with each other's browser tabs, crediting his own per-session isolation mechanism. However, the user pointed out within a day that the real problem lay one layer upstream — in how mcporter, their agent runner, handles MCP clients — making the transport choice irrelevant. Because mcporter either reuses a single client for all agents or creates a stateless new one per call, the maintainer's per-session isolation never engaged in either scenario. The maintainer acknowledged the error publicly, noting the core failure was verifying his own layer thoroughly while silently assuming conditions in an adjacent layer that he had never actually checked.