{"version":"2.1.284","anchor":"new-connected-sessions-gate-tengu-violin-maple-and-file","canonical_anchor":"new-connected-sessions-gate-tengu-violin-maple-and-file","heading":"New connected-session (tengu_violin_maple) and file-sync (tengu_violin_duet) gates for --cloud sessions","tier":"soon","area":"Cloud Sessions","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.284\/e\/new-connected-sessions-gate-tengu-violin-maple-and-file","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.284","markdown":"### New connected-session (tengu_violin_maple) and file-sync (tengu_violin_duet) gates for --cloud sessions\n\nCloud sessions gain two new server gates, tengu_violin_maple for staying attached and tengu_violin_duet for directory sync\n\n**Unclear.** It is not clear what a connected session or file sync actually changes about the cloud session that gets created, or what the file sync switch falls back to by default.\n\n**What**\n\n`--cloud` (and its deprecated alias `--remote`) starts a Claude Code session in the cloud. Two new feature gates, switches the server controls, now decide parts of that flow.\n\n- `tengu_violin_maple` is read by a new `isConnectedSessionsEnabled` check that is passed into startup checks. It is now another way, besides `tengu_remote_backend`, to stay attached to a cloud session, and another way, besides `tengu_violin_wood`, to get trusted-device enrollment and cloud session creation.\n\n- With `--attach-serve`, the connected-session launch check still uses `isViolinWoodEnabled` (`tengu_violin_wood`); otherwise it uses `isConnectedSessionsEnabled`.\n\n- The offer to sync your directory when creating a session (`decideSyncOffer`) now needs both `tengu_violin_maple` and `tengu_violin_duet`, where before it depended on the `tengu_violin_wood` check.\n\n- File sync is forced off if either gate is explicitly false from a server payload, an override or a disabled state.\n\n- Both gates are read through a new helper that returns false on error, and returns false straight away, without waiting on the network, when the cached value is not true and came from one of those sources. A built-in fallback only counts when feature values are fresh.\n\n- Session-creation reporting now records whether the connected-session gate was on, off or not yet fetched.\n\nOn the readings this site has taken, not under this release, the flag server returned both new gates off for its account and for an anonymous user.\n\n**Why**\n\nWhether you can stay attached to a cloud session or sync your directory into it now depends on these server-side gates rather than only on the older ones.\n\n- Flag `tengu_violin_maple`: Off in both readings (read for one account on one subscription tier against v2.1.284; this account: off, anonymous baseline: off, compiled default: off) These values were read against a different version of Claude Code, so treat them as the nearest reading available instead of one taken on this release.\n- Flag `tengu_violin_duet`: Off in both readings (read for one account on one subscription tier against v2.1.284; this account: off, anonymous baseline: off, compiled default: not a boolean we can read) These values were read against a different version of Claude Code, so treat them as the nearest reading available instead of one taken on this release.\n- Area: Cloud Sessions\n- Tier: Nothing to try yet\n- Useful: 5\/5\n- Signal: 5\/5\n- Present in the build but not switched on"}