post: remote coding agents have the repo, not the machine — Tailscale bridges it#20
Open
clarkbw wants to merge 1 commit into
Open
post: remote coding agents have the repo, not the machine — Tailscale bridges it#20clarkbw wants to merge 1 commit into
clarkbw wants to merge 1 commit into
Conversation
… bridges it Lesson-driven post: a cloud agent session ships you the portable repo but never the running system. Names the two planes (driving the work vs. the running system), shows the per-host tailnet as the bridge, and points out the boat behind Starlink CGNAT is just the extreme point on the same line. All claims proven on the Studio (tailscale status, MagicDNS POC curl, jekyll build). Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
New engineering post (2026-06-16).
Lesson: a remote/cloud coding-agent session ships you the portable repo but never the running machine — so the moment you want to see the thing running (a web POC, a live LAN service, the boat Pi behind CGNAT), the sandbox is stranded. Naming the two planes — driving the work vs. the running system — is the insight; a per-host tailnet is the bridge.
Proven, not asserted (all on the Studio):
hostname→studio.localtailscale status→ studio, homeassistant, iphone181, naturalaspi all upcurl http://studio.tailb19444.ts.net:8911/→ served a test POC over MagicDNSbundle exec jekyll build→ renders clean at/remote-coding-agent-has-the-repo-not-the-machine-tailscale-bridge/Framework-general, ~750 words, two real command blocks — same shape as the existing posts.
🤖 Generated with Claude Code