Skip to content

Security

The 0.8.4 runtime has Allow all enabled, prompt injection protection off, web search and history on, and the five per-category confirmations off. The plan is enabled in Preferences and keeps its own gate before the first actions.

Option Behaviour
Allow all Waives additional confirmations by risk; the corresponding controls become disabled. It does not remove protected-field or restricted-URL protection, nor the plan gate when the plan is active.
Prompt injection protection Analyzes suspicious instructions on the page, in the request and in attachments. Can block high risk or request review. It is configurable and is not infallible.
Allow web search Lets the provider’s search be used when the model/adapter supports it. May involve extra calls and costs.
Save conversation history Stores conversations on this device and enables the conversation manager. Changes apply after reloading the panel. Does not automatically delete existing history.

With Allow all off, you can enable:

  • Send/publish/buy/delete: operations classified as destructive or consequential.
  • Form submissions: confirmation before actions recognized as submissions.
  • Security changes: operations classified as security changes or sensitive input.
  • Cross-origin transfer: actions recognized as transfers between origins.
  • Navigation to a new domain: navigation to an unauthorized domain.

Classification is heuristic and depends on the tool and the target. It does not guarantee identifying every sensitive operation. Always check the site, the target and the consequences. Refusing does not undo actions already taken.

Add current domain lets you trust a domain to reduce confirmations for eligible actions. Review the list and remove domains that are no longer needed. Trusting does not allow filling protected fields nor bypassing URL restrictions. It does not imply prompt injection protection if you turned that option off.

The extension refuses automated interaction with recognized sensitive fields, including passwords, files and card fields. When needed, fill them manually and resume the flow. Browser-internal sites and extension stores may be blocked regardless of the options.

These protections do not guarantee screenshot anonymization. Before sending context from a private site, review Preferences and Privacy. To see these rules in action with practical examples, check the Prompt Injection Security & Demo Guide.