fix(computer-use): recover verified stale Chrome profile locks - #1809
Draft
briar-workflow[bot] wants to merge 1 commit into
Draft
fix(computer-use): recover verified stale Chrome profile locks#1809briar-workflow[bot] wants to merge 1 commit into
briar-workflow[bot] wants to merge 1 commit into
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Computer Use Chrome can remain blocked by singleton links after a browser crash or a stopped container is replaced. The launcher now reuses responsive Chrome through cookie- and peer-checked IPC, serializes requests per display profile, and removes only singleton links when recorded process identity or verified container retirement proves the owner has exited. Unknown ownership and unresponsive browsers return errors without deleting profile data or killing browsers.
Container replacement grants recovery authority only after removing the exact stopped Briar container and verifying an exclusively attached ordinary local profile volume. Cookies, saved passwords and shared-login synchronization remain intact. Embedded sandbox assets are regenerated from the launcher source. The IPC packet regression verifies there is no trailing NUL or empty argument.
Validation: 16 Python recovery/IPC/concurrency tests, 51 focused TypeScript tests, generated asset parity, managed image source validation, shell syntax and diff checks passed. Full local CI passed in 172 seconds with VITEST_MAX_WORKERS=2 (all four contexts). The first run hit a transient empty-archive failure in the existing login-export test; the complete retry passed, including all 2,867 unit tests. All four required signoff statuses were subsequently published as success for dbc82e5 through the project GitHub App (ci:signoff passed in 17 seconds). Real Linux Chrome startup, crash/restart/recreation and login persistence checks plus base-image rollout remain required; Docker and an approved Linux deployment target are unavailable on this worker. Runtime-only updates do not install this launcher.
Briar issue: https://briar-api.wbai.workers.dev/open/issues/4947dcf7-694e-4a0e-b702-ac9ce562b018/c33ba5a9-5bd1-5d34-956c-7df66ad2f961