--safe-mode vs Bare Mode
People think --safe-mode and --bare do the same thing, since both skip your add-ons. They have different jobs. --safe-mode is for finding a fault. It turns off CLAUDE.md, plugins, hooks and the rest, but sign-in, tools and permissions work as usual. Bare mode is for scripts and CI. It never reads your saved sign-in, so it needs an API key, and it gives Claude just a few tools. Use safe mode when something is broken. Use bare mode for a run that must act the same on each machine.
--safe-mode Flag
It starts Claude Code with your add-ons turned off.
--safe-mode starts Claude Code with your add-ons turned off. Then you can find what is breaking it. CLAUDE.md, skills, plugins, hooks, MCP servers, custom commands and agents, themes, the status line and auto memory do not load. Sign-in, the model, built-in tools and permissions still work. Your admin's settings still apply.
Bare Mode
Starting Claude Code with none of your hooks, skills or memory loaded.
Bare mode starts Claude Code without any of your extras. With the --bare flag, it skips hooks, skills, plugins, MCP servers, auto memory and CLAUDE.md. Skills in a folder you pass with --add-dir still load. Nothing from the machine is loaded, so a run gives the same result on every computer. It is meant for CI jobs and scripts, where a stray setting could change the outcome.
In one line
- --safe-mode Flag
- It starts Claude Code with your add-ons turned off.
- Bare Mode
- Starting Claude Code with none of your hooks, skills or memory loaded.