Computer Use
A graphical desktop with a mouse and keyboard, for work that lives behind an interface with no suitable API.
Opulent can navigate applications, enter information, operate menus, capture screenshots, and record a workflow.
Use Computer Use when the work lives behind an interface, when an application has no suitable API, or when visual behavior is part of the result. A passing test cannot show whether a checkout flow, a dashboard, or a document layout works for a person. A short recording shows what the test cannot.
Boundaries
Computer Use operates under the same boundaries as any other tool. Before the first run, state:
- Which sites are in scope.
- What the agent may change.
- Whether files may move in or out.
- Which actions require approval.
Do not place readable credentials in the prompt or in working files. When login, a CAPTCHA, or sensitive entry is required, a person takes over for that step.
Proof after a consequential action
Require a screenshot, a recording, a system receipt, or a read-after-write check. The failure that costs most is a browser action that appeared to succeed and did not, because the next step builds on it.
If a site blocks the managed browser, the run should stop and route the exception rather than implying the action succeeded.
Session persistence
Browser-session persistence varies by connection and deployment. Confirm the boundary before designing a workflow that depends on staying logged in across runs, rather than assuming it and discovering otherwise on the third invocation.