Skip to content

Cursor plugin specification and official plugins

TypeScript

tailscale: match the skill to current routing, refusals and troubleshooting.

Eric G.Y Liu139cc15566c6
diff --git a/third_party/tailscale/CHANGELOG.md b/third_party/tailscale/CHANGELOG.md
index 0d16db4d..9cf50eb3 100644
--- a/third_party/tailscale/CHANGELOG.md
+++ b/third_party/tailscale/CHANGELOG.md
@@ -5,7 +5,8 @@ All notable changes to this plugin will be documented here.
## 1.0.4
- The setup skill matches the current connection: one Tailscale row with a slot per tailnet, several tailnets at once, company tailnets enabled at cursor.com and limited with `custom:grokbot` postures, and personal tailnets via one-click Connect or `tag:grokbot`.
-- Drops the single-tailnet flow and the "confirm it's my Tailscale login" step. Grok Bot asks Allow/Deny before removing a device, signing in again, adding a tailnet, or changing the default.
+- Drops the single-tailnet flow and the "confirm it's my Tailscale login" step. Grok Bot asks Allow/Deny before removing a device, adding a tailnet, or changing the default.
+- Covers `http://` servers, one live personal tailnet at a time, Slack Connect refusals, and troubleshooting for expired devices, Tailscale plans without custom node attributes, shared-in devices, and internal certificates.
- The plugin description covers one-click Connect, `tag:grokbot`, and the company tailnet.
## 1.0.2
diff --git a/third_party/tailscale/README.md b/third_party/tailscale/README.md
index 11ad46b9..04e6c2df 100644
--- a/third_party/tailscale/README.md
+++ b/third_party/tailscale/README.md
@@ -12,7 +12,7 @@ Let Grok Bot reach MCP servers on your private Tailscale network: connect your o
## MCP
-This plugin ships no `mcp.json`. Grok Bot's Tailscale connection is served by the Cursor backend, and installing the plugin is the opt-in that turns it on. MCP servers on the tailnet are added separately, by their `https://` address.
+This plugin ships no `mcp.json`. Grok Bot's Tailscale connection is served by the Cursor backend, and installing the plugin is the opt-in that turns it on. MCP servers on the tailnet are added separately, by their `http://` or `https://` address.
## Setup
@@ -25,7 +25,7 @@ Grok Bot desktop has one **Tailscale** row (**Connect apps → Your plugins**) w
- An address under a tailnet's `.ts.net` name uses that tailnet. Short names and `100.x` addresses use the member's default tailnet.
- On a personal tailnet, only the bot owner, linked teammates, and routines the owner schedules can use it. On a company tailnet, only that member's own chats and routines.
-- Grok Bot asks before it removes a device, signs in again, adds a tailnet, or changes the default.
+- Grok Bot asks before it removes a device, adds a tailnet, or changes the default. Members change the default by asking Grok Bot.
- To disconnect, click **Remove** on the Tailscale plugin page in Grok Bot.
## Docs
diff --git a/third_party/tailscale/skills/tailscale-setup/SKILL.md b/third_party/tailscale/skills/tailscale-setup/SKILL.md
index 61f24323..3e0d4656 100644
--- a/third_party/tailscale/skills/tailscale-setup/SKILL.md
+++ b/third_party/tailscale/skills/tailscale-setup/SKILL.md
@@ -7,9 +7,9 @@ description: Connect Grok Bot to Tailscale on a company tailnet (a team admin en
Grok Bot desktop has one Tailscale row: **Connect apps → Your plugins → Tailscale**. The row has one slot per tailnet, labeled with the tailnet name first, then **Personal** or the team name, then the `.ts.net` address.
-A member can connect several tailnets at once. An address under a tailnet's `.ts.net` name goes to that tailnet. A short name or a `100.x` address goes to the member's default tailnet. They change the default on the plugin page or by asking Grok Bot.
+A member can connect several company tailnets at once, plus one personal tailnet; switching personal tailnets parks the others. An address under a tailnet's `.ts.net` name goes to that tailnet. A short name or a `100.x` address goes to the member's default tailnet. They change the default by asking Grok Bot.
-Grok Bot shows an Allow/Deny card before it removes a device, signs in to a tailnet again, adds a tailnet, or changes the default. Wait for **Allow**.
+Grok Bot shows an Allow/Deny card before it removes a device, adds a tailnet, or changes the default. Wait for **Allow**.
Reach tailnet MCP servers through this row. A Tailscale client installed on the bot's computer is wiped when that computer is replaced.
@@ -79,14 +79,17 @@ Otherwise define `tag:grokbot` and grant it only the MCP servers, then sign in w
## Who can use it
-On a personal tailnet, only the bot owner's messages, linked teammates, and routines the owner schedules. On a company tailnet, only that member's own Grok Bot chats, Slack DMs, and routines they schedule. Removing the member from the team logs the device out.
+On a personal tailnet, only the bot owner's messages, linked teammates, and routines the owner schedules. On a company tailnet, only that member's own Grok Bot chats, Slack DMs, and routines they schedule. Slack Connect channels never use a tailnet. Removing the member from the team logs the device out.
## Add MCP servers
-Add a server by its `https://` address on the tailnet, or add it when the user asks. Use the full `name.tailnet.ts.net` host when it should use that tailnet. A short name or a `100.x` address uses the default tailnet.
+Add a server by its `http://` or `https://` address on the tailnet, or add it when the user asks. Use the full `name.tailnet.ts.net` host when it should use that tailnet. A short name or a `100.x` address uses the default tailnet. Split-DNS names and subnet-route addresses use HTTPS on port 443.
## Troubleshooting
- **Wrong account or tailnet:** **Sign in again**.
-- **Expired link:** **Authenticate** again.
+- **Expired link or expired device:** **Authenticate** again. Company devices follow the tailnet's key expiry.
+- **Company sign-in says Grok Bot's Tailscale app isn't allowed:** the tailnet needs a plan with custom node attributes (Tailscale Premium or Enterprise).
- **Can't reach a server:** check the full `.ts.net` name against the default tailnet, the policy grant for that host and port, split DNS and subnet routes (ask the user's Cursor contact to enable those), and the certificate.
+- **Device shared in from another tailnet:** it can't be reached by name; use its `100.x` address with the receiving tailnet as the default.
+- **Server with an internal certificate:** a team admin adds the CA in **Integrations → Tailscale** (ask the user's Cursor contact to enable it).