-
Notifications
You must be signed in to change notification settings - Fork 3
plat 591
| Field | Value |
|---|---|
| State | deployed |
| Priority | P2 |
| Product | crew |
| Area | browser |
| Summary | Browser Start uses a moved Crew’s retained legacy browser key as its working directory, causing Directory does not exist for Ashutosh’s yami Crew on Excellence. |
Ashutosh's Excellence Crew yami-57c29c55 is registered at Crew/yami-57c29c55.
Its legacy alias is
_users/70ff7b0da57bee2bbf0c2e9719698e16/Chats/Work/projects/yami-57c29c55.
Start returned Directory does not exist for that old folder.
browserWorkspaceAccess returned browserProjectKey as the physical execution
folder. A moved Crew deliberately retains its old browser key to keep its
profile, cookies and tabs. That key is an identity, not a directory that still
exists after migration.
Resolve the authorized Crew path through resolveCrewPath for browser settings,
execution and folder grants. Continue using browserProjectKey to identify its
browser session, preserving the user's existing browser profile.
Verification: RUN_BROWSER_TEACH_E2E=1 go test ./cmd/server -run '^TestMovedCrewBrowserStartsRealChrome$' -count=1 starts real Chrome through the
real workspace shell handler with an absent legacy directory. Start succeeds
through both the current and old reference and returns the same browser session.
Restoring the old implementation reproduces the incorrect directory.
Existing browser authorization and moved-reference checks pass.
Verify Ashutosh's next browser Start on Excellence. The real Chrome regression passed locally; his next interactive server Start has not been observed.
Excellence release agents-99dc2842-20261006115535 records builder revision
99dc284251, which contains this fix. Public and agent health checks passed;
slot self-test completed with 156 passed, zero failed, 16 skipped.
Auto-synced from docs/ on main. Edit there, not here.