/update-config vs /config
People think /update-config is just a longer name for /config. Both change settings, but they work in very different ways. /config opens the settings panel, or sets one key such as theme=dark, and works at once. /update-config is a skill. You say a change in plain words, such as allow a command or add a hook, and Claude finds the right settings.json and edits it. Use /config for a switch. Use /update-config for a rule or a hook.
/update-config Command
You say a settings change, and Claude edits the file.
/update-config is a bundled skill that changes Claude Code's settings files for you. You say the change in plain words, such as allow npm test, set an environment variable, or add a hook. Claude finds the right settings.json and edits it. For simple choices like the theme or the model, /config is quicker.
/config Command
It opens the settings, or sets one from the prompt.
/config opens the settings panel, where you change how Claude Code works. You can also set one value from the prompt, such as /config theme=dark or /config model=sonnet. That way works with no panel open too. A few settings need you to say yes, such as going on past a usage limit, so they can only be turned on in the panel. /config --help lists the keys it takes.
In one line
- /update-config Command
- You say a settings change, and Claude edits the file.
- /config Command
- It opens the settings, or sets one from the prompt.