{"version":"2.1.290","anchor":"cloud-hook-warning-wording-and-ownerrepo-nested-path-gu","canonical_anchor":"cloud-hook-warning-wording-and-ownerrepo-nested-path-gu","heading":"Shorter cloud hook warning and a clearer error for nested project paths","tier":"notice","area":"Cloud Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290\/e\/cloud-hook-warning-wording-and-ownerrepo-nested-path-gu","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290","markdown":"### Shorter cloud hook warning and a clearer error for nested project paths\n\nThe warning about forwarding hooks to a cloud session is shorter, and `{owner}\/{repo}` endpoints now fail for project paths with more than two parts\n\n**What**\n\nHooks are commands Claude Code runs on your machine at set moments. When hooks are forwarded from a cloud session, the reason Claude Code gives is now shorter. It used to say the settings file \"sits where the cloud session can write on this machine\". It now says \"the cloud session may change its settings file\".\n\nEndpoints written with the `{owner}\/{repo}` placeholders now give an error when the project path is nested, meaning it has more than an owner and a repository name. The error says there \"would be more than one path segment here\" and suggests spelling the endpoint out in full.\n\n**Why**\n\nThe warning is easier to read. For projects in nested groups, you now get an error that tells you to write the full endpoint instead of the placeholder.\n\n- Area: Cloud Sessions\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}