Keep active sessions separate from agent work
An ordinary browser tab inherits whatever accounts, cookies, extensions, and unfinished work already live in that profile. A Browser Task Space starts from an Axiom-owned context instead, so a research or web-action task does not have to borrow the browser window the user is actively navigating.
The separation is architectural rather than cosmetic. Task identity, browser profile identity, allowed origins, and lifecycle state travel together so one task cannot silently become another task’s browser session.
Background browser work stays in its own Task Space. The user’s current browser remains theirs.
Choose a disposable or continuing context
An ephemeral profile is appropriate for one-off research and tasks that should not retain a session. A persistent profile can continue an explicitly chosen workflow across runs. The mode belongs to the Task Space rather than being inferred from whichever browser happened to be open.
Persistent does not mean unrestricted. The task still has an allowed-origin list and a distinct lifecycle that can be shown, handed off, reclaimed, or cancelled.
- Ephemeral contexts for disposable work
- Persistent contexts for deliberate continuity
- Separate ownership for concurrent tasks
- Cancellation tied to the exact owned browser process
Take control without losing ownership
Some tasks eventually need a human decision: sign in, review a purchase, resolve a challenge, or inspect the current page. Axiom can show the Task Space and hand control to the user without pretending the automated task has finished.
When control returns to Axiom, the broker checks the same Task Space identity and generation. A stale or replaced browser cannot quietly answer for the task that originally created it.
Recovery is a product state, not an invisible retry loop
Managed browsers can close, crash, or be replaced. Axiom records the task state needed to explain whether the context can resume, requires a new browser, or should be cancelled. Recovery does not mean attaching to an arbitrary open browser.
Distribution packages are verified before use, and browser ownership is proven before Axiom stops a process. Those boundaries keep recovery from becoming a reason to interfere with unrelated browser sessions.
What a Task Space does not promise
A Browser Task Space does not bypass website authentication, anti-bot controls, account permissions, or the user’s responsibility for consequential actions. It provides a cleaner execution boundary, not special access to a service.
Provider behavior and browser compatibility can change. Axiom should present the current task state and available recovery instead of promising that every website can be automated.
Common questions
Does Axiom use my normal browser profile?
Browser Task Spaces use Axiom-owned browser contexts rather than silently borrowing the profile you are actively using.
Can I take over a browser task?
Yes. A Task Space can be shown and explicitly handed to the user, then reclaimed by Axiom when the task continues.
Can a browser task stay signed in?
A persistent Task Space can retain an explicitly chosen session. Ephemeral Task Spaces are intended for disposable work.