Thanks for the report! This was fixed in v2.1.92.

Please:

1. Upgrade to the latest: claude update (seems like you did this already)

2. Start a new conversations (resuming an old convo may trigger this bug again in that convo)