[BUG] Plan file paths render as relative paths (`.claude/...`), breaking Cmd+Click in Ghostty and macOS Terminal

Resolved 💬 4 comments Opened Jan 10, 2026 by coygeek Closed Feb 24, 2026

Preflight Checklist

  • [x] I have searched existing issues and this hasn't been reported yet
  • [x] This is a single bug report (please file separate reports for different bugs)
  • [x] I am using the latest version of Claude Code

What's Wrong?

When Claude Code generates a plan file, it displays the file location at the bottom of the interface. In Ghostty and the default macOS Terminal, this path is rendered as a relative path starting with a dot (e.g., .claude/plans/filename.md).

Because the path is relative, the terminal emulator does not recognize it as a valid file link. Consequently, holding Cmd (or Ctrl) and hovering over the text does not turn it into a hyperlink, and clicking it fails to open the file in the system's default markdown viewer.

In contrast, iTerm2 renders this path as ~/.claude/plans/..., which works correctly.

What Should Happen?

The file path displayed in the footer should be consistent across all terminal environments and formatted in a way that allows standard terminal "Cmd+Click" functionality to work.

To ensure broad compatibility, the path should always render as either:

  1. Home-relative: ~/.claude/plans/my-plan.md
  2. Absolute: /Users/username/.claude/plans/my-plan.md

Error Messages/Logs

There are no crash logs, but here is the specific output text difference observed across terminals:

**Ghostty & macOS Terminal (Fails):**

ctrl-g to edit in VS Code . .claude/plans/joyful-whistling-candy.md


**iTerm2 (Works):**

ctrl-g to edit in VS Code . ~/.claude/plans/harmonic-skipping-hinton.md

Steps to Reproduce

  1. Open Ghostty or the default macOS Terminal.app.
  2. Start Claude Code (claude).
  3. Enter Plan mode (or ask Claude to "create a plan" for a task).
  4. Wait for the plan to be generated.
  5. Look at the gray text at the bottom of the output (the status line indicating where the plan was saved).
  6. Hold the Command key (macOS) and attempt to click the file path string.

Expected: The cursor turns into a pointer, the text underlines, and clicking opens the file.
Actual: The text remains plain text and cannot be clicked.

Claude Model

None

Is this a regression?

Yes, this worked in a previous version

Last Working Version

_No response_

Claude Code Version

2.1.3

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

Terminal.app (macOS)

Additional Information

I tested this behavior across three different terminal emulators on macOS to isolate the issue:

  1. Ghostty: Shows .claude/plans/... (Not clickable)
  2. Terminal.app: Shows .claude/plans/... (Not clickable)
  3. iTerm2: Shows ~/.claude/plans/... (Clickable / Works as expected)

While the ctrl-g shortcut provided in the UI works to open VS Code, the inability to click the file path is a friction point for users who prefer using other markdown viewers or quick-look functionality.

View original on GitHub ↗

This issue has 4 comments on GitHub. Read the full discussion on GitHub ↗