-
Notifications
You must be signed in to change notification settings - Fork 3
plat 574
| Field | Value |
|---|---|
| State | fixed on main |
| Priority | P2 |
| Product | browser |
| Area | browser |
| Summary | Browser settings exposes Copy connection code separately from account Reset; copying preserves live connections and the stable token. |
The connected Browser settings panel exposed Reset but no ordinary copy action. The owner needs to retrieve the same account connection code without revoking Code/Crew/workflow connections or making the panel wait for another pairing.
Add authenticated copy alongside pair and reset. It returns the existing
account token and server-derived project scope with the same product/owner/write
checks. Unlike pairing, it does not select the project or request an extension
connection. Reset remains the only action that rotates an existing token.
Copy intentionally uses PairForProfile to register/persist the current authorized
project on the account code. It is not read-only; it skips only the connection
request and never rotates the existing token.
The settings footer offers Copy connection code and a manual-copy fallback;
copying leaves the current Connected state intact.
The real server transport regression verifies the same token, unchanged Code connection, unselected Crew and absence of a connect-project frame. The browser panel regression verifies copy, clipboard contents and retained Connected UI. Focused server tests, panel tests and production frontend build passed.
Deploy the frontend/backend change to RTS; no credential migration is required.
Auto-synced from docs/ on main. Edit there, not here.