Reported as "he pressed yes ten times and it keeps asking". Several decks on
one computer share a config directory, so they start with one key; each read
the others' beacons as somebody wearing its name, took a fresh key, and wrote
it to the file the others read. The loop never settles, and every new key is a
new deck to everybody else on the network — so one machine sent a fresh pairing
request every few seconds and accepting one accomplished nothing, because the
deck that asked no longer existed by the time the answer arrived. Measured
here: six decks running on one Mac and ten `id-clash` lines in one session's
logs.

Decks on one computer recognise each other as the same machine now and leave
the key alone. The clash still worth healing is unchanged: a ~/.claude copied
to a second machine, where two real decks would otherwise be invisible to each
other.

And a failed round says what happened rather than what the syscall was:
`connect ECONNREFUSED 192.168.1.229:65059` was three wrapped lines in a 190px
column, carrying a code, an address and a port belonging to a machine whose
name is the first line of the same row. `not listening · last online 5m ago`,
with the sentence whole on the hover.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>