Optional connected workflows are separate from Oneira's local motion-reactive expression. A responsible setup begins with one clear job, one low-risk account, and permissions the owner can understand and revoke.
Start with the smallest useful task
Choose one supported task and ask the external workflow to explain what it will do before granting access. Browsing, coding, and workspace changes are not current included product promises.
Build from simulation to limited action
First ask the agent to explain the proposed steps without acting. Next, allow read-only access on test data. Then enable one reversible write behind an explicit confirmation. Watch for hidden side effects such as notifications, billing, sharing, or downstream automation before broadening the account or tool set.
Create the stop path first
Know how to remove credentials, disable each connection, revoke tool access, and inspect recent activity. Set service spending limits and alerts where available. A Oneira interaction should never be the only control surface for a workflow capable of changing money, messages, files, access, or public content.
The short version
- Give each agent one explicit job and a written prohibition list.
- Progress from explanation to read-only tests to reversible writes.
- Keep independent revocation, logs, and spending controls.
Continue the buyer path