Choose the execution surface. Keep the client boundary.
Outloop is Workspace infrastructure for deploying and operating AI workers. The Workspace holds the intended client’s Context, approved accounts and resources, methods and work records. An API or browser is one way to carry out the work around it.
| Decision | API | Browser |
|---|---|---|
| Task fit | Structured reads and changes that the service exposes | Website workflows, visual inspection and tasks exposed in the UI |
| Operating requirements | Approved operations, resource identifiers, permissions and rate limits | Correct signed-in identity, approved target, session and page state |
| Possible interruptions | Provider errors, quotas, permission changes or unsupported operations | Expired sessions, authentication challenges, page changes or unavailable controls |
| Verification | Check the response and intended client result | Check visible state and the intended client result |
| Shared requirement | Approved access, correct client/account/resource and review before consequential changes | |
A real workflow can use both.
An AI worker may read approved data through an API, inspect a website, prepare a local file and ask a person to review the result. Use a supported path at each step. Reusing the method for another client still requires that client’s own account/resource configuration and validation.
See the recorded Webflow workflow for structured API work alongside browser editing and visual review. The campaign example below demonstrates its stated workflow, not universal recovery across every surface.
Browser identity depends on the mode.
Local Chrome: a Workspace uses its configured Chrome profile for supported work and Browser Login. Separate configured profiles provide separate browser environments.
Managed Browser: the mode uses a shared profile. Supported Browser Login recovery can restore an approved session and continue on the same task page. This is not separate browser-profile isolation for every Workspace.
In either mode, verify the intended account and resource as well as sign-in identity. One login can reach more than one client.
Authentication and review are part of execution.
Some authentication challenges and business decisions need a person. Continue after the required step is completed and verified, and check whether an interrupted action already produced a result before repeating it. Supported recovery does not guarantee that every task resumes automatically.
A refusal remains a refusal across tools. Recorded Google Ads and Meta proof shows configured approved requests succeeding and out-of-scope requests refused through Outloop.
The machine is a separate decision.
API and browser choice does not decide whether the model or execution runs locally or in the cloud. Outloop currently uses a company-controlled Mac for supported execution. Compare local/cloud access, persistence and workload economics.
Current execution scope · Reusable implementation for client Workspaces · Set up the first Workspace.
