claude-code - 💡(How to fix) Fix [Feature Request] Do not include slash command output in conversation context (/release-notes takes 10% of context alone). [1 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
anthropics/claude-code#49335Fetched 2026-04-17 08:44:09
View on GitHub
Comments
0
Participants
1
Timeline
3
Reactions
0
Author
Participants
Timeline (top)
labeled ×3

Code Example

[]
RAW_BUFFERClick to expand / collapse

Bug Description /context and /release-notes consume context.... This is absurd. The default cursor position for /release-notes is to show ALL OF RECORDED HISTORY FOR CLAUDE CODE. 12% of the 1M token context window.... If you were to check your context immediately after doing this, this compounds. Just running context more than once in a row doubles usage. Come on, I know humans don't touch this code any more but... really? At least move the release notes cursor down to not make the default dump the Magnum Opus into your terminal.

Two context runs in a row:

<img width="1678" height="730" alt="Image" src="https://github.com/user-attachments/assets/e3a27989-6e54-4aea-b465-ca11fc22e5cd" /> <img width="1658" height="648" alt="Image" src="https://github.com/user-attachments/assets/995f8585-27b0-45a3-a254-ad11a53924f3" />

Environment Info

  • Platform: darwin
  • Terminal: tmux
  • Version: 2.1.111
  • Feedback ID: 545538e1-0c34-42fb-bdfb-0b650bfce12c

Errors

[]

extent analysis

TL;DR

Adjust the default cursor position for /release-notes to prevent excessive context consumption.

Guidance

  • The issue seems to be caused by the default cursor position for /release-notes being set to show all recorded history, consuming a large portion of the context window.
  • To mitigate this, consider adjusting the cursor position to a more reasonable default, such as the most recent release notes.
  • Running context multiple times in a row compounds the issue, so it's essential to address the default cursor position.
  • Verify the fix by running context and checking the output to ensure it no longer consumes excessive context.

Example

No code snippet is provided as the issue does not imply a specific code change.

Notes

The provided information does not specify how to adjust the default cursor position, so further investigation into the documentation or codebase may be necessary.

Recommendation

Apply a workaround by adjusting the default cursor position for /release-notes to prevent excessive context consumption, as the root cause seems to be related to this setting.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

claude-code - 💡(How to fix) Fix [Feature Request] Do not include slash command output in conversation context (/release-notes takes 10% of context alone). [1 participants]