Academy
8. Multi-Connection Awareness and Safety
Learn how @oupi coordinates several online connections across machines during missions, and apply safety best practices: scoped permissions, domain rules, opt-in controls, and revoking unused connections.
When you have several connections active — say the Chrome extension and OUPI Desktop on the same laptop, plus a Teams bot on your phone — @oupi is aware of all of them simultaneously. It knows which connections are online and on which machine. During a mission, it can coordinate across surfaces: for example, reading a local file through OUPI Desktop while using the Chrome extension to look something up on a website, all in the same workflow. If a connection that a mission needs is missing or offline, @oupi will tell you before proceeding, so nothing happens silently in the background.
Safety is built into every connection through four principles:
- Scoped permissions — Each connection can only do what its surface allows. The Chrome extension acts in the browser; OUPI Desktop controls screen, mouse, and keyboard; the Office add-in works inside documents. None of them exceeds its scope.
- Domain rules — Browser actions follow domain rules set by your organization, restricting where @oupi can act online.
- Opt-in controls — OUPI Desktop's agent control must be explicitly armed from the menu bar. While disarmed, nothing runs on your machine. Browser actions also require your permission.
- Revocability — Every connection can be disconnected or permanently revoked from "My connections" at any time.
Everything runs under your OUPI account with its existing permissions and credits.
Make it a habit to review "My connections" regularly. If you see a connection you no longer use — an old laptop's Desktop app, a browser extension on a shared machine — revoke it immediately. Stale connections are unnecessary risk. Pairing codes expire after five minutes and are single-use, so a code you didn't use in time is already dead.
OUPI Desktop has a visible arm/disarm toggle in the menu bar. Keep it disarmed by default and only arm it when you actively need @oupi to control your screen, keyboard, or applications. You can disarm it at any moment to instantly stop all agent-driven actions on your machine.
Credits are deducted from your single OUPI account regardless of which connection you use — whether it's the Chrome extension, OUPI Desktop, the Office add-in, Teams, Slack, or a device like the Orbe. There is no separate billing per surface. Your identity, knowledge bases, and memory also follow you across every connection, so @oupi's context stays consistent no matter where you interact with it.
Open "My connections" now. Check every listed connection: note its status and last-seen date. If any connection is on a machine you no longer use or a surface you've stopped needing, revoke it. Confirm that only the connections you actively use remain listed.
@oupi coordinates multiple connections across your machines during missions, automatically detecting what's online and where. Stay safe by relying on four pillars: scoped permissions per surface, organization-level domain rules for browser actions, opt-in arming for Desktop control, and prompt revocation of unused connections. All activity uses your single OUPI account's credits and permissions. Review "My connections" regularly to keep your setup clean.