| name | vps-server-management |
| description | Use when David wants to manage his VPS servers and the AI agents running inside them — connecting, deploying, monitoring, restarting, and operating remote hosts and their agents. Triggers on VPS, server management, remote host, SSH into server, manage my servers, agents on the server. |
VPS Server Management
Source of truth: docs/infrastructure.md or the user's private infrastructure inventory (read it for the latest — IPs/expirations change).
Servers (VPS) — example inventory
| Hostname | IP | OS | Purpose | Expires |
|---|
| example-app | <SERVER_IP> | Ubuntu 24.04 | App hosting | <EXPIRY_DATE> |
| example-automation | <SERVER_IP> | Ubuntu 24.04 | Workflow automations | <EXPIRY_DATE> |
| example-agent | <SERVER_IP> | Ubuntu 24.04 | Agent gateway | <EXPIRY_DATE> |
SSH as root@<IP>.
Access levels (never share higher than needed)
- App login — e.g.
app.example.com. Build/edit workflows, no server access. Safest to share.
- VPS SSH —
root@<IP>. Docker, files, system config. Trusted technical people only.
- Hostinger hPanel —
hpanel.hostinger.com. Billing, reboot, OS reinstall. Exposes SSH creds + browser terminal, so it grants server access too. David only.
Managing a VPS via an agent
When using an AI agent to manage a VPS, SSH into the box first and launch the agent ON the VPS (e.g. codex --yolo), then talk to that local-on-server agent. This is much better than running an agent locally and telling it to SSH per-command — the on-box agent has full filesystem/process context and avoids fragile SSH round-trips.
Agents on servers
- App host → example-app (managed via Dokploy or equivalent).
- Agent gateway → example-agent. Setup/config docs in
library/agent-gateway/.
- Automation server → example-automation.
