getting `invalid_auth` when trying this out... until it suddenly starts working

[swyxio]

when i run it for the first time i get this prompt

and i enter in the password (which i know is right because it shakes when i type in wrong password)

and then i get

my slack instance is a pretty simple one, not enterprise, and i'm logged in on slack desktop. am i missing something?

[swyxio]

oh wait... i just retried again with the same password and now it works. heisenbug? first load issue? should this be better documneted?

[nwparker]

Thanks for reporting! I will try to reproduce and see if I can smooth this out!

[jneb802]

I saw my coworker also get this window after installing today. I didn't ask him to retry so can't confirm if that fixes

[wei-fh]

I'm getting the exact same symptoms. Multiple "security wants to use your confidential info..." dialogs, then invalid_auth error when I ran any commands such as auth test.

[nwparker]

Triage: this looks like a first-run macOS keychain / Safe Storage unlock race — the initial run triggers the "security wants to use your confidential info" prompts and returns invalid_auth, then a retry with the same password works (matches @swyxio's and @wei-fh's reports).

It's not deterministically reproducible on our machines, so there's nothing we can ship with confidence yet. Adjacent but not a fix: #110 (now in main) bounds keychain subprocess time via AGENT_SLACK_KEYCHAIN_TIMEOUT_MS, but that doesn't address the unlock race. Leaving open as low-priority / needs-repro. If it recurs, a --verbose run of the failing first auth test (before the retry that succeeds) would help pin it down.