What happened
Matt Brewer’s page on teapawt displays a retweeted post by Vox describing a way to preview projects that are running on a computer from a phone. The post’s steps begin with installing Tailscale on both the computer and the phone and signing in to the same account. It says Tailscale can be used for free. It then suggests opening the project in Claude Code or Codex and asking the coding agent to run the project and provide a preview link.
The post’s main reusable detail is an instruction to save in AGENTS.md or CLAUDE.md. It tells the agent that whenever it returns a link to something running on that computer—such as a preview, review page, or dashboard—it should provide a Tailscale link rather than a localhost address. The instruction explains that the user works across several computers and a phone. It then directs the agent to publish the service with tailscale serve, open the link itself to check that it works, and only then send it to the user.
This is a workflow suggestion, not a claim that Claude Code, Codex, or Tailscale has added a new feature. It puts a network-access step and a verification step around the usual agent task of starting a project. The post does not specify a particular framework, operating system, port, or project configuration, nor does it provide a troubleshooting procedure. Its examples are previews, review pages, and dashboards, but it does not report a measured setup time or test results. The recommendation is to use the same pattern for links to services running on the computer.
The source presents Tailscale as the way to make the local service reachable and tailscale serve as the publishing command. It does not describe exposing the service to the public internet; the stated setup is for a computer and phone signed into the same Tailscale account. It also does not explain how the agent obtains permission to run the command or what confirmation the user should require before publishing a particular service. Those details matter when adapting the instruction to a team’s environment.
What the archive adds
We have not covered this before; it opens a new thread.
Trend signal
This does not yet fit a pattern New Runtime tracks. The example is a practical instruction for one local-preview workflow, but it does not establish a broader shift in how agent-ready software exposes capabilities, how runtimes enforce boundaries, or how teams structure agent systems.
Why it matters
A coding agent can start a development server and return a URL while still leaving the user unable to reach the result from the device they are using. Replacing localhost with a reachable address is a small operational step, but it closes the gap between “the agent says it is running” and “the builder can inspect it.” Requiring the agent to open the link before sharing it also makes verification part of the handoff rather than an assumption.
For teams, the pattern is useful because the instruction can live alongside the project instead of being reconstructed in each conversation. It may be especially convenient when a builder moves between a workstation and a phone. But a persistent instruction is not a security policy: it does not by itself decide which services may be shared, who may reach them, or what information a preview exposes. Teams should scope the practice to appropriate development services and retain human judgment over what gets published.
Limits and uncertainty
The post does not independently demonstrate the workflow or report tests across different operating systems, project types, or Tailscale configurations. It gives no latency, reliability, or setup-time measurements. Although it says Tailscale can be used for free, it does not spell out plan terms or whether every feature relevant to a particular setup is included. The scope of access to a published service, and any safeguards needed for sensitive previews, are not detailed. The suggested instruction asks the agent to check a link, but the post does not say how that check is performed or guarantee that it matches what a phone user will see.
Skill to build now
Take a development project that you already run locally and add a scoped instruction to its AGENTS.md or CLAUDE.md: when returning a link to a local preview, use the Tailscale address, publish it with tailscale serve, and verify that it opens before sending it. Try the workflow with a non-sensitive preview and check the resulting link from your phone. Keep the instruction limited to services you intend to share; do not treat a successful link check as approval to expose private data.
Reader takeaway
The reusable lesson is not merely to ask an agent to start a project. Specify how it should make the result reachable from your other devices, and require a link check before it hands that address back. Store that procedure in project guidance, then apply it only to previews that are appropriate to share.