Update the CLI and reload the matching extension to apply changes. No Ego installation or native browser engine is required.
spaces open creates a minimized Chrome window in an explicitly selected connected profile. It reuses that profile's website sessions without copying cookies, passwords or profile files. A task window is not cookie isolation: tasks in the same profile share website login state and storage. The human continues in their ordinary window. Window creation or website-created popups can still interact with OS/browser behavior; this is not a guarantee of complete invisibility.
The bridge pins each space to its original extension connection and owner session. Disconnection, extension replacement, a moved page or loss of background debugging fails closed instead of selecting another browser. Multiple connected profiles require profileId for open and list. profiles lists connected extensions only, not every profile on disk. Ordinary unscoped legacy commands still use the selected primary extension.
open,list,status,pages: inspect owned tasks and their named pages.new-page: create a background page within the task window. Labels are stable task-local identifiers; DOM element refs still need fresh snapshots after page changes.adopt: explicitly adopt an authorized existing tab already in the task window. It never moves a human tab into the task window.release-page,close-page: return control or close a managed page. Closing user-origin pages needs explicit authorization; moved pages are protected.report: save a caller-supplied progress note.needsConfirmation:truepauses further actions.handoff,resume,stop: let the human inspect, explicitly return control, or terminate execution. Stopped or finished tasks cannot resume.finish: release debugging, optionally close only agent-created pages omitted fromkeep, and return retained/closed labels as a receipt. Default retains all pages; user-origin and moved pages remain protected.events: read a bounded lifecycle log including popup origin. This is not a full CDP or download-event stream. Popups are observed, not silently adopted; a popup outside the task window pauses execution.notifications: opt in to local system progress/review/completion notifications. Changed progress reports are delivered on a configurable interval (default five minutes, minimum one); unchanged progress stays quiet. OS notification settings still apply.
The extension popup and persistent BeatBrowser workspace sidebar share the same task state. The sidebar adds named pages, per-page View and activity history. Open it explicitly from the toolbar popup; background work never opens it automatically. Both surfaces expose View / take over, Confirm / resume and Stop. Focusing a running task window pauses subsequent automation. This does not undo in-flight input. Returning control is not blanket approval for future consequential actions.
Ended tasks offer Clear. Clear ended removes all finished/stopped task cards; Clear all asks for confirmation, stops active tasks and cleans all cards. Cleanup closes only agent-created pages still in their task window. Adopted, moved and explicitly handed-over pages remain open. It never closes a whole window with unrelated tabs. Failed page closures remain retryable. These controls belong to the human UI, not the agent command API.
Agent session titles are labelled Linked page: they identify that session's associated tab, not necessarily the active tab or an ongoing action. Ended tasks do not display stale pause instructions.
The default lease is 15 minutes; requested leases range from 30 seconds to one hour. Explicit resume renews for 15 minutes. There are at most four nonterminal tasks per owner, 16 pages per task and 80 retained lifecycle events per task. Task metadata is saved in chrome.storage.local and mirrored in session storage. Reload/update restores task labels, progress, history and completed states. Unfinished tasks restore paused; no interrupted input or submission is replayed. This is task recovery, not a durable job scheduler.
Tasks are managed entirely in the popup and sidebar, without Chrome tab groups. Recovery uses the native debug-target identity, saved task window and URL fingerprint; an old numeric tab ID or matching URL alone never grants ownership. An extension reload recovers the same live pages paused. A full browser restart creates new identities: labels, progress and history survive, while page associations require Reconnect pages and explicit Continue. Moved, replaced or navigated pages also stay unlinked when ownership is uncertain.
Version 1 archives migrate only when a uniquely named legacy task group and a unique URL fingerprint still prove the association. Proven pages are ungrouped after their native identity is saved. Renamed/user groups are preserved.
Reconnect pages lets the human explicitly select a current page for each missing label. Association does not run the task; a separate Continue is required. Manually associated pages are protected from cleanup. If a page closes while running, the task is interrupted rather than marked completed.
After a bridge/extension reconnect, the original agent calls spaces list in the selected profile to reestablish routing. A new agent session can inspect recovered tasks and, only after explicit user instruction, use spaces claim with userConfirmed:true. Claim changes ownership but leaves execution paused; resume remains a separate explicit action. Completed/stopped tasks cannot be claimed or resumed.
Records already lost before installing this recovery version cannot be reconstructed. Existing grouped pages remain available in Browser pages. Removing the extension or clearing its local storage removes the archive. Use Clear, Clear ended or Clear all to remove retained records.
Use the existing MCP or CLI spaces command with explicit spaceId and tabId. Node agents can use the JavaScript SDK, including named pages and waits for human control, URLs and popups. Existing page tools are reused. Ordinary input with no visible effect is not automatically repeated through another input layer. Write-request receipts include method/status only and do not prove business success. Frozen tabs can be thawed before dispatch; timed-out writes are never resent. Discarded, busy and confirmed-dialog states are distinguished. The optional Fast JEV loop has not been validated with TaskSpaces. Grok Bot and Muse have not individually undergone client acceptance in this change.
BeatGEO owns schedules and product run records. BeatBrowser executes assigned work and returns evidence. BeatAPI remains an optional capability layer for analysis, research and generation, not a prerequisite to ordinary local browser control.
Unit/transport tests cover ownership, multi-profile selection, page membership, moved/user-page protection, leases, progress, popup attribution and explicit human resume. An isolated real Chrome 153 headless fixture exercised two named pages, input, rendering beyond five seconds, confirmation pause, the actual extension popup's resume button, stop and screenshots. Headless tests do not establish foreground focus or macOS minimization behavior.
An earlier headed fixture observed unchanged human-window focus and selected tab, a minimized task window, background input and rendering. Its minimized screenshot failed. That gap remains: BACKGROUND_CAPTURE_UNAVAILABLE is returned after a bounded wait; the code does not restore/focus the window to obtain a screenshot. The headed test was not repeated after the keychain-prompt report.
The synthetic launcher defaults to headless, enforces a disposable OS-temp profile and uses --use-mock-keychain on macOS. Those settings never apply to everyday Chrome. No real keychain permission was granted and no user password/cookie extraction was added. Headless success does not prove a headed permission dialog has disappeared.
Existing upload and binary fetch/save paths were also exercised successfully inside the headless task fixture. Missing full Download/FileChooser contracts do not mean ordinary uploads/downloads are missing; native Chrome downloads can still show save UI depending on settings. See upstream review.
Remaining work: reliable minimized headed screenshot rendering; native-level focus/ownership interception; durable element references; uniform cross-origin-frame event handling; complete Download/FileChooser/dialog contracts; action-bound approval evidence; real signed-in model-site acceptance. Progress notes are not verified outcomes. A finish receipt reports page disposition, not proof a business action succeeded.
npm test
npm run check:syntax
npm run check:security
npm run check:package
BEAT_TEST_CHROME='/absolute/path/to/Chrome for Testing' node scripts/check-spaces-browser.mjs
BEAT_TEST_CHROME='/absolute/path/to/Chrome for Testing' node scripts/check-spaces-recovery.mjsThe recovery check actually reloads the test extension and restarts Chromium with its disposable profile, then verifies paused recovery, explicit resume, missing-page association and protected cleanup.
The browser check uses a private bridge and synthetic pages; it never imports personal login data. Set BEAT_TEST_HEADED=1 only for an intentional foreground-behavior experiment.
Ordinary agent pages and TaskSpaces keep their associations and controls in the extension without creating Chrome tab groups. Upgrades ungroup proven legacy task pages, preserving renamed groups and moved pages. Already closed groups saved by older Chrome sessions are separate from task records and may need removal in Chrome's saved-group menu. An unavailable page inventory is not an empty inventory: the workspace offers Retry and reload instructions instead of reporting zero pages.