Noxgild Cloud Browser creates an isolated hosted browser session that an authorized AI client can use independently of your workstation. A live viewer keeps the session observable, while control can move explicitly between the agent and a human when protected interaction is required.
Cloud Browser is a separate execution surface from the Browser Worker on your own computer. Use it when the browser task should run in Noxgild-hosted infrastructure rather than depend on a local browser window.
The viewer exists so browser work is observable instead of disappearing into a hidden remote runtime. The backend remains authoritative for URL, page, session, and command state; the viewer is the human visual surface.
SESSION LIFECYCLE
Noxgild is designed to reuse a known active Cloud Browser session for follow-up actions instead of creating replacement browsers. Session identity, bounded lifetime, close state, recovery generation, and usage accounting are part of the durable backend lifecycle.
Create a hosted browser only when the task does not already have one.
Navigate, click, type, inspect, and continue inside that same session.
Move control to the human when direct interaction is required.
Close the backend session and release its compute when the task is finished.
When the session is human-controlled, the agent should wait for control to be returned rather than silently opening a replacement session.
CAPTCHA, OTP, passkeys, and other security challenges are represented as human gates instead of being bypassed automatically.
Hosted runtime has a bounded lifetime and production metering so browser compute can be accounted for instead of becoming an untracked background resource.
LOCAL BROWSER VS CLOUD BROWSER
Use the Browser Worker on your authorized computer when the task depends on that machine's existing signed-in browser session. Use Cloud Browser when you want a separate hosted browser that can run independently of the workstation.
Best for existing local sessions, authenticated dashboards, and workflows tied to your workstation environment.
Best for isolated hosted browser work that should not depend on your workstation browser being open.
WHAT WE VERIFY
Current product certification work has previously identified viewer typing and control-handoff issues in specific builds. Public claims should track the deployed, re-certified behavior rather than assume those issues are resolved.
A secure browser workflow sometimes requires a person to sign in, approve a prompt, or complete protected verification. Noxgild keeps that boundary explicit so the agent can continue afterward without pretending the protected step was automated.
