{"version":"2.1.281","anchor":"settings-forwarding-status-not-bound-replaced-by-bound-else","canonical_anchor":"settings-forwarding-status-not-bound-replaced-by-bound-else","heading":"Settings-forwarding status: not_bound replaced by bound_elsewhere, binding_unknown and switched_off; repeated_errors removed","tier":"notice","area":"Cloud Sessions","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281\/e\/settings-forwarding-status-not-bound-replaced-by-bound-else","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281","markdown":"### Settings-forwarding status: not_bound replaced by bound_elsewhere, binding_unknown and switched_off; repeated_errors removed\n\nReasons for home settings not reaching a cloud session are more specific, and 'sync kept failing here' is removed\n\n**Unclear.** The finding does not give the wording shown for the switched_off reason.\n\n**What**\n\nClaude Code can forward your home settings to a session running in the cloud. When it does not forward them, it shows a reason. The generic \"not bound\" reason is replaced by more specific ones:\n\n- 'this machine could not show that this session is bound to it'\n\n- 'could not check this session's binding'\n\n- a new `switched_off` reason\n\nThe sync-status reason 'sync kept failing here' no longer exists.\n\n**Why**\n\nWhen your settings do not reach a cloud session, the message now tells you more precisely what went wrong. For example, it separates a failed binding check from a binding that could not be confirmed.\n\n- Area: Cloud Sessions\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}