Error message word-wrap breaks mid-word in terminal output

Long error messages that contain long paths or URLs appear to wrap mid-word, splitting tokens across lines in a way that is hard to scan.

Example observed today

⏺ Bash(sleep 25 && grep -E "ready|Local:|error when|Electron.*started|App ready"
      /private/tmp/claude-501/-Users-jbbrown-code-github-jb-brown-Prosponsive--claude-worktr…)
  ⎿  Error: Blocked: sleep 25 followed by: grep -E "ready|Local:|error when|Electron.*started|App ready" /private/tmp/claude-501/-Users-jbbrown-code-g
     ithub-jb-brown-Prosponsive--claude-worktrees-fix-commerce-gate-bypass/2d0618b6-fee8-48cd-bf32-de7af36adbbc/tasks/bkpa540qh.output head -10. To
     wait for a condition, use Monitor with an until-loop (e.g. `until <check>; do sleep 2; done`). To wait for a command you started, use
     run_in_background: true. Do not chain shorter sleeps to work around this block.

Notice github split as -g / ithub- at the wrap point. The error text is readable, but a path token broken mid-word looks like a different string and breaks scanability.

Expected

Wrap at word boundaries (whitespace, or on path separators like /, -, _) rather than inside an identifier.

Impact

Minor, but affects every long error/path rendered in the transcript. More pronounced on narrower terminals.

Environment

• Claude Code CLI (terminal rendering)
• macOS / zsh

Suggestion

Use a word-aware wrap (e.g. break only on whitespace, and if a token exceeds the terminal width, insert a zero-width break or explicit soft hyphen rather than a hard mid-character break).