v0.1.0-beta.28

xmesh v0.1.0-beta.28 connects selected workspaces to local MCP clients, other devices and cloud agents.

Install and connect

Use the versioned install page to select Windows/macOS and amd64/arm64, download the desktop installer, or copy a version-pinned Agent prompt. Open the installed application, choose purpose/workspace/permissions/clients, review the setup plan and verify a real client request.

This release includes manifest.json with platform, architecture, SHA-256, byte size and verified signing metadata. Download and review install.sh (macOS) or install.ps1 (Windows), then pin this version:

bash install.sh --version v0.1.0-beta.28 --json

.\install.ps1 -Version v0.1.0-beta.28 -Json

Stable releases require Authenticode verification on Windows and a signed, notarized, stapled macOS application. Beta/rc versions belong to the testing channel. Consult each asset's trust entry; explicitly unsigned testing packages require --allow-unsigned / -AllowUnsigned. System security policies and signature checks remain active.

For offline installation, extract xmesh-offline-v0.1.0-beta.28-<os>-<arch>.zip, then use --offline <folder> / -Offline <folder>. The ZIP contains the native package, manifest, scripts and Agent documentation. OS trust verification may require network access or locally cached trust data. Verified downloads remain cached for retries. Bootstrap JSON events identify the phase, package, installed CLI path and recovery action.

The persistent CLI is inside the installed application: macOS xmesh.app/Contents/Resources/bin/xmesh, Windows resources/bin/xmesh.exe. Agent documentation is included in the offline bundle and published as raw Markdown under the versioned install page. Use setup inspect, plan --input, apply --plan, status/resume/verify --job, and doctor --json. Preserve plan/job IDs for recovery. A running service and client verification have separate readiness states.

Verify and validate

Every downloadable file is listed in SHA256SUMS.txt. Match the package hash with the corresponding release record. The signed desktop packages contain the platform CLI; stable Windows/macOS distribution uses these native bundles. Linux CLI archives include the scripts and real-environment runbook.

The release tag must pass the full CI run on the same commit before artifacts are built. This covers Go, contracts, Headscale, Onboarding, UI and the native desktop executor, including native user-service acceptance when the runner has a supported user session. Native installer launch and upgrade acceptance must also be run on target devices; passing build checks alone does not establish those outcomes.

Operational limits

• Windows L2 isolation is unavailable in production. A Windows node configured with agent.policy.isolation: L2 refuses exec and PTY with sandbox.unavailable; runbook step F checks that boundary.
• LAN Agent TCP port 7433 is fixed, so two LAN nodes cannot run on the same host.
• OAuth tokens are held in memory; an ingress restart requires authorization again.
• Cloud connections require a reachable public endpoint, browser authorization and a successful request from the intended client. Setup reports prerequisites and recovery actions when these remain pending.

What's Changed

• webui: add --allowed-origin for reverse-proxy deployments by @tzf1003 in #167
• webui: accept any Origin when no --allowed-origin is set by @tzf1003 in #168
• docs: agent-browser/agent-desktop P0 验证对照表 by @tzf1003 in #169
• computer: switchable agent-desktop engine (P2) with macOS background fallback by @tzf1003 in #170
• gateway: tool surface (unified/compact), tools.call, richer tools.search by @tzf1003 in #171
• 接入 agent-browser 浏览器后端（P1） by @tzf1003 in #172
• gateway: ?surface= override, faster unified list, backend desc and name check by @tzf1003 in #173
• computer: add computer.snapshot / computer.ref_act element tools (agent-desktop) by @tzf1003 in #174

Full Changelog: v0.1.0-beta.27...v0.1.0-beta.28

v0.1.0-beta.27

xmesh v0.1.0-beta.27 connects selected workspaces to local MCP clients, other devices and cloud agents.

Install and connect

Use the versioned install page to select Windows/macOS and amd64/arm64, download the desktop installer, or copy a version-pinned Agent prompt. Open the installed application, choose purpose/workspace/permissions/clients, review the setup plan and verify a real client request.

This release includes manifest.json with platform, architecture, SHA-256, byte size and verified signing metadata. Download and review install.sh (macOS) or install.ps1 (Windows), then pin this version:

bash install.sh --version v0.1.0-beta.27 --json

.\install.ps1 -Version v0.1.0-beta.27 -Json

Stable releases require Authenticode verification on Windows and a signed, notarized, stapled macOS application. Beta/rc versions belong to the testing channel. Consult each asset's trust entry; explicitly unsigned testing packages require --allow-unsigned / -AllowUnsigned. System security policies and signature checks remain active.

For offline installation, extract xmesh-offline-v0.1.0-beta.27-<os>-<arch>.zip, then use --offline <folder> / -Offline <folder>. The ZIP contains the native package, manifest, scripts and Agent documentation. OS trust verification may require network access or locally cached trust data. Verified downloads remain cached for retries. Bootstrap JSON events identify the phase, package, installed CLI path and recovery action.

The persistent CLI is inside the installed application: macOS xmesh.app/Contents/Resources/bin/xmesh, Windows resources/bin/xmesh.exe. Agent documentation is included in the offline bundle and published as raw Markdown under the versioned install page. Use setup inspect, plan --input, apply --plan, status/resume/verify --job, and doctor --json. Preserve plan/job IDs for recovery. A running service and client verification have separate readiness states.

Verify and validate

Every downloadable file is listed in SHA256SUMS.txt. Match the package hash with the corresponding release record. The signed desktop packages contain the platform CLI; stable Windows/macOS distribution uses these native bundles. Linux CLI archives include the scripts and real-environment runbook.

The release tag must pass the full CI run on the same commit before artifacts are built. This covers Go, contracts, Headscale, Onboarding, UI and the native desktop executor, including native user-service acceptance when the runner has a supported user session. Native installer launch and upgrade acceptance must also be run on target devices; passing build checks alone does not establish those outcomes.

Operational limits

• Windows L2 isolation is unavailable in production. A Windows node configured with agent.policy.isolation: L2 refuses exec and PTY with sandbox.unavailable; runbook step F checks that boundary.
• LAN Agent TCP port 7433 is fixed, so two LAN nodes cannot run on the same host.
• OAuth tokens are held in memory; an ingress restart requires authorization again.
• Cloud connections require a reachable public endpoint, browser authorization and a successful request from the intended client. Setup reports prerequisites and recovery actions when these remain pending.

What's Changed

• macOS 后台点击：拆分 input_failed 错误码 by @tzf1003 in #158
• 路径质量测量改造（阶段一） by @tzf1003 in #160
• Fix flaky TestManagerRebalanceMovesCarrierToNewPreferredPath by @tzf1003 in #161
• 新增直连途径 direct（第 3 期） by @tzf1003 in #159
• Fix flaky clean-shutdown and PTY fence tests by @tzf1003 in #163
• 双槽连接模型（第 2 期） by @tzf1003 in #162
• 设备详情显示两条连接与角色标签（双向连接第 4 期） by @tzf1003 in #165
• 加固直连公网端口并更新文档（阶段五） by @tzf1003 in #164
• 直连设置卡片、拓扑连接角色与审计拨出方向（双向连接第 4 期 续） by @tzf1003 in #166

Full Changelog: v0.1.0-beta.26...v0.1.0-beta.27

v0.1.0-beta.26

xmesh v0.1.0-beta.26 connects selected workspaces to local MCP clients, other devices and cloud agents.

Install and connect

Use the versioned install page to select Windows/macOS and amd64/arm64, download the desktop installer, or copy a version-pinned Agent prompt. Open the installed application, choose purpose/workspace/permissions/clients, review the setup plan and verify a real client request.

This release includes manifest.json with platform, architecture, SHA-256, byte size and verified signing metadata. Download and review install.sh (macOS) or install.ps1 (Windows), then pin this version:

bash install.sh --version v0.1.0-beta.26 --json

.\install.ps1 -Version v0.1.0-beta.26 -Json

Stable releases require Authenticode verification on Windows and a signed, notarized, stapled macOS application. Beta/rc versions belong to the testing channel. Consult each asset's trust entry; explicitly unsigned testing packages require --allow-unsigned / -AllowUnsigned. System security policies and signature checks remain active.

For offline installation, extract xmesh-offline-v0.1.0-beta.26-<os>-<arch>.zip, then use --offline <folder> / -Offline <folder>. The ZIP contains the native package, manifest, scripts and Agent documentation. OS trust verification may require network access or locally cached trust data. Verified downloads remain cached for retries. Bootstrap JSON events identify the phase, package, installed CLI path and recovery action.

The persistent CLI is inside the installed application: macOS xmesh.app/Contents/Resources/bin/xmesh, Windows resources/bin/xmesh.exe. Agent documentation is included in the offline bundle and published as raw Markdown under the versioned install page. Use setup inspect, plan --input, apply --plan, status/resume/verify --job, and doctor --json. Preserve plan/job IDs for recovery. A running service and client verification have separate readiness states.

Verify and validate

Every downloadable file is listed in SHA256SUMS.txt. Match the package hash with the corresponding release record. The signed desktop packages contain the platform CLI; stable Windows/macOS distribution uses these native bundles. Linux CLI archives include the scripts and real-environment runbook.

The release tag must pass the full CI run on the same commit before artifacts are built. This covers Go, contracts, Headscale, Onboarding, UI and the native desktop executor, including native user-service acceptance when the runner has a supported user session. Native installer launch and upgrade acceptance must also be run on target devices; passing build checks alone does not establish those outcomes.

Operational limits

• Windows L2 isolation is unavailable in production. A Windows node configured with agent.policy.isolation: L2 refuses exec and PTY with sandbox.unavailable; runbook step F checks that boundary.
• LAN Agent TCP port 7433 is fixed, so two LAN nodes cannot run on the same host.
• OAuth tokens are held in memory; an ingress restart requires authorization again.
• Cloud connections require a reachable public endpoint, browser authorization and a successful request from the intended client. Setup reports prerequisites and recovery actions when these remain pending.

What's Changed

• fix(computer): macOS 目标 App 在前台不再误判为人工介入 by @tzf1003 in #155
• Windows 鼠标移动校验光标落点，避免被吞时误报 executed by @tzf1003 in #156
• 优选 IP 测速按机房与地区筛选（控制接口 2.5） by @tzf1003 in #157

Full Changelog: v0.1.0-beta.25...v0.1.0-beta.26

v0.1.0-beta.25

xmesh v0.1.0-beta.25 connects selected workspaces to local MCP clients, other devices and cloud agents.

Install and connect

Use the versioned install page to select Windows/macOS and amd64/arm64, download the desktop installer, or copy a version-pinned Agent prompt. Open the installed application, choose purpose/workspace/permissions/clients, review the setup plan and verify a real client request.

This release includes manifest.json with platform, architecture, SHA-256, byte size and verified signing metadata. Download and review install.sh (macOS) or install.ps1 (Windows), then pin this version:

bash install.sh --version v0.1.0-beta.25 --json

.\install.ps1 -Version v0.1.0-beta.25 -Json

Stable releases require Authenticode verification on Windows and a signed, notarized, stapled macOS application. Beta/rc versions belong to the testing channel. Consult each asset's trust entry; explicitly unsigned testing packages require --allow-unsigned / -AllowUnsigned. System security policies and signature checks remain active.

For offline installation, extract xmesh-offline-v0.1.0-beta.25-<os>-<arch>.zip, then use --offline <folder> / -Offline <folder>. The ZIP contains the native package, manifest, scripts and Agent documentation. OS trust verification may require network access or locally cached trust data. Verified downloads remain cached for retries. Bootstrap JSON events identify the phase, package, installed CLI path and recovery action.

The persistent CLI is inside the installed application: macOS xmesh.app/Contents/Resources/bin/xmesh, Windows resources/bin/xmesh.exe. Agent documentation is included in the offline bundle and published as raw Markdown under the versioned install page. Use setup inspect, plan --input, apply --plan, status/resume/verify --job, and doctor --json. Preserve plan/job IDs for recovery. A running service and client verification have separate readiness states.

Verify and validate

Every downloadable file is listed in SHA256SUMS.txt. Match the package hash with the corresponding release record. The signed desktop packages contain the platform CLI; stable Windows/macOS distribution uses these native bundles. Linux CLI archives include the scripts and real-environment runbook.

The release tag must pass the full CI run on the same commit before artifacts are built. This covers Go, contracts, Headscale, Onboarding, UI and the native desktop executor, including native user-service acceptance when the runner has a supported user session. Native installer launch and upgrade acceptance must also be run on target devices; passing build checks alone does not establish those outcomes.

Operational limits

• Windows L2 isolation is unavailable in production. A Windows node configured with agent.policy.isolation: L2 refuses exec and PTY with sandbox.unavailable; runbook step F checks that boundary.
• LAN Agent TCP port 7433 is fixed, so two LAN nodes cannot run on the same host.
• OAuth tokens are held in memory; an ingress restart requires authorization again.
• Cloud connections require a reachable public endpoint, browser authorization and a successful request from the intended client. Setup reports prerequisites and recovery actions when these remain pending.

What's Changed

• Cloudflare：支持优选 IP（手动、列表文件、测速优选与导入） by @tzf1003 in #152
• Cloudflare 优选 IP：IP 池、定时测速、按设备策略与前端页面 by @tzf1003 in #154
• 修复拓扑读取 unauthorized，并去掉 Cloudflare 路径的「未知」 by @tzf1003 in #153

Full Changelog: v0.1.0-beta.24...v0.1.0-beta.25

v0.1.0-beta.24

xmesh v0.1.0-beta.24 connects selected workspaces to local MCP clients, other devices and cloud agents.

Install and connect

Use the versioned install page to select Windows/macOS and amd64/arm64, download the desktop installer, or copy a version-pinned Agent prompt. Open the installed application, choose purpose/workspace/permissions/clients, review the setup plan and verify a real client request.

This release includes manifest.json with platform, architecture, SHA-256, byte size and verified signing metadata. Download and review install.sh (macOS) or install.ps1 (Windows), then pin this version:

bash install.sh --version v0.1.0-beta.24 --json

.\install.ps1 -Version v0.1.0-beta.24 -Json

Stable releases require Authenticode verification on Windows and a signed, notarized, stapled macOS application. Beta/rc versions belong to the testing channel. Consult each asset's trust entry; explicitly unsigned testing packages require --allow-unsigned / -AllowUnsigned. System security policies and signature checks remain active.

For offline installation, extract xmesh-offline-v0.1.0-beta.24-<os>-<arch>.zip, then use --offline <folder> / -Offline <folder>. The ZIP contains the native package, manifest, scripts and Agent documentation. OS trust verification may require network access or locally cached trust data. Verified downloads remain cached for retries. Bootstrap JSON events identify the phase, package, installed CLI path and recovery action.

The persistent CLI is inside the installed application: macOS xmesh.app/Contents/Resources/bin/xmesh, Windows resources/bin/xmesh.exe. Agent documentation is included in the offline bundle and published as raw Markdown under the versioned install page. Use setup inspect, plan --input, apply --plan, status/resume/verify --job, and doctor --json. Preserve plan/job IDs for recovery. A running service and client verification have separate readiness states.

Verify and validate

Every downloadable file is listed in SHA256SUMS.txt. Match the package hash with the corresponding release record. The signed desktop packages contain the platform CLI; stable Windows/macOS distribution uses these native bundles. Linux CLI archives include the scripts and real-environment runbook.

The release tag must pass the full CI run on the same commit before artifacts are built. This covers Go, contracts, Headscale, Onboarding, UI and the native desktop executor, including native user-service acceptance when the runner has a supported user session. Native installer launch and upgrade acceptance must also be run on target devices; passing build checks alone does not establish those outcomes.

Operational limits

• Windows L2 isolation is unavailable in production. A Windows node configured with agent.policy.isolation: L2 refuses exec and PTY with sandbox.unavailable; runbook step F checks that boundary.
• LAN Agent TCP port 7433 is fixed, so two LAN nodes cannot run on the same host.
• OAuth tokens are held in memory; an ingress restart requires authorization again.
• Cloud connections require a reachable public endpoint, browser authorization and a successful request from the intended client. Setup reports prerequisites and recovery actions when these remain pending.

What's Changed

• Cloudflare：各设备令牌互通、删除隧道清本机配置、多级域名警告 by @tzf1003 in #151

Full Changelog: v0.1.0-beta.23...v0.1.0-beta.24

v0.1.0-beta.23

xmesh v0.1.0-beta.23 connects selected workspaces to local MCP clients, other devices and cloud agents.

Install and connect

Use the versioned install page to select Windows/macOS and amd64/arm64, download the desktop installer, or copy a version-pinned Agent prompt. Open the installed application, choose purpose/workspace/permissions/clients, review the setup plan and verify a real client request.

This release includes manifest.json with platform, architecture, SHA-256, byte size and verified signing metadata. Download and review install.sh (macOS) or install.ps1 (Windows), then pin this version:

bash install.sh --version v0.1.0-beta.23 --json

.\install.ps1 -Version v0.1.0-beta.23 -Json

Stable releases require Authenticode verification on Windows and a signed, notarized, stapled macOS application. Beta/rc versions belong to the testing channel. Consult each asset's trust entry; explicitly unsigned testing packages require --allow-unsigned / -AllowUnsigned. System security policies and signature checks remain active.

For offline installation, extract xmesh-offline-v0.1.0-beta.23-<os>-<arch>.zip, then use --offline <folder> / -Offline <folder>. The ZIP contains the native package, manifest, scripts and Agent documentation. OS trust verification may require network access or locally cached trust data. Verified downloads remain cached for retries. Bootstrap JSON events identify the phase, package, installed CLI path and recovery action.

The persistent CLI is inside the installed application: macOS xmesh.app/Contents/Resources/bin/xmesh, Windows resources/bin/xmesh.exe. Agent documentation is included in the offline bundle and published as raw Markdown under the versioned install page. Use setup inspect, plan --input, apply --plan, status/resume/verify --job, and doctor --json. Preserve plan/job IDs for recovery. A running service and client verification have separate readiness states.

Verify and validate

Every downloadable file is listed in SHA256SUMS.txt. Match the package hash with the corresponding release record. The signed desktop packages contain the platform CLI; stable Windows/macOS distribution uses these native bundles. Linux CLI archives include the scripts and real-environment runbook.

The release tag must pass the full CI run on the same commit before artifacts are built. This covers Go, contracts, Headscale, Onboarding, UI and the native desktop executor, including native user-service acceptance when the runner has a supported user session. Native installer launch and upgrade acceptance must also be run on target devices; passing build checks alone does not establish those outcomes.

Operational limits

• Windows L2 isolation is unavailable in production. A Windows node configured with agent.policy.isolation: L2 refuses exec and PTY with sandbox.unavailable; runbook step F checks that boundary.
• LAN Agent TCP port 7433 is fixed, so two LAN nodes cannot run on the same host.
• OAuth tokens are held in memory; an ingress restart requires authorization again.
• Cloud connections require a reachable public endpoint, browser authorization and a successful request from the intended client. Setup reports prerequisites and recovery actions when these remain pending.

What's Changed

• 设备路径质量观测：延时、丢包、断流 by @tzf1003 in #148
• 手动路径优先级：按用户顺序选局域网、Tailnet、Cloudflare by @tzf1003 in #149
• 智能选路：按延时、丢包和断流自动选最稳的路径 by @tzf1003 in #150

Full Changelog: v0.1.0-beta.22...v0.1.0-beta.23

v0.1.0-beta.22

xmesh v0.1.0-beta.22 connects selected workspaces to local MCP clients, other devices and cloud agents.

Install and connect

Use the versioned install page to select Windows/macOS and amd64/arm64, download the desktop installer, or copy a version-pinned Agent prompt. Open the installed application, choose purpose/workspace/permissions/clients, review the setup plan and verify a real client request.

This release includes manifest.json with platform, architecture, SHA-256, byte size and verified signing metadata. Download and review install.sh (macOS) or install.ps1 (Windows), then pin this version:

bash install.sh --version v0.1.0-beta.22 --json

.\install.ps1 -Version v0.1.0-beta.22 -Json

Stable releases require Authenticode verification on Windows and a signed, notarized, stapled macOS application. Beta/rc versions belong to the testing channel. Consult each asset's trust entry; explicitly unsigned testing packages require --allow-unsigned / -AllowUnsigned. System security policies and signature checks remain active.

For offline installation, extract xmesh-offline-v0.1.0-beta.22-<os>-<arch>.zip, then use --offline <folder> / -Offline <folder>. The ZIP contains the native package, manifest, scripts and Agent documentation. OS trust verification may require network access or locally cached trust data. Verified downloads remain cached for retries. Bootstrap JSON events identify the phase, package, installed CLI path and recovery action.

The persistent CLI is inside the installed application: macOS xmesh.app/Contents/Resources/bin/xmesh, Windows resources/bin/xmesh.exe. Agent documentation is included in the offline bundle and published as raw Markdown under the versioned install page. Use setup inspect, plan --input, apply --plan, status/resume/verify --job, and doctor --json. Preserve plan/job IDs for recovery. A running service and client verification have separate readiness states.

Verify and validate

Every downloadable file is listed in SHA256SUMS.txt. Match the package hash with the corresponding release record. The signed desktop packages contain the platform CLI; stable Windows/macOS distribution uses these native bundles. Linux CLI archives include the scripts and real-environment runbook.

The release tag must pass the full CI run on the same commit before artifacts are built. This covers Go, contracts, Headscale, Onboarding, UI and the native desktop executor, including native user-service acceptance when the runner has a supported user session. Native installer launch and upgrade acceptance must also be run on target devices; passing build checks alone does not establish those outcomes.

Operational limits

• Windows L2 isolation is unavailable in production. A Windows node configured with agent.policy.isolation: L2 refuses exec and PTY with sandbox.unavailable; runbook step F checks that boundary.
• LAN Agent TCP port 7433 is fixed, so two LAN nodes cannot run on the same host.
• OAuth tokens are held in memory; an ingress restart requires authorization again.
• Cloud connections require a reachable public endpoint, browser authorization and a successful request from the intended client. Setup reports prerequisites and recovery actions when these remain pending.

What's Changed

• 网关：首次 tools/list 等待远端设备工具表，最多 5 秒 by @tzf1003 in #147

Full Changelog: v0.1.0-beta.21...v0.1.0-beta.22

v0.1.0-beta.21

xmesh v0.1.0-beta.21 connects selected workspaces to local MCP clients, other devices and cloud agents.

Install and connect

Use the versioned install page to select Windows/macOS and amd64/arm64, download the desktop installer, or copy a version-pinned Agent prompt. Open the installed application, choose purpose/workspace/permissions/clients, review the setup plan and verify a real client request.

This release includes manifest.json with platform, architecture, SHA-256, byte size and verified signing metadata. Download and review install.sh (macOS) or install.ps1 (Windows), then pin this version:

bash install.sh --version v0.1.0-beta.21 --json

.\install.ps1 -Version v0.1.0-beta.21 -Json

Stable releases require Authenticode verification on Windows and a signed, notarized, stapled macOS application. Beta/rc versions belong to the testing channel. Consult each asset's trust entry; explicitly unsigned testing packages require --allow-unsigned / -AllowUnsigned. System security policies and signature checks remain active.

For offline installation, extract xmesh-offline-v0.1.0-beta.21-<os>-<arch>.zip, then use --offline <folder> / -Offline <folder>. The ZIP contains the native package, manifest, scripts and Agent documentation. OS trust verification may require network access or locally cached trust data. Verified downloads remain cached for retries. Bootstrap JSON events identify the phase, package, installed CLI path and recovery action.

The persistent CLI is inside the installed application: macOS xmesh.app/Contents/Resources/bin/xmesh, Windows resources/bin/xmesh.exe. Agent documentation is included in the offline bundle and published as raw Markdown under the versioned install page. Use setup inspect, plan --input, apply --plan, status/resume/verify --job, and doctor --json. Preserve plan/job IDs for recovery. A running service and client verification have separate readiness states.

Verify and validate

Every downloadable file is listed in SHA256SUMS.txt. Match the package hash with the corresponding release record. The signed desktop packages contain the platform CLI; stable Windows/macOS distribution uses these native bundles. Linux CLI archives include the scripts and real-environment runbook.

The release tag must pass the full CI run on the same commit before artifacts are built. This covers Go, contracts, Headscale, Onboarding, UI and the native desktop executor, including native user-service acceptance when the runner has a supported user session. Native installer launch and upgrade acceptance must also be run on target devices; passing build checks alone does not establish those outcomes.

Operational limits

• Windows L2 isolation is unavailable in production. A Windows node configured with agent.policy.isolation: L2 refuses exec and PTY with sandbox.unavailable; runbook step F checks that boundary.
• LAN Agent TCP port 7433 is fixed, so two LAN nodes cannot run on the same host.
• OAuth tokens are held in memory; an ingress restart requires authorization again.
• Cloud connections require a reachable public endpoint, browser authorization and a successful request from the intended client. Setup reports prerequisites and recovery actions when these remain pending.

What's Changed

• cloudflare：无钥匙串时存文件、自动安装 cloudflared、显示 Tunnel 主机名 by @tzf1003 in #146

Full Changelog: v0.1.0-beta.20...v0.1.0-beta.21

v0.1.0-beta.20

xmesh v0.1.0-beta.20 connects selected workspaces to local MCP clients, other devices and cloud agents.

Install and connect

Use the versioned install page to select Windows/macOS and amd64/arm64, download the desktop installer, or copy a version-pinned Agent prompt. Open the installed application, choose purpose/workspace/permissions/clients, review the setup plan and verify a real client request.

This release includes manifest.json with platform, architecture, SHA-256, byte size and verified signing metadata. Download and review install.sh (macOS) or install.ps1 (Windows), then pin this version:

bash install.sh --version v0.1.0-beta.20 --json

.\install.ps1 -Version v0.1.0-beta.20 -Json

Stable releases require Authenticode verification on Windows and a signed, notarized, stapled macOS application. Beta/rc versions belong to the testing channel. Consult each asset's trust entry; explicitly unsigned testing packages require --allow-unsigned / -AllowUnsigned. System security policies and signature checks remain active.

For offline installation, extract xmesh-offline-v0.1.0-beta.20-<os>-<arch>.zip, then use --offline <folder> / -Offline <folder>. The ZIP contains the native package, manifest, scripts and Agent documentation. OS trust verification may require network access or locally cached trust data. Verified downloads remain cached for retries. Bootstrap JSON events identify the phase, package, installed CLI path and recovery action.

The persistent CLI is inside the installed application: macOS xmesh.app/Contents/Resources/bin/xmesh, Windows resources/bin/xmesh.exe. Agent documentation is included in the offline bundle and published as raw Markdown under the versioned install page. Use setup inspect, plan --input, apply --plan, status/resume/verify --job, and doctor --json. Preserve plan/job IDs for recovery. A running service and client verification have separate readiness states.

Verify and validate

Every downloadable file is listed in SHA256SUMS.txt. Match the package hash with the corresponding release record. The signed desktop packages contain the platform CLI; stable Windows/macOS distribution uses these native bundles. Linux CLI archives include the scripts and real-environment runbook.

The release tag must pass the full CI run on the same commit before artifacts are built. This covers Go, contracts, Headscale, Onboarding, UI and the native desktop executor, including native user-service acceptance when the runner has a supported user session. Native installer launch and upgrade acceptance must also be run on target devices; passing build checks alone does not establish those outcomes.

Operational limits

• Windows L2 isolation is unavailable in production. A Windows node configured with agent.policy.isolation: L2 refuses exec and PTY with sandbox.unavailable; runbook step F checks that boundary.
• LAN Agent TCP port 7433 is fixed, so two LAN nodes cannot run on the same host.
• OAuth tokens are held in memory; an ingress restart requires authorization again.
• Cloud connections require a reachable public endpoint, browser authorization and a successful request from the intended client. Setup reports prerequisites and recovery actions when these remain pending.

What's Changed

• 界面：在设备页为本机创建和删除 Cloudflare 隧道 by @tzf1003 in #143
• release：所有标签都发布为正式版并设为 Latest by @tzf1003 in #144
• ci：双节点 coexist 冒烟测试的 MCP 客户端超时放宽到 120 秒 by @tzf1003 in #145

Full Changelog: v0.1.0-beta.18...v0.1.0-beta.20

v0.1.0-beta.18

xmesh v0.1.0-beta.18 connects selected workspaces to local MCP clients, other devices and cloud agents.

Install and connect

Use the versioned install page to select Windows/macOS and amd64/arm64, download the desktop installer, or copy a version-pinned Agent prompt. Open the installed application, choose purpose/workspace/permissions/clients, review the setup plan and verify a real client request.

This release includes manifest.json with platform, architecture, SHA-256, byte size and verified signing metadata. Download and review install.sh (macOS) or install.ps1 (Windows), then pin this version:

bash install.sh --version v0.1.0-beta.18 --json

.\install.ps1 -Version v0.1.0-beta.18 -Json

Stable releases require Authenticode verification on Windows and a signed, notarized, stapled macOS application. Beta/rc versions belong to the testing channel. Consult each asset's trust entry; explicitly unsigned testing packages require --allow-unsigned / -AllowUnsigned. System security policies and signature checks remain active.

For offline installation, extract xmesh-offline-v0.1.0-beta.18-<os>-<arch>.zip, then use --offline <folder> / -Offline <folder>. The ZIP contains the native package, manifest, scripts and Agent documentation. OS trust verification may require network access or locally cached trust data. Verified downloads remain cached for retries. Bootstrap JSON events identify the phase, package, installed CLI path and recovery action.

The persistent CLI is inside the installed application: macOS xmesh.app/Contents/Resources/bin/xmesh, Windows resources/bin/xmesh.exe. Agent documentation is included in the offline bundle and published as raw Markdown under the versioned install page. Use setup inspect, plan --input, apply --plan, status/resume/verify --job, and doctor --json. Preserve plan/job IDs for recovery. A running service and client verification have separate readiness states.

Verify and validate

Every downloadable file is listed in SHA256SUMS.txt. Match the package hash with the corresponding release record. The signed desktop packages contain the platform CLI; stable Windows/macOS distribution uses these native bundles. Linux CLI archives include the scripts and real-environment runbook.

The release tag must pass the full CI run on the same commit before artifacts are built. This covers Go, contracts, Headscale, Onboarding, UI and the native desktop executor, including native user-service acceptance when the runner has a supported user session. Native installer launch and upgrade acceptance must also be run on target devices; passing build checks alone does not establish those outcomes.

Operational limits

• Windows L2 isolation is unavailable in production. A Windows node configured with agent.policy.isolation: L2 refuses exec and PTY with sandbox.unavailable; runbook step F checks that boundary.
• LAN Agent TCP port 7433 is fixed, so two LAN nodes cannot run on the same host.
• OAuth tokens are held in memory; an ingress restart requires authorization again.
• Cloud connections require a reachable public endpoint, browser authorization and a successful request from the intended client. Setup reports prerequisites and recovery actions when these remain pending.

What's Changed

• 设备间下发连接方式：A 给 B 建 Cloudflare 隧道并下发 by @tzf1003 in #139
• 设备间下发 Tailscale 连接方式：预授权 key 经已配对连接发给对方 by @tzf1003 in #140
• 界面：设备页接受或拒绝其他设备发来的连接方式 by @tzf1003 in #141
• 界面：设备详情里直接分享 Cloudflare 隧道或 Tailscale key by @tzf1003 in #142

Full Changelog: v0.1.0-beta.17...v0.1.0-beta.18