A cloud session can hold its first reply until your settings arrive; two env vars shorten the wait.
What's wrong with this entry?
A cloud session can hold the first turn until your forwarded settings have been applied or a timeout fires, so they affect that first reply instead of the next one. Two environment variables tune the wait, CLAUDE_CODE_HOME_SEED_HOLD_TIMEOUT_MS and CLAUDE_CODE_HOME_SEED_VERDICT_TIMEOUT_MS, and both are clamped against built-in caps, so they can only shorten it.
- The confirmation notice switches between " (in effect for this reply)" and " (from your next message)" depending on whether the hold succeeded.
- Setting the hold timeout to zero or less skips the hold entirely.
- Outcomes reported to telemetry: released, timeout, verdict_timeout, flag_timeout, interrupted, gate_off.
CLAUDE_CODE_HOME_SEED_HOLD_TIMEOUT_MS=500 claudeCLAUDE_CODE_HOME_SEED_HOLD_TIMEOUT_MS
Strings lifted out of the shipped bundle, so the claim above can be checked against them.