v0.2.9 - Cross-Platform Preview

v0.2.9 - Managed Tunnel Bootstrap

v0.2.9 removes upstream Secure Tunnel executables from the project repository and release artifacts. Tunnel mode now bootstraps the verified upstream runtime on first use.

Highlights

• No tracked or packaged tunnel-client, tunnel-client-runtime, Cloudflared executable, or Cloudflared manifest.
• First tunnel-mode startup automatically detects Windows/Linux/macOS and amd64/arm64.
• The updater queries the latest official non-prerelease openai/tunnel-client release.
• The selected asset is the official tunnel-client-runtime-cloudflared-vX.Y.Z-<os>-<arch>.zip.
• GitHub asset SHA-256 metadata and upstream SHA256SUMS.txt are both verified before extraction.
• Archive path traversal and symbolic links are rejected.
• The downloaded runtime must report the exact release semantic version before it is published into the managed cache.
• Verified runtime state lives only under .agent_state/tunnel-runtime/.
• A previously verified managed cache can be used when a later update check is offline; a fresh install with no verified cache fails closed.
• Project packaging fails if an upstream tunnel runtime file is accidentally tracked at repository root.

Distribution

Project release archives now contain only the MCP project/controller source and metadata. Tunnel and Cloudflared binaries are acquired directly from the official upstream release for the host platform when tunnel mode is first started.

This substantially reduces the Windows project archive size and prevents stale upstream executables from being redistributed by this project.

Compatibility

The explicit MCP_TUNNEL_CLIENT_BIN override remains available for operators that intentionally manage the runtime themselves. Version pinning, required-update mode, prerelease opt-in, and update interval controls remain supported.

The repository name windows-agent-mcp and MCP server identifier ali_windows_agent_mcp remain unchanged.