fix: statusLine in settings.json, suppress fullscreen prompt, silence auto-update warning#5
Merged
Merged
Conversation
… auto-update warning
From live-session feedback (auto mode + advisor confirmed working):
- statusLine was in settings.local.json and didn't render. Per the docs, Claude
Code reads `statusLine` from ~/.claude/settings.json (user settings) — moved it
there; removed it from settings.local.json.
- "Try the new fullscreen renderer?" prompt kept reappearing ("Not now" is only a
per-session decline). Set `"tui": "default"` in settings.json to pick the classic
renderer explicitly and suppress the prompt (verified against docs/en/fullscreen).
- "No write permissions for auto-updates" setup warning: added `"autoUpdates": false`
to settings.json (alongside the existing env DISABLE_AUTOUPDATER=1).
Validated on the local build (amd64): baked ~/.claude/settings.json carries
defaultMode=auto, advisorModel=opus, autoUpdates=false, tui=default, and the
statusLine command — all survive the RTK/caveman settings-merge during build;
settings.local.json no longer has statusLine.
NOT verifiable headless (TUI-only, user-confirmable): that the status line now
renders and the fullscreen prompt no longer appears. "Found invalid entries in: ."
points at the project dir (cwd) — run `/doctor` in that project to see which
file/keys; it is not in the baked image config.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changed
Fixes from live-session feedback. Auto mode and the advisor (Opus) were confirmed working; these
address the remaining UI issues.
settings.local.json, but Claude Code readsstatusLinefrom
~/.claude/settings.json(user settings) per the docs. Moved it tosettings.json; removedit from
settings.local.json."Not now" only declines for the session. Set
"tui": "default"insettings.jsonto pick theclassic renderer explicitly (verified against
docs/en/fullscreen)."autoUpdates": falsetosettings.json(alongside the existingenv.DISABLE_AUTOUPDATER=1) to silence "No write permissions for auto-updates".Validation (local build, amd64)
~/.claude/settings.jsoncarriesdefaultMode:auto,advisorModel:opus,autoUpdates:false,tui:default, and thestatusLinecommand — all survive the RTK/caveman settings-merge duringbuild;
settings.local.jsonno longer hasstatusLine../build.sh→ exit 0.NOT verifiable headless (TUI-only — please confirm in a live session)
TUI behaviors).
.is the project/cwd, so the invalid entries are in afile under your project (e.g.
/workspace/.claude/settings*.jsonor.mcp.json), not in thebaked image config. Run
/doctorin that project to see exactly which file/keys; happy to fix ifyou paste the details.