Security
Control access to secrets, files and agent settings.
Enable the protections you need. Depending on the rule, ClevAgent warns, pauses, or blocks supported actions.
Sensitive info protection
API keys, access tokens and private credential files need care when an agent reads or sends them.
With Security Mode on, ClevAgent blocks recognized secrets from being sent to the model and pauses identified private credential reads for approval.
Unsaved work protection
A cleanup or reset can erase changes that have not been saved in Git.
ClevAgent checks the files at risk and pauses supported destructive cleanup. You can review the affected files before deciding.
Agent settings protection
Settings can change what an agent can access or do automatically.
Writes to agent settings files pause for your approval. You see the paths, not the contents.
Persistent access protection
Some changes can keep scripts running or preserve access to your computer.
ClevAgent pauses writes to protected startup files and other settings that can preserve access. You decide whether to allow the change.
Dangerous commands
Some commands can erase files or make large changes that are hard to reverse.
Recognized risky commands are blocked for review. You can allow a specific action when approval is available, or refuse it.
Agent cursor
When your agent uses its own cursor on your Mac, some clicks and keystrokes are hard to undo.
Before the agent's cursor pays, deletes, sends, types a password, changes a setting, approves a ClevAgent card or runs a flagged terminal command, ClevAgent shows a card. You allow that one action or block it.
Unchecked requests
Some requests and replies are too large or too unusual for ClevAgent to check.
If ClevAgent can't check an agent's reply or a step it is about to take, your agent pauses and you decide. A request it can't check goes through and is listed in Activity.
Outside-folder changes
An agent ClevAgent can't check can still change files outside its work folder.
In Auto and Full, ClevAgent pauses that agent before a recognized change outside its work folder. You approve or block each change.
Cleva
These rules apply to agent actions through Cleva.
If payment details or deletion targets are unclear, the action stays blocked for you to review.
Payment review
A final payment or subscription action should stay under your control.
When Cleva detects a final payment or subscription action, ClevAgent holds it for your approval. Approval covers that specific action once.
Reviewing deletions before they happen
Deleting data or closing an account should be a deliberate decision.
When Cleva detects a deletion or account-removal action, ClevAgent holds it before proceeding. You can approve that specific action once or refuse it.