What changed, and when.
Security updates and upgrade notes for TSLink v0.1.1
2026/10/09
Security update. Commands, flags and stored data are unchanged from 0.1.0.
brew upgrade --cask anydoor7/tap/tslink. Other installs: download the new archive or package from this release.tslink install again after upgrading so the service starts the new binary.govulncheck -mode=binary reports vulnerable standard-library symbols for 12 advisories: GO-2026-6599, GO-2026-6600, GO-2026-6603, GO-2026-6605, GO-2026-6607, GO-2026-6608, GO-2026-6609, GO-2026-6610, GO-2026-6611, GO-2026-6612, GO-2026-6613 and GO-2026-6617. They cover HTTP/2 server crashes, resource exhaustion and flow-control errors, HTTP/2 response smuggling via malformed headers, HTTP/1 connection desynchronization after CONNECT, Range header parsing without a size limit, MIME header memory-limit bypasses, html/template escaping and malformed crypto/tls ECH extension references. With Go 1.27.2, govulncheck ./... reports no reachable vulnerabilities in the 0.1.1 source on macOS arm64.tailscale.com is updated to v1.104.1 and golang.org/x/net to v0.60.0.tslink manifest --json reports that minimum.Changes and compatibility notes for the first public TSLink version
2026/10/06
First public release. TSLink gives each app on your computer or server, whether a web app, a folder or file, or a TCP port, its own private address on your Tailscale network, so you can open it from your own devices. You decide who else can reach it: people you name, browser guests with an expiring link, or, only when you ask for it, the public internet. Run it yourself from the CLI or through an AI agent over MCP. TSLink needs a Tailscale account and is an independent project, not made or endorsed by Tailscale.
.deb and .rpm packages for Linux, and a Homebrew cask for macOS and Linux: brew install --cask anydoor7/tap/tslink.checksums.txt and the SBOMs carry Sigstore signatures, and every release asset has a GitHub build provenance attestation. See Verify a release. Building from source needs Go 1.26.6 or newer.tslink share 3000, tslink share ./photos or tslink share ./report.html gives a web app, folder or single file its own HTTPS address in your tailnet. tslink add <name> --tcp <port> does the same for a TCP service. Each app runs as its own embedded Tailscale node inside one background daemon.tslink install starts the daemon at login: a LaunchAgent on macOS, a systemd user service on Linux and a per-user scheduled task on Windows (--startup uses the Startup folder instead).tslink apps detect finds apps listening on this machine, and tslink apps share <recipe> previews a registration that --yes applies.--max-request-body and timeouts) for large or slow uploads. The default body limit is 32 MiB.tslink people add alice@example.com --apps photos,finance --for 7d lets that Tailscale login open the chosen web and file apps until the deadline. people update, extend and people remove change or revoke access. --invite --print-links adds device invitations for someone outside your tailnet (this needs a user-owned API token), and --qr prints a QR code for phone setup.tslink guest create photos --for 3d --public --print-link creates an expiring browser link, optionally with a PIN, for a web app. Guests need no Tailscale account. The link goes through Tailscale Funnel behind a mandatory guest gate. Anyone holding the link can use it; TSLink stores only its hash.--funnel --public, works for web apps only and always expires, after 24 hours by default and at most 7 days unless you raise durations.public_max.90m, 36h, 3d, 1w, 1d12h or until 2030-06-01. The minimum is one hour. Only tailnet members can be given never, and only with --ack-never.tslink portal enable --owner you@example.com starts a private home page on its own tailnet node. Each visitor sees the apps they may open, with their health and deadlines.--requestable are offered. tslink requests approve <id> --for 3d or tslink requests deny <id> decides, and a new request can trigger an alert.healthy, degraded, down or unknown in status, list --verbose, doctor and the portal. status and doctor warn 14 days and 3 days before a node key expires.alerts.json.tslink access log shows who opened which app and when, including denied requests, with summaries per person and per app. By default only the first path segment is recorded; tslink access path changes that per app.tslink mcp accepts --json and returns a versioned tslink.result envelope; Cobra's help and completion are not in the manifest and print plain text. tslink manifest --json lists those commands with their flags, exit codes and error codes.tslink mcp is an MCP server over stdio. tslink serve --mcp adds a remote MCP endpoint on its own tailnet-only node; it is never published through Funnel.viewer, app-operator and people-manager limit an agent to listed apps, a fixed set of tools and a maximum grant duration, while owner keeps full control. Use tslink mcp --scope locally, or mcp.bindings for remote callers, who are identified by Tailscale login or tag. tslink mcp-audit reads the journal of changes made through MCP.link_local_target_refused) and file shares that would expose TSLink's config directory (path_exposes_config_dir).Tailscale-* and X-Tailscale-* identity headers before adding the caller's identity from Tailscale.tslink remove and cleanup delete a tailnet device only when TSLink recorded that exact device as its own.mcp.allow_elevated_invites opt-in.For later 0.x releases, these are the public automation and data contracts:
--json keeps the tslink.result envelope and its type, ok, schema_version, command, code, data, and error fields. Optional data, error, and error.next stay optional; fields may be added.data fields keep their meaning; fields and warnings may be added. Public view data.schema_version stays an integer.tslink manifest --json derives error_codes from this mapping.registry.json schemas 1 and 2 and known config.json keys remain readable; fields may be added. Run registry check before an upgrade.isError: true, one JSON text failure object (code, message, next, optional data), and no structuredContent; schema argument errors use usage_error. The four behavior annotations remain present on every tool.--json instead. runtime.json and other daemon/CLI state files are private.