dev-mcps/dev-server-mcp/test
Lucio Lelii 1eedcb8964 Reclaim previews nobody is using any more
Nothing gave an instance back. A flow that ended, or an agent that simply stopped
calling, left its service running and its copy on disk until somebody noticed -
which is how dev-server-instances became the one volume that only ever grows.

Two clocks, because they answer different questions. Idle asks whether anybody
is still looking: a preview request or an MCP call resets it, and running out
stops the process while keeping the copy, so an evaluator who stepped away for a
meeting pays a restart and not a reinstall. The absolute one asks whether this
has been here long enough to be forgotten, and discards everything - the only
thing in the whole stack that hands disk back on its own.

Asking after an instance counts as using it, not only preview traffic. The
browser reaches a running service straight on its port, which the worker never
sees, so an agent mid-loop would otherwise look idle to the clock watching it.

What the sweep reclaimed is logged. A preview that vanishes without a word is
indistinguishable from one that broke, and the person it vanished under has no
way to tell the difference.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
2026-09-24 17:12:05 +02:00
..
dev-server-service.test.js Improve MCP guidance and tool availability 2026-09-23 13:15:39 +02:00
execution-instances.test.js Reclaim previews nobody is using any more 2026-09-24 17:12:05 +02:00
instance-workspace.test.js Bring the three MCP servers together as one deployable stack 2026-09-22 11:45:55 +02:00
pinned-headers.test.js Bring the three MCP servers together as one deployable stack 2026-09-22 11:45:55 +02:00
ports.test.js Bring the three MCP servers together as one deployable stack 2026-09-22 11:45:55 +02:00
preview-proxy.test.js Let a person open the preview an execution is running 2026-09-24 17:00:22 +02:00
streamable-http.test.js Bring the three MCP servers together as one deployable stack 2026-09-22 11:45:55 +02:00