Skip to content

ServerFS v0.24.1

Choose a tag to compare

@github-actions github-actions released this 07 Nov 01:54
bac14a4

ServerFS v0.24.1 — Native macOS Cloudflare Tunnel

Native macOS Cloudflare Tunnel

v0.24.1 adds an optional native Cloudflare Tunnel ingress for Apple Silicon Macs running macOS 27.x. A dedicated HTTP origin binds to loopback, and a cloudflared Connector connects to an operator-configured remotely managed Tunnel. Bootstrap verifies the pinned official macOS arm64 artifact. The origin enforces the exact configured public Host and independent ServerFS API Key or OAuth caller authentication; the Tunnel Token authenticates only the Connector.

The Connector Token and HTTP-origin environment source are current-user files with mode 0600, stored outside the checkout and every configured workdir. The origin and Connector use the same app-associated SMAppService LaunchAgent mechanism as the existing OpenAI Tunnel and Agent Bridge. This is Login Items architecture parity; no logout/login or whole-machine reboot was performed.

The existing OpenAI Secure MCP Tunnel, Agent Bridge, and Linux Docker Cloudflare ingress shipped in v0.24.0 remain available. Native Windows Cloudflare remains planned for v0.24.2. ServerFS does not provision Cloudflare Tunnels or DNS routes. See the macOS native deployment runbook for CLI syntax, service lifecycle, staging, rollback, and operator acceptance.

Recorded macOS staging evidence

On the supported macOS 27 Apple Silicon staging host, isolated read-only staging produced the following results:

  • Public HTTPS returned 401 without caller authentication and 200 with the configured identity.
  • MCP discovery exposed 11 tools. A fixture read succeeded; write attempts, traversal, absolute paths, and hidden paths were rejected.
  • A persistent SSE connection remained usable for 65.1 seconds with keepalives.
  • After a controlled Connector-only restart, the prior session returned 404; a new session recovered successfully in 8/8 checks. This does not demonstrate old-session continuity or replay of SSE events in flight.
  • Cloudflare and HTTP-origin services reached enabled state. Local stop/start and service persistence succeeded. Existing OpenAI Tunnel and Agent Bridge remained undisturbed.
  • Source and contract review found the same SMAppService.agent(plistName:), app-owned ServiceLauncher, and LaunchAgent restart policy as the accepted native services. This is architecture review, not an actual logout/login or reboot test.

These results describe isolated, read-only staging only. They do not establish production workdir, Agent, or Repo Ops acceptance. The operator's sanitized evidence is private and is not reproduced here; this note contains no user-specific hostname, username, IP address, Token, or credential.

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.1-py3-none-any.whl ServerFS env ec70e8d5bc1ea3f703f418e05eeae753849ebf54d069a74a0ed38037f428cc39
serverfs_windows_native-0.24.1-cp312-abi3-win_amd64.whl ServerFS env 2534256e047c703ba2b2a7d8ffe3575042a46543c21a3e0aa8ca5d418438a2e3
serverfs_agent_bridge-0.24.1-py3-none-any.whl Agent Bridge env f12c08b1bb9708596d3e1e8bf7158ea6cd0b4bcb8beb2e935dde6d9c249a6e65

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.1/serverfs_mcp-0.24.1-py3-none-any.whl https://github.com/NTLx/ServerFS_MCP/releases/download/v0.24.1/serverfs_windows_native-0.24.1-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.1/serverfs_agent_bridge-0.24.1-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.1/serverfs_windows_native-0.24.1-cp312-abi3-win_amd64.whl" --sha256 2534256e047c703ba2b2a7d8ffe3575042a46543c21a3e0aa8ca5d418438a2e3