{"version":"2.1.277","anchor":"ccr-worker-requests-can-target-a-custom-session-url","canonical_anchor":"ccr-worker-requests-can-target-a-custom-session-url","heading":"CCR worker requests can target a custom session URL","tier":"internal","area":"CCR","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.277\/e\/ccr-worker-requests-can-target-a-custom-session-url","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.277","markdown":"### CCR worker requests can target a custom session URL\n\nCCR worker requests can now target a custom session URL instead of the default endpoint\n\n**Unclear.** The finding does not say what CCR stands for or in what situation a custom ccrSessionUrl would be set.\n\n**What**\n\nThe function that sends CCR worker requests to a Claude session now checks for a `ccrSessionUrl()` value from the host's launch options first. If one is set (with any trailing slashes removed), it's used as the base address for the `\/worker\/...` call; otherwise Claude Code falls back to the default `...\/v1\/code\/sessions\/{id}` URL. When a socket is used for the connection, the log now also notes \"over ${socket path}\" for extra context.\n\n**Why**\n\nThis allows worker requests to be redirected to a non-default session endpoint, useful when a session isn't reachable at the standard URL.\n\n- Area: CCR\n- Names: `ccrSessionUrl`\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}