# Yeah, I gave it access to my email

> Source: <https://forum.level1techs.com/t/yeah-i-gave-it-access-to-my-email/260970#post_2>
> Published: 2026-11-21 22:03:56+00:00

**Recommendation:** Scope the agent with an llm.txt that requires harness and service confirmation, read-only node inspection, a per-service plan with installer links, explicit approval, one-at-a-time installs verified by a real request, and documented undo steps.
More in the playbook "Designing agent systems": <https://wpnews.pro/playbooks/agent-architecture>

llm.txt

```
Help me build a Proxmox homelab similar to this Level1Techs guide: https://forum.level1techs.com/t/yeah-i-gave-it-access-to-my-email/260970 . Use the author’s earlier config post as the starting point: https://forum.level1techs.com/t/253398 . Where the posts differ, follow the newer guide. Adapt it to my hardware; don’t copy the author’s network settings. 1. Ask me: “Which coding harness do you want to use (Pi, OpenCode, Claude Code, Codex, or another)? Which services from the guide do you want?” 2. Ask which Proxmox node to use and how to authenticate. Use an existing SSH alias or a scoped credential from my secret store. If I need to sign in, have me do it locally. Never ask me to paste passwords, tokens, or private keys into chat. 3. Check the node version, available resources, storage, bridges, and existing guests read-only. Show a short plan mapping each requested service to a new guest or an existing service to reuse. Link its installer from https://community-scripts.org/scripts . Flag anything without a matching script, including hardware-specific setup. Wait for my approval. 4. Inspect each selected installer and its dependencies before running it. Install one service at a time, keep it private, and verify it with a real request before moving on. Don’t overwrite guests or change host networking. If a step fails, stop and report what changed. Finish with access instructions, test results, and how to undo the new installs.
```
