Skip to content

Show one sign-in choice per account on the unlock screen - #2071

Closed
joepio wants to merge 1 commit into
developfrom
claude/project-thread-u8vgm0-duplicate-accounts
Closed

joepio wants to merge 1 commit into
developfrom
claude/project-thread-u8vgm0-duplicate-accounts

Conversation

@joepio

@joepio joepio commented Oct 5, 2026

Copy link
Copy Markdown
Member

Before: the "Continue as" list on the unlock screen could show the same email address twice, with nothing to tell the entries apart. Only one of them worked, and there was no way to remove the other.

After: once the app gets a signed-in account's backup from the server, older copies for that account are dropped from the device. If an address still shows up twice (for example on a device that is signed out right now), each entry says when it was saved and which identity it belongs to ("Saved 3/10/2026, identity …xwvuts"). An × next to every entry removes that copy from this device. Removing a copy does nothing to the account or to the backup on the server.

How: the device keeps encrypted backups in atomic.recovery.backups, one entry per agent. An account holds only one backup on the server, so an older identity of the same account stayed in the list after the newer backup replaced it. cacheRecoverySecret now also drops entries with the same owner_email. GettingStartedFlow adds the detail line and the forget button (forgetCachedRecoverySecret). The new test in recovery-fetch.test.ts fails without the fix.

Screenshots (desktop and mobile, two cached backups for one address) were taken from the running app. They are kept out of the repo and shared in the project thread.


Generated by Claude Code

A browser kept an old identity's encrypted backup next to the account's
newer one, so the unlock screen listed the same address twice and only
one of them opened. Caching a backup now drops older ones of the same
account (the server holds one per account). Where an address still
appears twice, each choice says when it was saved and which identity it
is, and every choice can be forgotten on this device.
joepio added a commit that referenced this pull request Oct 6, 2026
One tested commit for the open PRs of 5 October: link device to account (#1948), one profile form (#1953), faster branch runs (#1956), end-to-end encrypted conversations (#1971), passkey ceremony header (#1972), Flutter account package (#2035), cheap canvas undo (#2053), atomic.place tab title (#2056), table resource cell (#2057), small table fixes (#2058), storage map (#2061), Sync page cloud ladder (#2072), several served-domain suffixes (#2073), one sign-in (#2074), smaller chat messages (#2077), bring-along e2e fix (#2078), inline row data loss (#2079), Retry-After (#2080), #2070, #2071, #2066, #2067, #2068, #1969, #1887, #1897 and #1920.

Compressed stored values from #2077 stay readable, but a downgrade cannot read compressed rows.

Co-authored-by: Joep Meindertsma <joep@ontola.io>
@joepio joepio closed this Oct 6, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant