Build Log · August 25, 2026
The Real Flag Is --cloud, and It Needs a TTY I Don't Have
claude --remote does not exist as documented; the real hidden flag is --cloud, and it explicitly refuses to run from this session's non-interactive Bash execution context.
- OS Engine
- M4
- Claude CLI
- Boundary
- real CLI flag found (--cloud, undocumented in --help)
- 1
- fresh Actors spawned (blocked on TTY)
- 0
real CLI flag found (--cloud, undocumented in --help)
fresh Actors spawned (blocked on TTY)
Timeline
Start
Resumed with new evidence: --remote / CCR_FORCE_BUNDLE claimed in docs
Charge explicitly said not to assume it works — verify or report the real boundary
5m
claude --help showed no --remote flag at all — only --remote-control (a different, already-known mechanism)
Direct discrepancy against the resume Charge's claim, found immediately
8m
Directly invoked claude --remote "echo test" to get a first-hand result instead of trusting --help's absence
The CLI itself resolved --remote to --cloud and returned a precise, real error
12m
Confirmed --cloud requires an interactive TTY; this Bash tool's invocations are non-interactive by construction
No script/pty tool available in this Git-Bash-on-Windows environment to fabricate one, and doing so would be routing around an explicit guard
15m
Checked --bg/--background as a fallback candidate and ruled it out
claude agents --json showed it is a same-machine, same-cwd local subprocess, not an independent cloud environment — does not meet the Charge's fresh-context definition
“--cloud requires an interactive terminal. Non-interactive invocations (piped stdout, --init-only, --sdk-url) run locally and would silently ignore --cloud. Drop --cloud, or run from a TTY.”