Tailscale plugin: support inbound to the Grok Bot box, or a Tailscale node that survives resets

未關閉
#774 1 則留言 0 個 reaction 已指派 0 人 在 GitHub 檢視

維護者通常 1 天內回覆

還沒有人認領這個 Issue。

評估

難度
5/5
預估耗時
一週以上
新手友好度
25/100
Issue 類型
功能
描述清晰度
基本清楚
活躍度
活躍
技術堆疊
typescript

研究方向

Start by reading the Tailscale plugin under third_party/tailscale and trace how its managed connection is set up for outbound MCP traffic. The issue asks for inbound SSH, TCP, Funnel/Serve, general outbound traffic, or a persistent node identity; compare those needs with the plugin's current scope and identify a supported design. Done means the chosen approach supports the required traffic and survives box resets without interactive re-login.

由索引模型根據 Issue 內容生成。

描述

Summary

The Tailscale plugin (third_party/tailscale) lets Grok Bot reach MCP servers on my tailnet as a managed tag:grokbot device. That covers outbound MCP traffic only. Most of what I need from Tailscale is the other direction: devices on my tailnet reaching the Grok Bot box itself. Today that only works by installing Tailscale on the box by hand, and box resets keep breaking it.

My setup

  • Personal tailnet. The box runs its own tailscaled as grokbot-host (tag:grokbots), with Tailscale SSH and one Funnel path.
  • Inbound uses:
    • SSH from my devices into the box (Tailscale SSH only, rules in my tailnet policy)
    • A private web app my bots serve on the box's tailnet IP
    • A Twilio voice webhook exposed through Tailscale Funnel on a single path (/phone)
  • Outbound uses: reading various homelab services over the tailnet

What breaks

The box has been reset several times recently. Each reset wipes /var/lib/tailscale, so the self-managed node needs an interactive re-login, comes back under a new name (grokbot-host-1) until I delete the old machine, and loses its Funnel config. A plugin-managed connection would avoid all of that.

Ask

  1. Let the plugin's tailnet connection accept inbound traffic to the box: SSH, a TCP port, and Funnel/Serve for a path.
  2. Let non-MCP traffic from the box (plain HTTP, scripts) use the plugin's connection, not just MCP connectors.
  3. Or provide a supported way to run a Tailscale node on the box whose identity persists across resets.

Environment

Grok Bot on a personal tailnet. Box Tailscale 1.104.2, kernel TUN mode.

主要語言
TypeScript
星號
14.9k
分支
1.5k
平均合併
3 小時 20 分鐘
30 天內合併 PR
142

環境準備

這個專案沒有提供開發容器、Dockerfile 或貢獻指南,環境需要你自己搭建:先看它的 README,通用步驟見我們的新手貢獻指南。

從這裡開始

  1. 先讀完整個 Issue,再讀專案的貢獻指南。
  2. 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
  3. Fork 儲存庫,在一個分支上完成修改。
  4. 送出 Pull Request,並在描述裡引用這個 Issue 編號。

cursor/plugins 的其他 Issue

查看 cursor/plugins 的全部 Issue

相似的 Issue

更多 TypeScript Issue

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。