Provision a first cluster
You are starting a new project and want to open it in your browser at a real address with a trusted padlock, not at a port number.
You runaide init and then aide cluster create, from the project directory.
aide init --name myproject --domain dev.mycompany.io --ca-generate aide cluster create
Live reload through the real ingress
Your web front end is already running in the cluster. You want to change its pages and see the result at the same address, without rebuilding anything after each edit.
You runStart the dev server on 0.0.0.0, then aide route set-external portal --port 3000.
Stop, start and recover a cluster
You finish for the day and want to pause the cluster, then pick up tomorrow with your address and padlock still working.
You runaide cluster stop, later aide cluster start, then aide cluster status and aide cluster list.
Registered clusters NAME DOMAIN STATUS RUNTIME * myproject dev.mycompany.io running k3d staging staging.mycompany.io stopped k3d
Brief an agent on the cluster
You ask a coding agent to deploy to your local cluster, and it keeps guessing your domain and how traffic is routed.
You runaide prompt, and give the agent its output, or redirect it with aide prompt > AGENT.md.
aide prompt > AGENT.md
Check what is wrong
Something does not work, and you cannot tell whether the cause is your sign-in, a missing tool or the network.
You runaide doctor.