[BUG] Text Wrapping Breaks Hyperlink Functionality in Terminal Output

Status Closed — not planned
Maintainer reply None cached
Activity 8 comments · opened Mar 24, 2025 · closed Jan 6, 2026

Bug Description
Normally in my terminal when there is a long URL string I'm able to hover it and click on it. However when code outputs a longer URL it is unfortunately wrapped and that wrapping is splitting the URL into two pieces.

This means only the first part of the URL is clickable which of course makes the URL invalid. This is not an issue in my terminal as I have performed by echoing out along URL and it wraps correctly and the full URL is clickable.

Example:
!Image

Environment Info

  • Platform: linux
  • Terminal: gnome-terminal
  • Version: 0.2.53
  • Feedback ID: 34b8066e-c97c-4714-94da-9d4a2f5f6d84

Errors

[]

Normal url output

Note the underline continues onto the second line meaning the full URL is clickable.
!Image

URL output in Claude Code

Note the URL breaks at the end of the first line.

!Image

The refusal and that it checked the date first before we continuing is also.... interesting. But that's a bit off topic.

View original on GitHub ↗

8 Comments

gworley3 · 1 year ago

It's not just URLs, but lots of text that I might need to copy-paste out. Claude Code seems to set its own margins, which it manages manually by inserting spaces, and this also breaks for example commands I want to copy-paste to run. I frequently run Claude Code in a tmux window that's side by side with code and other terminal windows and this gets really annoying to patch the commands back together manually, making Claude Code very hard to use for infra/devops work where I don't want to trust Claude to run the commands itself since some of them make changes to production infrastructure.

github-actions[bot] · 10 months ago

This issue has been inactive for 30 days. If the issue is still occurring, please comment to let us know. Otherwise, this issue will be automatically closed in 30 days for housekeeping purposes.

gerrywastaken · 10 months ago

This issue still exists. I find I'm getting notifications via the above bot 30 days from when I first opened a ticket. Due to opening a lot of tickets on various days that means this bot essentially spams me now. :/ This is less than ideal. I hope this is temporary. Having to reevaluate bug reports every 30 days when they have not received an official response to the intial report will make it so that people are less likely to want to leave a report.

I get that you have a huge backlog; I just feel that maybe Claude could test if the issue still exists instead of asking me? The video proves that it is the Claude CLI that breaks URLs as just echoing them in the normal CLI doesn't result in a broken url. So it seems there could be a way for Claude to test if this is still an issue?

https://github.com/user-attachments/assets/f012032c-b71a-4d47-96d0-82e026607078

---

Just in case I need to reevaluate next month. Here is the prompt for future Gerry:

I'm trying to demonstrate a bug for Anthropic. Please just echo out this URL: "https://github.com/anthropics/claude-code/issues/609#issuecomment-3619850951" 
gerrywastaken · 10 months ago

I also just noticed that urls have lost the blue highlight they used to have when I fist created this bug report. I wonder if that was a mistake. I find the dark urls less readable, but I guess it does kind of hide this bug.

github-actions[bot] · 9 months ago

This issue has been automatically closed due to 60 days of inactivity. If you're still experiencing this issue, please open a new issue with updated information.

gerrywastaken · 9 months ago

Hey what! We never got a warning!

gerrywastaken · 9 months ago

Luckily it seems it was actually fixed... so 🤷

<img width="628" height="526" alt="Image" src="https://github.com/user-attachments/assets/f65e5b22-60b1-423a-ac61-af060929d99e" />

github-actions[bot] · 9 months ago

This issue has been automatically locked since it was closed and has not had any activity for 7 days. If you're experiencing a similar issue, please file a new issue and reference this one if it's relevant.