{"version":"2.1.234","anchor":"newly-created-pull-requests-can-be-reported-to-the-cloud-ser","canonical_anchor":"newly-created-pull-requests-can-be-reported-to-the-cloud-ser","heading":"Newly created pull requests can be reported to the cloud service","tier":"soon","area":"Cloud Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.234\/e\/newly-created-pull-requests-can-be-reported-to-the-cloud-ser","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.234","markdown":"### Newly created pull requests can be reported to the cloud service\n\nPull requests you create could be reported to a cloud endpoint, but nothing is sent here.\n\n**What**\n\nAfter a successful `gh pr create` that is not a `--dry-run`, Claude Code can post the owner, repo, PR number and head branch to a new `\/worker\/record-created-pr` endpoint. This is gated on `tengu_record_created_pr_to_ccr`, which reads false without a server value, so nothing is sent in this build.\n\n**Details**\n\n- Outcomes are counted under `ccr_record_created_pr`, including a `not_deployed` case when the endpoint answers 404 or 501.\n- Separately, git command parsing now infers that a push happened from the command text on exit 0, and labels link-fetch attempts as \"pushed\" or \"checked-out\".\n\n**Evidence**\n\n`\/worker\/record-created-pr`\n\n- Flag `tengu_record_created_pr_to_ccr`: Not enough to say (read for one account on one subscription tier against v2.1.234; this account: no value returned, anonymous baseline: no value returned, compiled default: off)\n- Area: Cloud Sessions\n- Names: `tengu_record_created_pr_to_ccr`\n- Tier: Nothing to try yet\n- Useful: 3\/5\n- Signal: 4\/5\n- Present in the build but not switched on"}