{"version":"2.1.242","anchor":"bundling-for-a-cloud-session-reports-whether-your-read-rules","canonical_anchor":"bundling-for-a-cloud-session-reports-whether-your-read-rules","heading":"Bundling for a cloud session reports whether your Read rules were applied","tier":"notice","area":"Cloud Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.242\/e\/bundling-for-a-cloud-session-reports-whether-your-read-rules","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.242","markdown":"### Bundling for a cloud session reports whether your Read rules were applied\n\nBefore packaging your checkout, you are told if broken settings mean only committed files go up.\n\n**What**\n\nBefore packaging your checkout for a cloud session, Claude Code reads the rules that withhold files from upload and records how many applied versus how many could not be read. If a settings file has errors you are told that uncommitted contents stay local and the cloud session will start from what is committed.\n\n**Details**\n\n- Reported under `tengu_teleport_bundle_read_rules`.\n- If the repository layout is not supported by the newer packaging path, an older capture method retries the upload.\n\n**Evidence**\n\n`tengu_teleport_bundle_read_rules`\n\n- Area: Cloud Sessions\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}