{"version":"2.1.290","anchor":"agent-proxy-startup-handed-over-token-and-new-timing-teleme","canonical_anchor":"agent-proxy-startup-handed-over-token-and-new-timing-teleme","heading":"Agent proxy startup accepts a handed-over token and reports where its certificate came from","tier":"notice","area":"Cloud Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290\/e\/agent-proxy-startup-handed-over-token-and-new-timing-teleme","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290","markdown":"### Agent proxy startup accepts a handed-over token and reports where its certificate came from\n\nAgent proxy startup can use a handed-over token instead of reading a file, and now records timings and `ca_source` to help diagnose slow or failed starts\n\n**What**\n\nIn cloud sessions, Claude Code can start an agent proxy, a local relay that network traffic passes through, which needs a certificate (CA) and a token.\n\n- Startup can now use a token handed to it directly, so the token file is not read.\n\n- Startup records how long fetching the certificate, writing it to the trusted list, bringing the relay up and gathering inputs each took, and where the certificate came from (`ca_source`).\n\n- When setting up the certificate fails, the failure report now also carries `ca_source`. Before, it had no details.\n\n- The check for `jq` on the PATH now has a time limit and records when it times out.\n\n- Environment variables are read through a shared helper.\n\n**Why**\n\nIf a cloud session is slow to start or the proxy certificate fails, the extra detail shows which step was slow and where the certificate came from. The time limit on the `jq` check stops that one check from holding up startup.\n\n- Area: Cloud Sessions\n- Names: `CCR_AGENT_PROXY_ENABLED`\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}