{"version":"2.1.248","anchor":"remote-agent-proxy-adds-upload-and-receive-backpressure-with","canonical_anchor":"remote-agent-proxy-adds-upload-and-receive-backpressure-with","heading":"Remote agent proxy adds upload and receive backpressure, with two env kill switches","tier":"use","area":"Remote Agents","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248\/e\/remote-agent-proxy-adds-upload-and-receive-backpressure-with","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248","markdown":"### Remote agent proxy adds upload and receive backpressure, with two env kill switches\n\nThe remote agent proxy now caps stalled uploads and reads, with two env vars to disable each.\n\n**What**\n\nThe remote agent proxy tunnel now aborts an upload with a visible reason if the tunnel accepts no bytes for 60 seconds, and pauses reads past a receive high-water mark. Two new environment variables, `CCR_AGENT_PROXY_RECEIVE_GATE_DISABLED` and `CCR_AGENT_PROXY_UPLOAD_GATE_DISABLED`, turn each limit back off. Both are unset by default, so the limits are active for anyone running the remote proxy.\n\n**Details**\n\n- Defaults: `sendPauseAfterPendingBytes: 0`, `sendStallTimeoutMs: 60000`, plus receive high\/low water marks and a queued-download report size.\n- The two variables are read once at proxy startup and then removed from the inherited environment, so child processes do not see them. Both names were added to the remote env allowlist.\n- The whole path requires `CCR_AGENT_PROXY_ENABLED` and a remote (`CLAUDE_CODE_REMOTE`) session.\n\n**Usage**\n\n`CCR_AGENT_PROXY_UPLOAD_GATE_DISABLED=1 claude` **Evidence** `CCR_AGENT_PROXY_UPLOAD_GATE_DISABLED`, `CCR_AGENT_PROXY_RECEIVE_GATE_DISABLED`\n\n- Area: Remote Agents\n- Names: `CCR_AGENT_PROXY_RECEIVE_GATE_DISABLED`, `CCR_AGENT_PROXY_UPLOAD_GATE_DISABLED`\n- Tier: Use it now\n- Useful: 3\/5\n- Signal: 4\/5"}