Set up Claude Code's global config in one paste. No questions asked.
한국어: README.ko.md
Paste this into Claude Code:
Read https://raw.githubusercontent.com/getCurrentThread/claude-code-starter/main/prompts/bootstrap.md
and follow that procedure exactly to configure my global Claude Code settings.
Claude backs up your settings.json, merges in the settings below, installs a status line, and
reports what changed. It does not ask you anything along the way.
Read
prompts/bootstrap.mdbefore you run it. It is short, and it turns onbypassPermissions. To pin a reviewed version instead of trackingmain, swapmainfor a tag in the URL.
| Key | Value |
|---|---|
permissions.defaultMode |
bypassPermissions — no permission prompts |
skipDangerousModePermissionPrompt |
true — no startup confirmation for bypass mode |
model |
opus |
effortLevel / ultracode |
xhigh / true |
modelSettings |
xhigh for claude-opus-5-5 and claude-sonnet-5-5 — the top-level effortLevel does not reach Opus 5.5 and later |
autoCompactEnabled / autoCompactWindow |
true / 400000 — compacts at 400K tokens |
autoUpdatesChannel |
latest |
remoteControlAtStartup, agentPushNotifEnabled, inputNeededNotifEnabled |
true |
attribution |
empty — no Claude signature in commits or PRs |
Plus a hook, hooks/stay-bypass, that sends a session back to bypass mode if you Shift+Tab
into Manual, Accept Edits, or Auto: on the next tool call it raises a permission request, allows it,
and switches the mode back. Plan mode and subagents are left alone, and if the switch does not take
(for example, bypass is disabled by policy) it backs off for the session instead of retrying.
And CC-statusline at size m, unless you already
have a statusLine — then yours is left alone.
Keys not in this table are kept as they are, and a settings.json that does not parse is left
untouched.
bypassPermissionsmode skips permission prompts, including for writes to protected paths such as.gitand.claude. Only use this mode in isolated environments like containers or VMs where Claude Code can't cause damage. — Claude Code docs
Every run backs up to settings.json.bak-<timestamp> first, and the final report prints the exact
restore command. By hand:
Copy-Item "$env:USERPROFILE\.claude\settings.json.bak-<timestamp>" "$env:USERPROFILE\.claude\settings.json" -Forcecp ~/.claude/settings.json.bak-<timestamp> ~/.claude/settings.json
