Go into your settings, turn the entire dispatch feature off, refresh the claude app instance (command + R works), and then turn it back on. It will catch up to your pending messages. I would not be surprised if this bug is the same as when you use claude code in a terminal and perform an update and the session hangs. A quick fix to get back in is to just --resume in a new session with the ID. Another Tip: If you need the ID, just hit esc to get the session ID for that session. Another Tip: If your claude code session needs to use --chrome, but for some reason it disconnects (lol always), press esc to get the session ID if you want or just go into a new terminal instance, claude --chrome, then /resume. submitted by /u/Rotatos
Originally posted by u/Rotatos on r/ClaudeCode