Repository navigation
tailscale: never install or run the Tailscale client on the bot's computer (1.0.5) - #1030
Open
ericgyl817 wants to merge 1 commit into
Open
ericgyl817 wants to merge 1 commit into
ericgyl817 wants to merge 1 commit into
Conversation
… on the bot's computer (1.0.5)
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
• What: the setup skill again forbids installing or running the Tailscale client on the bot's computer, and says Tailscale isn't available when there's no row.
• Why: 1.0.4 (82ad96d) softened the rule to a caveat, and bots outside the beta started running Tailscale themselves outside tailnet-egress's checks (SAND-6713).
• Regression: none; the row-based path is unchanged.
Note
Low Risk
Documentation and agent skill text only; no runtime or connection logic changes.
Overview
Bumps the Tailscale plugin to 1.0.5 and tightens Grok Bot setup guidance after 1.0.4 had weakened it.
The
tailscale-setupskill again forbids installing, starting, or signing intotailscale/tailscaledon the bot machine, and tells the bot not to ask users to approve a device for that path—because it bypasses tailnet safety checks and exposes the user's tailnet to every bot on that host. It also instructs Grok Bot to say Tailscale isn't available when there is no Tailscale row in Connect apps → Your plugins. Row-based tailnet access is unchanged; this is documentation/skill behavior only.Reviewed by Cursor Bugbot for commit 82026f6. Bugbot is set up for automated code reviews on this repo. Configure here.