Issue Station
Sign In
Tools hereToolbox

claude-code - 💡(How to fix) Fix [DOCS] Settings docs omit `/config` search matching for option values

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…

Root Cause

Search settings

Use the search box in /config to filter settings. Search matches both setting names/labels and option values. For example, searching vim finds Editor mode because vim is one of that setting's available values.

RAW_BUFFERClick to expand / collapse

Documentation Type

Missing documentation (feature not documented)

Documentation Location

https://code.claude.com/docs/en/settings

Section/Topic

/config settings interface behavior, specifically search/filter behavior in the interactive Settings UI

Current Documentation

The settings page currently says:

Claude Code offers a variety of settings to configure its behavior to meet your needs. You can configure Claude Code by running the /config command when using the interactive REPL, which opens a tabbed Settings interface where you can view status information and modify configuration options.

The commands reference currently says:

/config | Open the Settings interface to adjust theme, model, output style, and other preferences. Alias: /settings

The settings reference also lists the editorMode option and its value:

editorMode | Key binding mode for the input prompt: "normal" or "vim". Default: "normal". Appears in /config as Editor mode

These pages explain that /config opens the Settings UI and that Editor mode has a "vim" value, but they do not document that the /config search box can match option values.

What's Wrong or Missing?

Claude Code changelog v2.1.116 says:

/config search now matches option values (e.g. searching "vim" finds the Editor mode setting)

Current docs do not explain this behavior anywhere I could find in the Claude Code docs mirror. Users are told that /config opens the Settings interface, but not that they can search within it, and not that searches can match setting values as well as setting names/labels.

That gap matters for discoverability: a user who knows the value they want (vim) but not the setting label (Editor mode) has no documented way to learn that /config search can find the setting from the value.

Suggested Improvement

Add a short subsection to settings.md near the /config introduction that documents the Settings search behavior.

Suggested content outline:

Search settings

Use the search box in /config to filter settings. Search matches both setting names/labels and option values. For example, searching vim finds Editor mode because vim is one of that setting's available values.

Also update the /config row in commands.md to mention that the Settings interface is searchable.

Impact

Medium - Makes feature difficult to understand

Additional Context

Affected Pages:

PageContext
https://code.claude.com/docs/en/settingsPrimary /config documentation and settings reference
https://code.claude.com/docs/en/commands/config command reference

Total scope: 2 pages affected

Source: Changelog v2.1.116

Exact changelog entry: /config search now matches option values (e.g. searching "vim" finds the Editor mode setting)

extent analysis

TL;DR

Add documentation for the search behavior in the /config settings interface to improve discoverability.

Guidance

  • Update the settings.md page with a new subsection titled "Search settings" that explains how the search box in /config filters settings based on both setting names/labels and option values.
  • Modify the /config row in commands.md to mention that the Settings interface is searchable.
  • Verify the changes by checking the updated documentation on the affected pages: https://code.claude.com/docs/en/settings and https://code.claude.com/docs/en/commands.
  • Ensure the new documentation is concise and easy to understand, using examples like searching for "vim" to find the Editor mode setting.

Example

### Search settings
Use the search box in `/config` to filter settings. Search matches both setting names/labels and option values. For example, searching `vim` finds **Editor mode** because `vim` is one of that setting's available values.

Notes

The suggested improvement should be applied to the two affected pages: https://code.claude.com/docs/en/settings and https://code.claude.com/docs/en/commands. The changes should be minimal and focused on documenting the search behavior.

Recommendation

Apply workaround: Add the suggested documentation to improve discoverability, as the current documentation gap makes the feature difficult to understand.

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…
#file not found#serialization error#model compatibility#GPU setup#container setup

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 [DOCS] Settings docs omit `/config` search matching for option values