Skip to content

ServerFS v0.24.2

Latest

Choose a tag to compare

@github-actions github-actions released this 10 Nov 06:38

v0.24.2 — Windows-native Cloudflare Tunnel

v0.24.2 adds optional native Windows 11 x64 Cloudflare Tunnel ingress for ServerFS Streamable HTTP. The Windows release uses the existing current-user Task Scheduler 2.0 → watchdog → runner lifecycle and a kill-on-close Job Object for the HTTP Origin and cloudflared Connector generation.

Changes

  • Adds optional Windows Cloudflare ingress while preserving OpenAI Tunnel as the default provider. The accepted deployment runs two independent same-user Task Scheduler owners: OpenAI default and ServerFS Cloudflare WorkPC via service cloudflare-parallel. Each has separate venv/state/watchdog/runner and may share intended writable workdirs and one Agent Bridge/Repo Ops service. The provider guard remains owner-scoped; no universal automatic handover is claimed. Keep the shared Agent Bridge running while Cloudflare depends on it.
  • Adds a pinned official Windows x64 cloudflared 2026.10.7 bootstrap with SHA-256, Authenticode publisher and executable-version checks.
  • Adds fail-closed private Windows credential-file validation for current-user SID/owner, protected DACL, symlink/junction/reparse rejection and locations outside configured workdirs/checkout. The raw Tunnel Token is not passed as an argument; cloudflared uses --token-file.
  • Requires independent ServerFS HTTP API Key or OAuth, an explicit exact public Host allowlist, a 127.0.0.1 bind and anonymous HTTP 401 readiness before Connector startup.
  • Adds provider-specific status/child liveness, crash/recovery handling, Windows native HTTP subprocess acceptance and bilingual operator/site/Agent Skills guidance without changing filesystem policy, Repo Ops or Agent Bridge authority.

Acceptance evidence

  • Two independent same-user Task Scheduler owners passed public Cloudflare HTTPS 401/200, ChatGPT tool calls and cross-ingress read/write/edit/delete on shared writable workdirs. Codex and Claude passed through the accepted setup.
  • Three authenticated public SSE holds lasted 75.0 s, 70.0 s and 65.0 s, with approximately 15-second keepalives. Subsequent same-session tools/list returned 200 with 27 tools; a new session returned 200. This does not establish restart behavior or guarantee same-session survival or replay.
  • Five ordinary CI results passed on df08fadd: Windows Native, Windows Agent, Linux Container, macOS Native and Pages. These results are not the exact-SHA release workflow gates for the final release commit.
  • Prior independent-instance lifecycle acceptance included runner recovery. It is not evidence of v0.24.2 full-generation recovery after Connector failure.
  • Operator release waiver on 2026-11-10: no restart/recovery test was required for this release. The Windows full-generation restart/recovery test was NOT tested and did NOT pass. Connector-only restart behavior is unverified. This waiver is recorded as a release decision, not as a test result.

Compatibility and limitations

  • Linux Docker Cloudflare Tunnel shipped in v0.24.0. Native Apple Silicon/macOS 27 Cloudflare Tunnel shipped in v0.24.1 using the existing app-associated SMAppService/LaunchAgent lifecycle.
  • Windows requires a user-level, version-matched serverfs-mcp and serverfs-windows-native installation, current-user-private Tunnel Token and HTTP Origin environment files, and a separately managed Cloudflare hostname/tunnel.
  • Qoder's provider error predated this acceptance. Python urllib's default User-Agent received Cloudflare edge WAF 1010; this is an edge configuration caveat.
  • No lossless SSE replay is supported or claimed. No Connector-only restart pass, full-generation restart/recovery pass, Windows sign-out/reboot result, or broader production workdir/Agent acceptance is claimed.

See the Windows Cloudflare runbook, release checklist, and v0.24.2 development plan.

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.24.2-py3-none-any.whl ServerFS env 0314c6c1f092a1d73a7cdc3380c6b3381dda8a16c3080877bb0c2370dcfe7ae8
serverfs_windows_native-0.24.2-cp312-abi3-win_amd64.whl ServerFS env 99e3a706c6bc2dd76a624f23a8ba3b67ff5b35a65e81f29e770e3f8a25f6e7d9
serverfs_agent_bridge-0.24.2-py3-none-any.whl Agent Bridge env 3b93e81fb7435c80c4426fd3afe40fae4b8a85fa1cd208ac8ad1347b4b771bf3

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.24.2/serverfs_mcp-0.24.2-py3-none-any.whl https://github.com/NTLx/ServerFS_MCP/releases/download/v0.24.2/serverfs_windows_native-0.24.2-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.24.2/serverfs_agent_bridge-0.24.2-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.24.2/serverfs_windows_native-0.24.2-cp312-abi3-win_amd64.whl" --sha256 99e3a706c6bc2dd76a624f23a8ba3b67ff5b35a65e81f29e770e3f8a25f6e7d9