| Signed in with the wrong account | Restart claude and sign back into the team account before following the rest of this guide. |
| Configuration feels overwhelming | Go back to Core Session Commands, Your First Feature, and Daily Workflow. |
Unsure whether to use /init or CLAUDE_CODE_NEW_INIT=1 claude | Use /init for the faster baseline and the env-var flow for the broader guided bootstrap. |
| Hooks not firing | Verify with /hooks, then re-check the matcher and the event name in .claude/settings.json. |
| Hook blocks unexpectedly | Confirm whether the hook returned allow (0), warn (1), or block (2), then inspect the message Claude surfaced. |
| Context is filling too fast | Use /context, compact earlier with /compact, and interrupt bad turns with Ctrl+C instead of letting the session drift. |
| Debugging keeps looping without progress | Switch to /debug, provide the real failure output, and ask Claude to investigate before changing code. |
| Permission prompt fatigue | Review /permissions and pre-approve safe commands in shared settings first. Use --allowedTools for a one-off wide-open session before you reach for --dangerously-skip-permissions. |
| Plugin you expected is missing | Open /plugin, review what is already installed, add only the missing plugin, and restart Claude Code if the state still looks stale. |
| Superpowers features are unavailable | Check the plugin manager first. If Superpowers is installed, ask Claude what skills are active before assuming the plugin failed. |
| Remote Control session is hard to find | /rename before /rc, then resume by name or use the Claude app/code view. |
claude doctor shows environment issues | Update Claude Code first, then re-check authentication, shell setup, and network access. |
