Using Virillio Code
Permissions and approvals
Choose what the agent can do, and understand what you are approving.
On this page
Permission choices
Permission controls can allow a tool, block it, or ask you before it runs. Where available, open Settings → Permissions to inspect the defaults. Read the scope shown by the app before changing a rule.
| Choice | What it means |
|---|---|
| Allow | Permit the matching action under that rule |
| Ask | Request your decision before the action proceeds |
| Deny | Block the matching action |
Respond to a request
- Read the requested tool, command, file, or service.
- Check why it is needed for your task.
- Check whether it can write data or affect an external system.
- Approve only the scope you intend, or deny and explain an alternative.
Approving one useful action is not a reason to grant every future action broad access. If an operation seems unrelated, ask for an explanation before approving it.
Connected services
A plugin may ask you to sign in and grant access to another service. Review both the service’s authorization screen and Virillio’s tool approval. Disconnecting a plugin and revoking its access at the provider are separate controls.
If work is waiting
Look for a pending approval, sign-in request, or question. The agent may be waiting for you rather than still processing. If a tool is denied, either keep that boundary and choose another approach or intentionally update the relevant permission.