feat: opt-in Remote Control + bake a default statusLine#2
Merged
Conversation
Remote Control: `--remote-control` was hard-wired into the entrypoint, but it needs a full-scope login token (`claude auth login`) — the long-lived CLAUDE_CODE_OAUTH_TOKEN / `claude setup-token` this image uses is inference-only, so RC was a dead default (Status: disabled). Make it opt-in: the flag is added only when CLAUDE_REMOTE_CONTROL=1. Docs (README, SECURITY, CLAUDE.md, .env.example) updated to state the token requirement. statusLine: bake statusline-command.sh to /usr/local/bin/claude-statusline.sh (fixed, HOME-independent path) and wire settings.local.json's statusLine.command to it, so the compact status line (dir, git, model, duration, context %, 5h/7d rate limits) works by default. Deps (jq, git, awk, date, grep) already in the image. Validated on a fresh local build (amd64): - statusLine: piping a sample JSON to claude-statusline.sh renders the full line ( /workspace · Opus 4.8 · 1h30m · 73% · 19.7k · 5h 82% · 7d 58% ) - RC off by default: entrypoint logs "Starting Claude Code in /workspace..." (no --remote-control); with CLAUDE_REMOTE_CONTROL=1 it announces RC requested - settings.local.json statusLine wired; script is 0755 at the fixed path 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
Two image-config fixes surfaced from runtime diagnostics.
1. Remote Control is now opt-in (was a dead default)
The entrypoint hard-wired
claude … --remote-control, but Remote Control requires a full-scopelogin token (
claude auth login). The long-livedCLAUDE_CODE_OAUTH_TOKEN/claude setup-tokenthis image uses is inference-only, so RC was always
Status: disabled— a flag promising afeature that can't work with the supported auth.
--remote-controlonly whenCLAUDE_REMOTE_CONTROL=1(off by default)..env.exampleupdated to state the token requirement and theopt-in env var.
2. Default statusLine
Bake
statusline-command.shto/usr/local/bin/claude-statusline.sh(a fixed, HOME-independentpath) and wire
settings.local.json'sstatusLine.commandto it, so a compact status line worksout of the box: directory, git branch + dirty counts, model, duration, context %, and 5h/7d rate
limits. Dependencies (
jq,git,awk,date,grep) are already in the image.Validation (fresh local build, amd64)
claude-statusline.shrenders the full line —/workspace · Opus 4.8 · 1h30m · 73% · 19.7k · 5h 82% · 7d 58%; script is0755at the fixedpath;
settings.local.jsonstatusLineconfirmed in the baked config.Starting Claude Code in /workspace...with no--remote-control; withCLAUDE_REMOTE_CONTROL=1it announces Remote Control requested../build.sh→ exit 0.Notes
misleading default and documents how/when it could work.