Choose the plugin. Control its access.
Before a plugin runs, review what it needs and which actions it can take. You keep control of the actions that need a person’s approval.
Three things to review before installing.
1. What it needs
Accounts, credentials and other plugins it depends on.
2. What it can do
The actions it exposes, such as reading a file or posting a comment.
3. Where it connects
The outside services and hosts it requests access to.
Reading a file is different from merging code.
Each tool action has a rule: Allow, Ask or Refuse. Here are three defaults from the GitHub plugin.
You can adjust suggested rules. Actions marked as requiring approval always need a person. After installation, access settings live in the plugin’s Configure tab.
Use a published plugin or your own.
Install from the Hub, a Git repository, an uploaded bundle or a local folder.
Check oz0 Hub for published versions. Configure the plugin’s connections and model, where needed. Set a model budget, run a small task, then review its result and cost.
Updates are your decision
An installed version stays fixed until you update it. Updates go through compatibility checks; plugins with evals also run their test cases.
Before you connect real systems
- Install code you trust
- Plugins run code. How far they are isolated depends on the node and operating system.
- Read the limits
- Check where actions run
- Outside a sandbox, a tool can reach what the node’s user can. Approval rules do not replace isolation.
- Read the limits
- Check how credentials are handled
- Credential protection differs across node platforms and execution modes.
- Read the limits
Publishing your own plugin? See listing and README limits.