[FEATURE] Display plan file path when showing plans inline in convo history

Resolved 💬 2 comments Opened Feb 11, 2026 by danneu Closed Mar 11, 2026

Preflight Checklist

  • [x] I have searched existing requests and this feature hasn't been requested yet
  • [x] This is a single feature request (not multiple features)

Problem Statement

There's no way to see a plan's file path when rendered in convo history.

(i.e. when the plan is rendered first-class in this teal box)

$ claude -p "Plan to echo 'test' in bash"

⏺ Updated plan
  ⎿  /plan to preview
  ⎿  User rejected Claude's plan:
     ╭─────────────────────────────────────────╮
     │ Plan: Echo test in bash                 │
     │                                         │
     │ Context                                 │
     │                                         │
     │ Run a simple echo test command in bash. │
     │                                         │
     │ Steps                                   │
     │                                         │
     │ 1. Run echo test in bash.               │
     │                                         │
     │ Verification                            │
     │                                         │
     │ Command prints test to stdout.          │
     ╰─────────────────────────────────────────╯

❯ Excellent plan

Proposed Solution

When rendering a plan inline in convo history, always include the path to that plan file.

$ claude -p "Plan to echo 'test' in bash"

⏺ Updated plan
  ⎿  /plan to preview
  ⎿  User rejected Claude's plan:
     ╭─────────────────────────────────────────╮
     │ Plan: Echo test in bash                 │
     │                                         │
     │ Context                                 │
     │                                         │
     │ Run a simple echo test command in bash. │
     │                                         │
     │ Steps                                   │
     │                                         │
     │ 1. Run echo test in bash.               │
     │                                         │
     │ Verification                            │
     │                                         │
     │ Command prints test to stdout.          │
     ╰─────────────────────────────────────────╯
     Path: /Users/dan/.claude/plans/swift-drifting-forest.md 

❯ What if I wanted to do it in fish shell instead?

Alternative Solutions

_No response_

Priority

Medium - Would be very helpful

Feature Category

Interactive mode (TUI)

Use Case Example

I'm constantly getting claude code to formalize its ideas and approaches via the plan system. One benefit is that a plan file is super easy to exfilterate to other agents, review in my editor, etc.

However, there's no way to easily see paths for plans -- esp historical ones --, and to get the path to the current plan, I have to wait for claude to stop yapping so that I can query /plan (which I need to execute twice for some reason -- a bug on its own):

❯ What does this plan do?

⏺ The plan just runs echo test in bash — it prints the word test to the terminal. That's it.

❯ /plan
  ⎿  Enabled plan mode

❯ /plan
  ⎿  Current Plan
     /Users/dan/.claude/plans/swift-drifting-forest.md

Additional Context

_No response_

View original on GitHub ↗

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