Day two of running a server is not deploying, it is operating: is it up, why is memory climbing, reboot it, back it up, start over from a clean image. All of that works from the chat once your assistant is connected, and the read-only parts are safe to hand over freely.
What you can do from the chat
- Read live status: power state, CPU, memory, disk, network and uptime
- Power actions: start, reboot, graceful shutdown or a hard stop
- On-demand backups, plus a list of what backups exist
- Reinstall from an OS template when you want a clean slate
Operate it
Find the server
Ask your assistant to list your services. Each VPS has a service id, and that is what every other action refers to.
Check the status first
Pull the live state before acting: power state plus CPU, memory, disk, network and uptime. This is read-only, so it is the part you can grant with nothing but a read scope.
Reboot or shut down
Ask for a reboot, a graceful shutdown or a start. Prefer the graceful shutdown, which signals the operating system to close down properly, over the hard stop that cuts power immediately.
Back it up on demand
Trigger a backup any time, then check the backup list until it shows as finished. Do this before any change you are not certain about.
A reinstall wipes the VPS and lays down a fresh OS template. Every file, database and configuration on the disk is gone, and there is no rollback. Before you ask for one: take a backup, confirm it actually completed in the backup list, and make sure anything you need is also stored somewhere off that server. Only then reinstall.
The graceful shutdown lets the system flush pending writes and close databases cleanly. The hard stop is the equivalent of pulling the cord: use it only when the machine is unresponsive and a graceful shutdown has already failed. Either one takes the server offline, so expect downtime for anything it serves.
Reading status needs very little. Rebooting, backing up and reinstalling sit behind the manage scope, which is also what allows spending. Grant it for the task at hand and revoke it afterwards: see connect your AI agent with OAuth.
A reinstall asks for a new root password. Generate a long random one in your password manager rather than reusing an old password, and never paste it into a shared chat log or a ticket.
Start now
Spin up an offshore VPS, connect your assistant with OAuth, or read the documentation.