Problem
When the Local Proxy has no saved credential, Start creates an API key named maple-desktop-YYYYMMDD. Signing out scrubs the local proxy credential, but manual proxy keys are not tracked and revoked with the Agent proxy keys.
If the same account signs back in on the same UTC day, Start finds the existing name and stops. The old secret cannot be revealed again, and the Local Proxy UI has no way to select it, so setup cannot recover without deleting the remote key or waiting for a new day.
Expected behavior
Local Proxy setup should recover after logout without becoming blocked and without accumulating orphaned API keys.
Suggested direction
- Give auto-created manual proxy keys collision-safe names.
- Track their ownership and exact names.
- Revoke or clean them up during reset, logout, and failed setup where appropriate.
- Add a regression test for start, logout, same-account login, and restart.
The timestamp-only naming change explored in PR #652 would bypass the collision but would not solve credential lifecycle or orphaning, so this should be handled separately.
Problem
When the Local Proxy has no saved credential, Start creates an API key named maple-desktop-YYYYMMDD. Signing out scrubs the local proxy credential, but manual proxy keys are not tracked and revoked with the Agent proxy keys.
If the same account signs back in on the same UTC day, Start finds the existing name and stops. The old secret cannot be revealed again, and the Local Proxy UI has no way to select it, so setup cannot recover without deleting the remote key or waiting for a new day.
Expected behavior
Local Proxy setup should recover after logout without becoming blocked and without accumulating orphaned API keys.
Suggested direction
The timestamp-only naming change explored in PR #652 would bypass the collision but would not solve credential lifecycle or orphaning, so this should be handled separately.