claude-code - 💡(How to fix) Fix [Bug] Text-to-Speech reads record symbol "⏺" as "Record Media Symbol" instead of being silent

[{"error":"AxiosError: Request failed with status code 401\n at XU (/$bunfs/root/src/entrypoints/cli.js:110:1194)\n at <anonymous> (/$bunfs/root/src/entrypoints/cli.js:115:12736)\n at emit (node:events:92:22)\n at endReadableNT (internal:streams/readable:865:50)\n at processTicksAndRejections (native:7:39)\n at request (/$bunfs/root/src/entrypoints/cli.js:117:2467)\n at async sc1 (/$bunfs/root/src/entrypoints/cli.js:3084:14667)\n at async Ee9 (/$bunfs/root/src/entrypoints/cli.js:3084:15206)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-04-20T09:52:53.073Z"},{"error":"AxiosError: Request failed with status code 401\n at XU (/$bunfs/root/src/entrypoints/cli.js:110:1194)\n at <anonymous> (/$bunfs/root/src/entrypoints/cli.js:115:12736)\n at emit (node:events:92:22)\n at endReadableNT (internal:streams/readable:865:50)\n at processTicksAndRejections (native:7:39)\n at request (/$bunfs/root/src/entrypoints/cli.js:117:2467)\n at async sc1 (/$bunfs/root/src/entrypoints/cli.js:3084:14667)\n at async Ee9 (/$bunfs/root/src/entrypoints/cli.js:3084:15206)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-04-20T09:52:53.105Z"},{"error":"AxiosError: Request failed with status code 404\n at XU (/$bunfs/root/src/entrypoints/cli.js:110:1194)\n at <anonymous> (/$bunfs/root/src/entrypoints/cli.js:115:12736)\n at emit (node:events:92:22)\n at endReadableNT (internal:streams/readable:865:50)\n at processTicksAndRejections (native:7:39)\n at request (/$bunfs/root/src/entrypoints/cli.js:117:2467)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-04-20T12:38:00.029Z"}]

TL;DR

The issue can be mitigated by configuring the Text To Speech settings to correctly pronounce the "⏺" symbol.

Guidance

• The reported error messages indicate Axios errors with status codes 401 and 404, but the primary concern is the incorrect pronunciation of the "⏺" symbol.
• To address the pronunciation issue, add a custom pronunciation rule in the Read/Speak Settings, such as ⏺ => *, as the user has already done.
• Investigate the Axios errors separately, as they may be unrelated to the pronunciation issue.
• Verify that the custom pronunciation rule resolves the issue and does not introduce any other problems.

Notes

The provided error messages do not directly relate to the pronunciation issue, so it's essential to address these errors separately to ensure the overall system functions correctly.

Recommendation

Apply workaround: Configure the Text To Speech settings to correctly pronounce the "⏺" symbol, as this has already been shown to resolve the primary issue reported by the user.