Tailscale: tagging tag:grokbot drops the session; reconnect mints a new untagged device
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
- Domain
- authentication, networking
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
- Install/connect the Tailscale plugin so Grok Bot joins the personal tailnet (device appears, typically named like
grokbot-user-…). - In Tailscale admin, set device tags to
tag:grokbot(withtagOwnersallowing that tag). - Observe the Grok Bot Tailscale session disconnects / device goes offline.
- Authenticate / Sign in again from Grok Bot.
- A new Grok Bot device appears on the tailnet — still untagged (owner access).
- Repeat: tagging again → disconnect → reconnect → another new untagged device.
Expected
Either:
- tagging
tag:grokbotkeeps the same device online and tagged, so grants likesrc: ["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-setupskill presenttag:grokbotas 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
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from cursor/plugins
-
pstack: interrogate asks the user, which worker.md forbids for delegates that reach itPossibly taken A pull request linked to this issue is open or already merged. Open
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
cursor/plugins#1272 · 1 comment ·
Maintainers usually reply within 1 day
-
poteto-mode: multi-phase-plan Merge placeholder still appends every PR to a base-branch stackPossibly taken @mangeshraut712 claimed this 15 days ago. Open
Difficulty 1/5 Under an hour Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
typescript-best-practices: schema example uses z.string().uuid(), deprecated in Zod 4Possibly taken @mangeshraut712 claimed this 14 days ago. Open
Difficulty 1/5 Under an hour Newbie friendliness 88/100
cursor/plugins#1165 · 1 comment ·
Maintainers usually reply within 1 day
-
statechart: relative-symlink launcher test fails on macOS because /var is a symlinkPossibly taken A pull request linked to this issue is open or already merged. Open
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
cursor/plugins#1164 · 2 comments ·
Maintainers usually reply within 1 day
-
pstack docs/harness/claude-code.md: transcript slug replaces every non-alphanumeric character, not only / and .Possibly taken @isTuhin claimed this 9 days ago. Open
Difficulty 1/5 1-3 hours Newbie friendliness 82/100
cursor/plugins#1155 · 2 comments ·
Maintainers usually reply within 1 day
Similar issues
-
[UI] Guard webApis against undefined window in SSR environmentsPossibly taken @madhavzanwar claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
headroomlabs-ai/headroom#4992 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
paperclipai/paperclip#22575 ·
Maintainers usually reply within 1 day
-
community first-timers-only good first issue hacktoberfest help wanted low hanging fruit up-for-grabs
Difficulty 1/5 Under an hour Newbie friendliness 82/100
lingdojo/kana-dojo#34502 · 1 comment · 5 reactions ·
Maintainers usually reply within 1 day
-
bug frontend good first issue help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
nikhilb2/simple_invoicing#935 ·