Repository navigation
ServerFS v0.21.0
ServerFS v0.21.0 — Operational Maturity
ServerFS v0.21.0 adds a shared, secret-safe operational observation contract and an opt-in common status view for supported native macOS and Windows deployments.
What’s new
- On supported macOS and Windows deployments,
serverfs service status --format common-jsonand--format common-humanshow the common status projection. The default native status output is unchanged. Linux does not gain a native service lifecycle or native status projection. - Agent Bridge now records bounded, process-local observations for task outcomes and durations, queue depth and wait, writer-lease contention, and recovery outcomes. Labels use finite categories: task IDs, secrets, paths, prompts, provider values, and other high-cardinality data are excluded. These observations reset when the Bridge restarts and are not authoritative over durable task or recovery state; recording failures do not override durable transitions.
- The Phase D Linux/VPS performance gate passed: submit-call p95 median was 21.409 ms, within the 22.424 ms budget; startup and idle RSS deltas were 0 KiB.
- v0.21.0 ships without a Prometheus or OpenTelemetry exporter, listener, telemetry egress, or background collector.
Compatibility and scope
This release adds no data, configuration, or schema migration and grants no new authority. Existing MCP capabilities, authentication, and service lifecycle boundaries remain in place.
Supported deployment families remain Linux (amd64 and arm64), Windows 11 x64, and Apple M-series macOS on native arm64 with macOS 27. The release does not add MCP Tasks, ACP v2, a new Agent runtime or authentication provider, A2A, AG-UI, MCP Apps, or a generic shell/exec capability.
Upgrade
Upgrade from v0.20.0 using the deployment procedure for your platform. No v0.21.0 data or configuration migration is required.
Artifacts
Release artifacts include the Linux container image, Windows product and Agent Bridge distributions with the native kernel wheel, and the portable Agent Plugin. Windows wheel and checksum details follow below.
Windows installation assets (Python >= 3.12; no Rust/MSVC/Docker required)
The three release wheels install into two isolated environments, matching the
frozen ServerFS/Agent-Bridge process boundary (the supervisor selects the Bridge
interpreter through SERVERFS_BRIDGE_PYTHON; the packages never share one dependency
graph):
| file | installs into | sha256 |
|---|---|---|
| serverfs_mcp-0.21.0-py3-none-any.whl | ServerFS env | 28e2dc4f2b135be3c07ed87b078566e205b7f3e27622533022993b5ab062b03c |
| serverfs_windows_native-0.21.0-cp312-abi3-win_amd64.whl | ServerFS env | 6f634d5943ccd3a1e8e94d3f908ada8f0eeece7cc379c3610ab51ba85ea4e346 |
| serverfs_agent_bridge-0.21.0-py3-none-any.whl | Agent Bridge env | 01f21320964e2207f1d7d1326a459acda4efb877a1348ea0afc2ad22207ed848 |
ServerFS environment (product + native kernel):
uv venv --python 3.12 .venv-serverfs
uv pip install --python .venv-serverfs/Scripts/python.exe https://github.com/NTLx/ServerFS_MCP/releases/download/v0.21.0/serverfs_mcp-0.21.0-py3-none-any.whl https://github.com/NTLx/ServerFS_MCP/releases/download/v0.21.0/serverfs_windows_native-0.21.0-cp312-abi3-win_amd64.whl
Agent Bridge environment (Bridge + provider SDKs; it must NOT contain the product):
uv venv --python 3.12 .venv-bridge
uv pip install --python .venv-bridge/Scripts/python.exe https://github.com/NTLx/ServerFS_MCP/releases/download/v0.21.0/serverfs_agent_bridge-0.21.0-py3-none-any.whl
Point the ServerFS supervisor at the Bridge interpreter (set this in the environment
that starts serverfs supervisor; it is not a provider setting and does not belong in
[agent] config):
$env:SERVERFS_BRIDGE_PYTHON = "<path>\.venv-bridge\Scripts\python.exe"
Verified native-wheel storage alternative:
serverfs bootstrap native-wheel --url "https://github.com/NTLx/ServerFS_MCP/releases/download/v0.21.0/serverfs_windows_native-0.21.0-cp312-abi3-win_amd64.whl" --sha256 6f634d5943ccd3a1e8e94d3f908ada8f0eeece7cc379c3610ab51ba85ea4e346