{"version":"2.1.247","anchor":"cloud-working-tree-upload-refuses-when-git-is-missing-or-whe","canonical_anchor":"cloud-working-tree-upload-refuses-when-git-is-missing-or-whe","heading":"Cloud working-tree upload refuses when git is missing or when project settings steer git","tier":"notice","area":"Cloud Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.247\/e\/cloud-working-tree-upload-refuses-when-git-is-missing-or-whe","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.247","markdown":"### Cloud working-tree upload refuses when git is missing or when project settings steer git\n\nCloud upload refuses when git is missing or your project settings set git-related environment variables.\n\n**What**\n\nUploading your working tree to a cloud session now stops in three more cases, all reported as `refused`: git cannot be found on the startup PATH once directories a cloud session could write to are excluded, a project or local `.claude` settings file (or `--settings`) sets a git-relevant environment variable, or a private git directory under `~\/.claude\/seed-admin` cannot be created.\n\n**Details**\n\n- Telemetry outcomes are `git_not_on_path` and `admin_dir_failed`; the settings case adds new event fields `steering` and `steered_by` naming the variable involved.\n- A partial clone with an older git now reports `refused` rather than a git error.\n\n**Evidence**\n\n`which decides where your own settings are found`\n\n- Area: Cloud Sessions\n- Names: `--settings`\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 3\/5"}