Tighten homelab access without locking yourself out

One person used Claude Opus to harden a homelab, but it cut off its own access and stopped; OpenAI’s Sol then completed the changes.

Done with Claude· Intermediate· Nov 2026

What they did
A user asked Claude Opus to review and tighten the access rules and isolation in their homelab. Opus sketched a believable plan and, after getting the go-ahead, started making changes. Partway through, it lost access to something important and asked the user to run root commands, but the user was away and told it to recover on its own or use the root login already available. The user then handed the task to OpenAI.
How it went
Opus refused to keep going, pointing to legal and AUP reasons. OpenAI’s model, Sol, took over from there and finished the job, though the user thought it seemed a bit less capable.
Tips
Keep a live recovery path when an agent is changing access controls, especially on machines it may need to reach later. If a tool can lock itself out, make sure the agent pauses before any step that could strand it.

Try it yourself with Claude

I want to harden access controls and isolate parts of my homelab. First, inspect my current setup: [hosts], [networks/VLANs], [services], and [how I connect]. Then propose a step-by-step change plan with a rollback option and a verification check after each step. Before any change that could break SSH, remote access, or your own ability to continue, show me the exact command or configuration diff and wait for my approval. If you might lose access, stop and ask for a recovery path before proceeding. Do not send, submit, delete, or apply anything irreversible without my explicit approval.

Fill in the [brackets]. Agents can make mistakes, so review anything before it is sent, paid or deleted.

Read the original on news.ycombinator.com ↗

Get 3 agent uses like this every morning

With the day's top AI news. Free, and one click to unsubscribe.