Tailscale: tagging tag:grokbot drops the session; reconnect mints a new untagged device

Open
#1,172 5 comments 1 reaction 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
46/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
typescript

Research direction

Start with the Tailscale plugin in third_party/tailscale and trace how it authenticates and reconnects a device after its tag changes. Check the plugin docs and tailscale-setup skill for the documented tag:grokbot flow. Done means tagging no longer leads to repeated new, untagged devices, and the documented least-privilege grants work as expected.

Written by the indexing model from the issue text.

Description

Summary

On a personal Tailscale tailnet, applying tag:grokbot to the Grok Bot device immediately drops its session. Reconnecting via Authenticate mints a new device that is again untagged. Least-privilege ACL/grants that target only tag:grokbot therefore never take effect in practice.

Steps to reproduce

  1. Install/connect the Tailscale plugin so Grok Bot joins the personal tailnet (device appears, typically named like grokbot-user-…).
  2. In Tailscale admin, set device tags to tag:grokbot (with tagOwners allowing that tag).
  3. Observe the Grok Bot Tailscale session disconnects / device goes offline.
  4. Authenticate / Sign in again from Grok Bot.
  5. A new Grok Bot device appears on the tailnet — still untagged (owner access).
  6. Repeat: tagging again → disconnect → reconnect → another new untagged device.

Expected

Either:

  • tagging tag:grokbot keeps the same device online and tagged, so grants like src: ["tag:grokbot"] → MCP host:port work; or
  • reconnect after tagging re-joins as the same tagged device (or re-applies the tag automatically).

Actual

Tagging forces a disconnect; each reconnect creates a fresh untagged machine. The documented least-privilege path (tag:grokbot + narrow grants) is effectively unenforceable for personal tailnets. Workaround today is owner-access (untagged) plus host/IP grants, which is broader than intended.

Notes

  • MagicDNS names in grants were rejected as invalid in our policy; we used the Tailscale IP (100.x) instead — separate friction, may be worth documenting.
  • Plugin docs / tailscale-setup skill present tag:grokbot as the least-privilege path; this loop contradicts that.
  • Related but different: #774 (inbound to the box / node surviving resets).

Environment

  • Grok Bot Tailscale plugin (third_party/tailscale)
  • Personal tailnet (incremental.coach / *.ts.net)
  • Goal: reach a private MCP on the tailnet with grants limited to tag:grokbot
Dominant language
TypeScript
Stars
18.2k
Forks
2k
Avg merge
3h 56m
Merged PRs (30d)
96

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from cursor/plugins

All issues in cursor/plugins

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.