[guide] Claude Remote Control pin-off (#5607, in v4.1.0) is undocumented — no CHANGELOG entry, no security-model coverage

[kubestellar-hive]

Documentation Gap

PR #5619 (commit e26a861, released in v4.1.0) pins the Claude Code Remote Control bridge OFF at every claude-CLI launch: since Claude Code ~2.1.226 the bridge auto-starts via a server-side rollout flag when no explicit remoteControlAtStartup value exists, which exposed every hive agent (launched with --dangerously-skip-permissions) as a remote-controllable session on the shared claude.ai account.

This is a user-visible security change with an operator-facing opt-out (set remoteControlAtStartup: true in /data/home/.claude/settings.json; hive never clobbers an existing value and logs an Info receipt when the bridge is enabled), yet:

1. The ### Security section of the 2026-09-02 (v4.1.0) CHANGELOG entry does not mention it — despite the CHANGELOG policy header requiring user-visible security changes to be recorded.
2. src/docs/security-model.md Layer 4 (agent sandboxing) documents per-agent UIDs, tokens, tool denylists, and the policy proxy, but says nothing about the Remote Control session-exposure vector or the pin.

grep -rni "remote control" src/docs docs CHANGELOG.md returns nothing.

Recommendation

• Add a Security entry to the v4.1.0 CHANGELOG section describing the exposure, the pin, and the operator opt-out.
• Add a bullet to security-model.md Layer 4 documenting the pin, the add-if-missing merge semantics, and the hasUsedRemoteControl launch-time warning.

Scope claimed: CHANGELOG.md (v4.1.0 Security section) and src/docs/security-model.md (Layer 4). Disjoint from open PRs #5559 (UPGRADE.md), #5625 (pkg/convergence code), #4032 (proxy code).

---

Filed by guide agent (ACMM L5 — hold-gated mode)

— hive: agent=guide backend=copilot model=claude-sonnet-4-6

[clubanderson]

Verified before dispatching — the gap is real, with one correction to the issue itself.

The PR number in the title is wrong. It says #5607, which 404s. The actual PR is #5619 — fix(agent): pin Claude Remote Control off at every launch — merged. The body has it right; only the title is off. Worth fixing, because a reader following #5607 finds nothing and may conclude the whole issue is stale.

Confirmed on v4:

• the pin-off is in the shipped code — remoteControlAtStartup appears in src/pkg/agent/manager.go, 2 hits repo-wide
• CHANGELOG.md has zero mentions of remote control

So a security-relevant behaviour change shipped in a release with no operator-facing record of it.

Why this one matters more than a typical docs gap

The change closes a real exposure: since Claude Code ~2.1.226 the Remote Control bridge auto-starts via a server-side rollout flag when no explicit value exists — which made every hive agent, launched with --dangerously-skip-permissions, a remote-controllable session on the shared claude.ai account.

Two consequences for the documentation:

1. An operator who does not know this shipped cannot reason about their exposure window. Anyone running a pre-fix(agent): pin Claude Remote Control off at every launch #5619 image is still in that state and has no way to learn it from the CHANGELOG.
2. There is an opt-out that silently does nothing if described wrongly. Setting remoteControlAtStartup: true in /data/home/.claude/settings.json re-enables the bridge, and hive deliberately never clobbers an existing explicit value. Documenting the file path or the never-clobber semantics inaccurately would leave someone believing they had opted out when they had not — or believing hive would override a choice it actually respects.

For whoever writes it

Read manager.go and #5619's diff and describe what the code does, not what this issue says it does. Four strategist findings were closed today as non-defects because their evidence predated or misread the code, and two guide issues this week cited PRs that did not exist — including this one's title.

The security-model section in particular should state the pre-#5619 exposure explicitly rather than only documenting the current safe state. A reader on an older image needs to recognise their own situation.

[clubanderson]

Correcting my earlier comment: #5607 is not a bad reference. I checked it with the pulls endpoint, which 404s for an issue number — #5607 is the issue ("🐛 Claude agents start with Remote Control..."), and #5619 is the PR that fixed it. Both are valid; citing the issue is the right choice for a CHANGELOG entry. My apologies for the noise.

The substance of the finding stands and is verified: the pin-off is live in manager.go on v4, and CHANGELOG.md had no mention of it. #5628 now addresses that.