Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

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

Abierto
  • ¿Algo no está bien?
#774 1 comentario 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
25/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
typescript
Área
infrastructure, networking

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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.

Lenguaje dominante
TypeScript
Estrellas
13.9k
Forks
1.4k
Merge medio
5 h 57 min
PR fusionados (30 d)
135

Preparar el entorno

Este proyecto no incluye contenedor de desarrollo, Dockerfile ni guía de contribución, así que la configuración corre por tu cuenta: empieza por su README y consulta nuestra guía para la primera contribución para los pasos generales.

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de cursor/plugins

Todos los issues de cursor/plugins

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.