Keep control and keys in your environment
CLI, orchestration, safety policy, and reports run in your environment. Best for evaluating VOLY and individual work.
Install Local
Install the control plane, connect one provider, and begin with a dry-run. File changes are rolled back while the diff and run report remain available for review.
CLI, orchestration, safety policy, and reports run in your environment. Best for evaluating VOLY and individual work.
Install LocalOrganizations, members, hosted runs, and shared spend history live in the team dashboard.
Open CloudRun these commands in order from the directory where you want to keep the VOLY source.
Use a separate virtual environment so VOLY dependencies stay isolated from your projects.
Your shell is now inside the active .venv environment.
The editable install is convenient for core updates and includes the local dashboard dependencies.
The voly command is available in the current shell.
Copy the environment example, add at least one API key, and create voly.yaml. Agents cannot write to .env by default.
Status shows at least one available executor or provider.
Point VOLY at a test repository. The agent completes the task, but file writes are rolled back and the diff remains in the report.
The repository is unchanged; the result, touched files, and dry-run diff are saved.
Read the latest run in the CLI or start the local dashboard on port 7788.