A shell-capable agent can use Jio through the same CLI as a developer. Jio does not currently publish an MCP server or installable agent skill.
Prepare Jio
Install the CLI and authenticate with an operator-issued key:
curl -fsSL https://github.com/jiovannish/client/releases/latest/download/install.sh | sh
jio login '<your-api-key>'
jio usageFor non-interactive environments, set JIO_API_KEY instead of saving a login. Give
each automation environment the narrowest account access available.
Choose an integration
| Agent | Current path |
|---|---|
| Codex | jio yolo codex [session-id] |
| Any terminal agent | Connect with jio connect, then install and run it in the VM |
| CI or job runner | Use non-interactive create, exec, and destroy --yes |
| MCP client | No supported Jio MCP endpoint yet |
Codex onboarding
jio create
jio yolo codexThis transfers the local Codex login into the VM and starts Codex in /workspace
with its approvals and sandbox disabled. Use jio login codex if you want to
transfer the login without launching it.
Generic agent onboarding
jio create
jio connectInside the VM, install the agent and clone or upload the project using your normal workflow. When finished, exit and clean up from the local machine:
jio destroy --yesDocumentation for agents
The machine-readable documentation index is available at /llms.txt.
Point an agent there when it needs to discover the current Jio guides and concepts.
Security boundary
- A shell agent can read credentials available inside its VM.
jio yolo codexgrants full access within the VM.- The trusted Jio host operator can inspect guest data.
- Local VM SSH credentials are required to connect; an API key and VM ID alone are insufficient from another client machine.
- Destroy sessions that no longer need to exist.
Continue with Coding agents for the hands-on flow.