Optimization
Keep work focused and easier to maintain.
Reusing content already read
When an agent asks for content it has already read, ClevAgent checks whether that content is still reusable.
For clear, substantial repeats, it can interrupt and redirect the agent to existing context. Smaller overlaps get guidance; uncertain cases stay quiet.
Reusing recent edits
Recent edits can be reused without another full read.
After a repeat read, ClevAgent reminds the agent to reuse unchanged content it just wrote.
Keeping useful files easy to find
Notes and reports are more useful when they have a clear place in your project.
ClevAgent suggests a suitable location for newly created work files. It does not move files automatically.
Keeping growing code manageable
Large code files can make new work harder to follow.
ClevAgent guides new logic into smaller units where practical. It favors a small local edit when splitting would add risk or unnecessary work.
Keeping Claude project memory useful
Useful project memory should stay easy to find and reuse.
ClevAgent checks Claude memory for growth and repeated notes. Small duplicate cleanups can prompt the agent automatically; broader cleanup suggestions wait for you to send them.
Keeping document folders organized
Crowded folders make useful documents harder to find.
After files are added, ClevAgent can suggest an organization review. You choose whether to send it; the rule does not move or delete files itself.
Following up on missing checks
A finished coding task should include the checks relevant to its changes.
At task completion, ClevAgent can ask the agent to run missing checks, using recorded results for the latest changes. Checks already running are left alone.
Breaking repeated failure loops
Retrying the same failed step without progress can leave a task stuck.
Repeated failures trigger guidance to investigate the cause or change approach. Code failures and environment problems get different advice.
Reading the relevant part of a large file
A focused question may need one section rather than an entire large file.
After a large full-file read, ClevAgent encourages reuse and focused reads for the next step. Explicit requests to review the whole file are respected.
Security
Control access to secrets, files and agent settings.
Turn on a protection to pause the actions it recognizes. If an action cannot be safely approved, it stays blocked.
Protecting secrets
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.
Resisting hidden instructions
Webpages and tool results can carry instructions that try to redirect your agent.
ClevAgent holds detected attempts from supported external sources before they reach the model. You can allow the request or refuse it.
Protecting recent work
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.
Keeping control of agent settings
Settings can change what an agent can access or do automatically.
Recognized writes to protected Claude and Codex configuration files pause for your approval. The affected paths are shown without exposing file contents.
Controlling startup and background changes
Some changes can keep scripts running or preserve access to your Mac.
ClevAgent pauses writes to protected startup files and other settings that can preserve access. You decide whether to allow the change.
Stopping destructive 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.
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.
Reviewing payments before they proceed
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.