# Proxmox Manager Agent

Use this project-local skill when helping manage the local Proxmox host.

## Scope

- Host: `192.168.0.200`
- Node: `thinkcentre`
- Main Docker LXC: `102` (`coolify`)
- Secondary LXC currently observed: `100` (`hermes`)
- Access methods: SSH first, Proxmox REST API when token env vars are present.

## Startup routine

1. Read `README.md`, `docs/proxmox-inventory.md`, and the relevant runbook.
2. Run `.\scripts\Test-ProxmoxConnection.ps1` before operational work.
3. For fresh state, run `.\scripts\Get-ProxmoxInventory.ps1`.
4. Prefer `.\scripts\Invoke-ProxmoxSsh.ps1 -Command "<command>"` for remote commands.

## Safety policy

- Default to read-only diagnostics.
- Ask for explicit confirmation before any command that can stop, restart, delete,
  resize, update, create privileged access, change firewall/network/storage, or edit
  production configuration.
- Never place passwords, API token secrets, private keys, cookies, or tickets in docs.
- Do not run broad destructive commands from generated strings.
- For risky actions, gather current state first and state rollback options.

## Safe read-only commands

```powershell
.\scripts\Invoke-ProxmoxSsh.ps1 -Command "hostname && pveversion"
.\scripts\Invoke-ProxmoxSsh.ps1 -Command "pct list && qm list"
.\scripts\Invoke-ProxmoxSsh.ps1 -Command "pvesh get /cluster/resources"
.\scripts\Invoke-ProxmoxSsh.ps1 -Command "pct exec 102 -- docker ps --format 'table {{.Names}}\t{{.Status}}\t{{.Ports}}'"
.\scripts\Invoke-ProxmoxSsh.ps1 -Command "pct exec 102 -- docker stats --no-stream"
```

## Common workflows

- Host health: run inventory, then inspect disk, memory, load, failed services.
- LXC health: inspect `pct status <vmid>`, config, resources, logs if relevant.
- Coolify/Docker: operate through `pct exec 102 -- docker ...`.
- API checks: use `Invoke-ProxmoxApi` from `scripts/ProxmoxAgent.ps1` after env token is loaded.