How to use Claude to set up Headscale
Claude reportedly completed a long-postponed Headscale setup in three hours, requesting credential access and recording corrections, documentation and rollback points.
news.ycombinator.com
Suggested prompt
Suggested prompt written by Agents In Use, not the source author. Replace bracketed inputs and review tool permissions first.
Set up Headscale for [environment], accounting for [existing Tailnet-only SSH access]. Use [local documentation], request approval when credentials are required, log access, create rollback points, test corrections and record progress in [designated log].
Reach people exploring AI agents
See placements →Evidence at a glance
Sourced account- Source poster / publisher
- nemosaltat
- Original account
- Read the source ↗
- Published
- Source link checked
- Reported result
- The author reported that Claude completed the Headscale setup in three hours, including tested corrections, documentation, rollback points and searchable progress records.
- Human involvement
- Claude requested credential access when needed; the author could follow logged activity and Mattermost updates.
A linked account supports attribution. It does not mean we independently reproduced its result.
Report an issue with this case
Open correction emailOpens your email app with the case link included. Nothing is sent automatically.
How the agent did it
- Used the author's domain-specific local retrieval resources during the Headscale setup.
- Requested op access when credentials were needed and logged each usage.
- Corrected and tested mistakes, including region-setting errors.
The author had postponed setting up Headscale for years despite knowing how to do it. Tailscale already worked for them, and some assets had been hardened to accept SSH only from their Tailnet. That existing access arrangement was one reason they had avoided the task.
They reported letting Claude perform the setup while they worked on other things. Claude used domain-specific local retrieval resources that it had also helped build and maintain. When credentials were required, it prompted for access through op and logged each usage. The author described their own involvement as minimal and said the work took three hours.
The process included documentation, rollback points and propagation of learnings into the appropriate local resources. Claude made mistakes, including region-setting errors, then reasoned about them, corrected them and tested the corrections. Work was backed by Git, with progress posted to the author's Mattermost server for later searching. The post does not provide the deployment configuration or a detailed migration procedure.
Who it's for: Administrators delegating infrastructure backlog tasks while retaining credential-access checkpoints.
Prompt
Suggested prompt (written by Agents In Use, not the author's)
Source: Hacker News · nemosaltat
Frequently asked questions
How did Claude obtain required credentials?
The author says Claude prompted for op access when keys were needed and logged every usage.
Did the setup proceed without mistakes?
No. The author mentioned mistakes such as region settings, followed by reasoning, corrections and testing, with Git backing and progress updates.
More details
Remaining steps
- Recorded documentation, rollback points and learnings with Git-backed work and Mattermost updates.
About this account
The author delegated the setup while doing other work, reporting minimal involvement over three hours.
Platform: Hacker News. Attribution: https://news.ycombinator.com/item?id=48972669. Prompt: Suggested (written by Agents In Use, not the author's). Sourced by the Agents In Use pipeline.
Credit: nemosaltat on Hacker News
Source published
Added to Agents In Use
Source checked
Tools and topics
Claude · Headscale · op · Git · Mattermost
Headscale · Infrastructure · Delegation
Editorial completeness: 100/100. Measures documented fields, not agent performance or verified outcomes.