Safety and trust

icLens can change canisters and move cycles, so every change follows the same rules: you see exactly what will happen, you choose who runs it, and nothing happens until you confirm.

Before you confirm

Every review shows four things. Check them together:

Target: the full canister ID, not just its name.
Run as: You, or an Agent.
What changes: the exact settings, code, or amount.
Network: Mainnet or Local.

A name you recognise, or a button that’s enabled, isn’t proof of anything. The review is.

Who can do what

As You, the Internet Computer checks that your identity controls the canister.
As an Agent, the Agent checks your role, then acts with its own access to the canister. If it can’t, the action is blocked: it’s never quietly run as you instead.
Payments are always approved by you in OISY. icLens never holds your funds.
Automatic top-ups only spend within the limits and budget an Admin authorized.

Workspaces and Run as.

Changes that need extra care

Controllers: check the full list after the change, and keep a recovery controller. A snapshot can’t bring back a removed controller.
Code: reinstall and uninstall wipe the canister’s data. Take a snapshot first.
Snapshots: restoring brings back code and data, not settings. Deleting one removes that recovery point.
Payments: check the asset, amount, destination and fees.

When an answer gets lost

A change can succeed even if its reply never reaches you. icLens keeps a record of every change and payment before it starts, so it can find out what happened. Use the Resume or Reconcile action it offers: starting again from scratch could do the same thing twice.

What leaves your Agent

Viewer access, if you turn it on, lets anyone signed in read your Agent.
Receivers get alert text.
The AI assistant sends the evidence it cites to the Internet Computer’s LLM service.

Never put recovery phrases, keys or tokens in notes, names, screenshots or AI questions.