Writing

Field notes · October 14, 2026

Persistent Networking in Ephemeral AI VMs: Tailscale in ChatGPT Dots

A community-developed script enables persistent Tailscale networking and user-level OpenSSH within the ephemeral virtual machines of ChatGPT Dots by storing state in the /workspace directory. This development raises significant theoretical

Persistent Networking in Ephemeral AI VMs: Tailscale in ChatGPT Dots
I made a small script for running Tailscale in ChatGPT Dots

A recent contribution to the r/ChatGPT community details a method for maintaining network connectivity across the transient lifecycle of virtual machines provisioned through ChatGPT Dots. The author, operating under the handle abruption, developed and published a setup script designated as dots-tailscale version 0.1.0. According to the project documentation hosted on GitHub, the fundamental challenge addressed by this script is that ChatGPT Dots virtual machines can be replaced periodically, resulting in the loss of installed software and network configurations. To circumvent this ephemerality, the script installs Tailscale alongside a user-level instance of OpenSSH. Crucially, the installation files and the node state are directed to the /workspace directory, which persists across virtual machine replacements. The author reports having confirmed the stability of this configuration for over twenty-four hours in their own environment before publishing the release and soliciting community feedback.

I made a small script for running Tailscale in ChatGPT Dots

The mechanism underlying this solution relies on the architectural separation between the root filesystem of an ephemeral container or virtual machine and its mounted persistent storage volumes. In standard cloud computing paradigms, ephemeral compute instances are designed to be stateless; any modifications made to the base operating system are discarded when the instance is terminated or recycled. However, platforms frequently provide attached storage directories—such as the /workspace directory in this context—to allow users to save data, code, or artifacts between sessions. By redirecting the Tailscale binaries, configuration files, and cryptographic node state into this persistent volume, the script effectively decouples the network identity from the underlying hardware lifecycle. When the virtual machine is replaced, the initialization script re-establishes the Tailscale daemon using the preserved state, allowing the new instance to seamlessly rejoin the user's private mesh network without requiring manual re-authentication. The inclusion of user-level OpenSSH further extends this persistence, enabling secure remote access without requiring root privileges that might not survive the environment reset.

While the technical ingenuity of this approach is notable, the limits of the current evidence must be carefully delineated. The primary constraint is the sample size and duration of the validation. The author confirms functionality over a period exceeding twenty-four hours within a single personal setup. In distributed systems engineering, twenty-four hours is insufficient to evaluate long-term reliability, particularly regarding edge cases such as token expiration, platform-side updates to the Dots environment, or race conditions during rapid virtual machine recycling. Furthermore, because this is a community-driven project rather than an officially supported feature from the platform provider, it operates in a gray area of terms of service. Platform operators may alter the behavior of the /workspace directory, restrict outbound networking protocols required by Tailscale, or implement automated detection for unauthorized persistent daemons at any time. Consequently, while the proof of concept is functional, its durability as a reliable infrastructure component remains empirically unproven beyond short-term observation.

When the link between persistent networking in AI-provisioned environments and educational practice is examined, several theoretical implications emerge. Educational technology increasingly relies on sandboxed environments where students can experiment with code, deploy applications, and interact with AI agents without risking institutional infrastructure. ChatGPT Dots represents a paradigm where the AI model itself provisions and manages these computational environments. If educators or students utilize tools like dots-tailscale to establish persistent, private networks across these ephemeral virtual machines, the pedagogical affordances expand significantly. Students could theoretically maintain continuous, long-running projects—such as training small machine learning models, hosting persistent databases, or chaining multiple AI agents together—that require stable network endpoints despite the underlying hardware being routinely recycled by the platform.

However, this capability introduces complex challenges for instructional design and institutional security. From a cognitive load perspective, providing students with persistent infrastructure reduces the extraneous load associated with repeatedly configuring environments, allowing them to focus on germane cognitive processes related to computer science or data analysis. Yet, the ability to tunnel persistent SSH access out of a managed AI sandbox fundamentally alters the security boundary of the educational environment. Institutions that adopt AI-provisioned sandboxes typically rely on their ephemerality as a security control. A script that maintains a permanent network bridge to external devices bypasses this control, potentially exposing student work to external interference or allowing students to route unauthorized traffic through institutional AI subscriptions.

Moreover, this development highlights a broader tension in the integration of AI into technical education. As large language models transition from purely conversational interfaces to agentic systems capable of executing code and provisioning infrastructure, the distinction between the AI as a tutor and the AI as a hosting provider blurs. Educators must now consider not only how students interact with the AI's knowledge but also how they interact with the AI's computational substrate. The dots-tailscale script demonstrates that users will inevitably seek to impose permanence and external connectivity onto systems designed for transience and isolation. For teaching and learning with AI, this implies that curricula involving AI-provisioned computing must explicitly address infrastructure lifecycle management, the ethics of circumventing platform constraints, and the security implications of persistent networking in shared, ephemeral environments. Without such pedagogical framing, the technical capability to persist state in an AI sandbox risks becoming a vector for instability rather than a tool for sustained learning.

Source: I made a small script for running Tailscale in ChatGPT Dots

Read the original