TSLink v0.4.0: two-command guest links, limits set
Guest links work on a new installation with tslink add and tslink guest create, upload limits change in place, and remote MCP needs the portal owner for public changes.
TSLink v0.4.0 makes browser guest links work on a new installation in two commands, lets you change an app's upload limits without starting it over, and requires the current portal owner for every public change made over remote MCP. The home gateway that new installations use was introduced in v0.3.0.
Guest links in two commands
tslink add photos --proxy localhost:3000
tslink guest create photos --for 3d --public --print-linkWhen only you and your admins use the app's gateway route and the app's own node is running with an exact URL, the first guest link takes the app off the home gateway in the same write that saves the grant and says so (removed_gateway_route). If the node URL is not ready yet, it refuses with url_not_ready and saves nothing: run tslink url photos --wait=30s and create the link again. Conditions are in guest links. If someone else depends on that route, for example a person you granted the app to, it refuses with portal_route_guest_refused, changes nothing and names the next command. A second link now works while the guest gate is up, and tslink remove revokes the app's guest links, so an app re-added under the same name cannot bring old links back. While the guest gate is up an app cannot take new people grants; grants given before the gate keep working on the private tailnet listener. Walkthroughs: send a download link that expires, let someone upload big files and guest links.
Upload limits in place
tslink limits set photos --max-request-body 256MiB changes only the app's request limits, including on an app with guest links, where add is refused. It restarts the app's node, so guests reopen their link. An upload over the cap now gets a JSON 413 that names the limit, and status and doctor count those refusals with the command that raises it.
Remote MCP operators
On an installation with a portal owner or a home gateway, a remote principal with the MCP owner role that is not the current portal owner now gets access_request_owner_required for changes to public apps, including unshare, limits_set and app_restart. Revoking a guest link stays open to it. Run such changes as the portal owner, or locally with the CLI or stdio MCP. Installations without a remote MCP control plane are unaffected.
Upgrade
No registry migration is required. For Homebrew:
brew upgrade --cask anydoor7/tap/tslink
# If TSLink runs as a background service:
tslink installScoop users run scoop update, then scoop update tslink. Other users can download the v0.4.0 release archives and packages. v0.4.0 is built with Go 1.27.4 for GO-2026-6859.
See the installation and verification guide and the frozen TSLink v0.4.0 changelog. TSLink is an independent project, not made or endorsed by Tailscale.
Author
Categories
More Posts
Introducing TSLink: Share Local Services by Name
A Go CLI for sharing an existing app or file on your private tailnet, then managing named services with CLI JSON and MCP.
TSLink v0.2.0: one gateway share for several private apps
Opt-in portal gateway mode, health-check changes, upgrade steps and registry compatibility.
Share Your First Local Service with TSLink
Install TSLink, share an existing app or file, approve the node if prompted, and retrieve its private URL.