How Operon keeps you in control: safety pauses, the vault and live view
Handing web work to an AI raises fair questions. Here is exactly when Operon stops and asks, how your logins are stored, and how you can watch and take over any run.
Letting software click around your portals is a real decision. This post explains, plainly, the controls Operon has and how they behave.
1. Safety pauses before anything final
Before Operon presses a button that makes something final, the run pauses and asks you. That includes actions like:
- Submit, Place order, Pay, Buy
- Finish or Confirm on the last step of a flow
- Delete or Remove
You see what it is about to do, then approve it or stop the run. If you stop, nothing is sent.
Some actions are deliberately not paused, because they are easy to undo and pausing on them would make every run tedious: opening pages, typing into fields, picking options, uploading a file into a form and reading results.
The pause is part of how runs work, not a setting the AI can decide to skip.
2. Logins in an encrypted vault
Most useful jobs happen behind a login. Operon keeps portal logins in a vault inside your workspace:
- Stored encrypted, never shown back in full.
- Filled in only when a run needs that site.
- Managed by workspace admins only.
Captchas and one-time passwords are never guessed. When a site asks for one, the run hands control to you; you complete it, then hand back.
3. Live view and take over
Every run streams live into your chat and the Computer view. The AI cursor shows where it is about to click or type, with a caption such as “Typing into Email”. You can go full screen, take over at any moment and hand back when you are done.
Afterwards, each run keeps a step-by-step record, so you can see exactly what happened.
4. Emails when it matters
Operon emails you when a run finishes, fails or needs you, including runs started by a schedule.
5. Your own AI key, if you prefer
By default Operon uses its own AI. Admins can add their own key for Groq, Gemini, OpenAI, Anthropic or OpenRouter, and runs in that workspace use it. Only the last four characters of a key are ever shown.
What this means in practice
The worker does the repetitive part: logging in, filling, uploading, reading. You keep the decisions that matter. Start with a read-only job, such as pulling a table into a CSV, to see how it behaves before giving it anything with a final step.
Questions about security? Email hello@vipanihq.com.