claude-code - 💡(How to fix) Fix Feature request: Hide individual built-in slash commands & show effort level in status line [2 comments, 2 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#47722Fetched 2026-04-15 06:44:08
View on GitHub
Comments
2
Participants
2
Timeline
6
Reactions
0
Author
Timeline (top)
labeled ×3commented ×2closed ×1
RAW_BUFFERClick to expand / collapse

Feature Request

1. Allow hiding individual built-in slash commands

Currently, / autocomplete shows all built-in commands. Users who don't use certain commands (e.g., /stickers, /mobile, /passes) find them cluttering the list.

Custom skills support user-invocable: false to hide from the menu, but there's no equivalent for built-in commands. --disable-slash-commands disables everything, which is too aggressive.

Proposed: A setting like "hiddenCommands": ["/stickers", "/mobile"] in settings.json to hide specific commands from the autocomplete list.

2. Show effort level in the status line

The current effort level (low/medium/high/max) is not visible in the status line. Users have to run /effort without arguments to check. It would be helpful to have an option to always display the current effort level in the status line, either as a built-in status line variable or via the custom status line configuration.

extent analysis

TL;DR

Implement a setting like "hiddenCommands": ["/stickers", "/mobile"] in settings.json to hide specific built-in slash commands from the autocomplete list.

Guidance

  • To address the first feature request, consider adding a hiddenCommands array to the settings.json file, allowing users to specify which built-in commands to hide.
  • For the second feature request, explore adding a built-in status line variable or a custom status line configuration option to display the current effort level.
  • Investigate the feasibility of implementing these features without disrupting existing functionality or introducing compatibility issues.
  • Review the custom skills user-invocable: false functionality to understand how it hides commands from the menu and apply similar logic to built-in commands.

Example

No code snippet is provided as the issue is a feature request and does not include specific implementation details.

Notes

The proposed solution assumes that the settings.json file is a viable location for storing user preferences and that the application can be modified to read and respect these settings.

Recommendation

Apply workaround: Implement the proposed hiddenCommands setting and effort level display option, as they provide a targeted solution to the feature requests without requiring a version upgrade.

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