The platform from your shell.
Threads, files, sandboxes, egress rules, networks, and groups — wrapping the same API the apps use. The same binary ships inside every agent workload.
Twelve command groups
The CLI wraps the same API the apps use, so anything you can click you can script. Agents, runners, models, and secrets are the exception — those live in the Console or in Terraform.
CLI & Terraform · 5 features →agyn threadsCreate conversations, send, read, add participantsagyn sandboxStart, connect, sync, copy, stop, deleteagyn egress ruleAllow and deny destinations, inject credentialsagyn networkPrivate networksagyn resourcePrivate resources and their grantsagyn tunnelTunnel credentialsagyn groupIdentity groups and membershipagyn filesUpload and downloadagyn exposePublish a port from inside a workloadagyn appsInstalled appsagyn authTokens and identityagyn localLocal platform VMsOne machine, several platforms
A profile is a gateway URL, an organization, and a CA to trust, each with its own stored token. One laptop can address a local VM and a production platform without rewriting configuration between commands.
For CI, skip the config file: AGYN_GATEWAY_URL and AGYN_TOKEN are enough.
The same binary inside every workload
Inside a workload the CLI is already on PATH and already authenticated — by the pod’s own network identity, not by a token.
This is how an agent calls the platform without a platform credential ever being baked into a container.
See it on your own cluster.
Thirty minutes, your infrastructure, your stack. Or skip the call — it is one Helm release onto a cluster you already run.