{"version":"2.1.304","anchor":"excluded-repository-check-and-cloud-device-wording","canonical_anchor":"excluded-repository-check-and-cloud-device-wording","heading":"Computer tools can be unavailable for an excluded repository, and notices say \"Linux VM\"","tier":"notice","area":"Cloud Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.304\/e\/excluded-repository-check-and-cloud-device-wording","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.304","markdown":"### Computer tools can be unavailable for an excluded repository, and notices say \"Linux VM\"\n\nYour computer's tools can now be reported unavailable to a cloud session because the repository is excluded, and notices say \"Linux VM\" not \"sandbox\"\n\n**Unclear.** How a repository comes to be excluded is not stated.\n\n**What**\n\nWhen a cloud session uses tools served from your own computer, Claude Code explains why they are unavailable. A new reason, `excluded_repository`, can now be given, meaning the repository is excluded.\n\nOther changes in the same area:\n\n- The notices now say the tools must run in a \"Linux VM\" (a virtual machine, a computer simulated inside your computer) instead of a \"sandbox\".\n\n- The prompt asking to share your computer's MCP servers with a cloud session now remembers a \"not now\" answer.\n\n**Why**\n\nThese are visible changes for people running a cloud session against their own computer.\n\n- Area: Cloud Sessions\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 4\/5\n- Scope: individual\n- Heads-up: no"}