Skip to content

[PR] fix: keep /bili/ base-URL legs direct when clients honour proxy envs (Claude Code 2.1.301 self-tunnel 403) - #3448

Closed
ranxianglei wants to merge 2 commits into
masterfrom
2026-10-17_fix-claude-self-tunnel-noproxy
Closed

ranxianglei wants to merge 2 commits into
masterfrom
2026-10-17_fix-claude-self-tunnel-noproxy

Conversation

@ranxianglei

Copy link
Copy Markdown
Owner

Closes #3446

What

The bili claude (and bili codebuddy) launcher sets HTTPS_PROXY=http://127.0.0.1:<port> alongside a base-URL override pointing back at its own listener (ANTHROPIC_BASE_URL=http://127.0.0.1:<port>/bili/https://api.anthropic.com). That design assumed Claude Code ignores HTTPS_PROXY (true for older builds' undici fetch). Claude Code >= 2.1.301 now honours proxy env vars, so the /bili/ leg goes out through the same listener: pre-#3251 that was a hard 403 tunnel_destination_denied: self; with #3251 (merged, not yet released) it becomes a wasted forward-proxy hop through itself.

Two layers

Behavior change (old -> new)

Lane Old child env New child env
claude (base URL wraps to /bili/) no bili-owned NO_PROXY/no_proxy (raw process.env inherited as-is) both set to the union of pre-existing values (either case variant) + localhost,127.0.0.1,::1; user entries never dropped
codebuddy (base URL wraps to /bili/) all inherited proxy vars stripped, no NO_PROXY/no_proxy same merged triple added; inherited non-loopback entries still stripped (#890 invariant intact)
other lanes unchanged unchanged (gate fires only when the final base-URL value is bili's own loopback /bili/ form)

Why: keep bili's own listener directly reachable from the child. A loopback-only exclusion cannot alter routing to real upstreams or corporate proxies.

Config surface: none — no new config key, env var, or CLI flag. (NO_PROXY here is child-process routing hygiene, documented in CONFIGURATION.md en/zh.)

Kernel: untouched. Wire / compression modes: untouched (launcher-only change; both-mode reasoning trivially holds since no request path changes).

Tests

  • 7 new unit tests in tests/launcher.test.ts: wrapped base URL => merged triple; union of both case variants preserves user entries + dedupes; already-complete value unchanged; raw-https upstream wins => no merge; codex (no base-URL lane) untouched even with proxy set; codebuddy parity.
  • One existing assertion updated: the codebuddy [Suggestion] 建议 launcher 一并覆盖常见小写代理变量(http_proxy / https_proxy) #890 inherited-proxy-stripping test now expects the launcher-owned loopback triple on NO_PROXY/no_proxy while inherited .corp entries stay stripped.
  • Local targeted runs green: tests/launcher.test.ts 309/309, tests/launcher-gemini-family.test.ts 28/28, tests/fix-1292-windows-claude-settings.test.ts + tests/launcher-plugin-mode.test.ts 13 pass / 1 skip, npm run typecheck clean. Full-suite verdict = CI.

Docs

Stale "undici fetch ignores HTTPS_PROXY" claims updated in CONFIGURATION.md/zh (manual section, env table row, launcher paragraph), README.md/zh (#2290 field-test note), and the in-code comment in discoverRoutes. Historical CHANGELOG/devlog entries left as-is.

@github-actions

github-actions Bot commented Oct 16, 2026 •

Copy link
Copy Markdown
Contributor

📦 Built Package Artifact

Branch: 2026-10-17_fix-claude-self-tunnel-noproxy (0c8a166)

Option A — Install this exact build (recommended)

npm install -g billion-context@0.0.4584-pr.3448.7723e42

This exact version is immutable and reproducible. The rolling pr tag tracks the newest test build across all PRs.

Option B — Download artifact

  1. Download the artifact from the Actions run
  2. Extract the tarball and install:
tar xzf billion-context-pr3448.tgz
npm install -g package

Install instructions are refreshed on each push.

@ranxianglei

Copy link
Copy Markdown
Owner Author

🤖 Powered by ework · qwen3.8-27b

(ai: vllm-qwen/qwen3.8-27b)

查重: 不重复。本 PR 是 #3446 的修复 PR;与 #3245/#3251 同属「自指代理 403」症状家族但生产者不同(客户端 GUI 代理设置 vs bili launcher 自身 env 组合),已在 issue 侧正确拆分并互链。

审核方式: 独立重读了 diff、全部调用点与测试,本地定向跑了改动面测试(typecheck + launcher 四个套件),未照抄 #3446 线程结论。

结构化八问

  1. 是什么问题:bili claude / bili codebuddy 启动器把 base URL 指回自己监听器的 /bili/ 前缀,同时又给子进程设 HTTPS_PROXY 指向同一 origin——CC ≥ 2.1.301 开始遵守代理 env,于是 /bili/ 这一腿从自己隧道回自己(fix: serve self-addressed absolute-form requests locally instead of self-denying them (ZCode, #3245) #3251 合入前是硬 403 tunnel_destination_denied: self,合入后是绕一圈的空转)。
  2. 什么原因导致的:启动器的「base URL + HTTPS_PROXY」组合建立在旧版 CC 的 undici fetch 忽略 HTTPS_PROXY 这一假设上;新版行为变了,假设失效。文档/注释里还留着这条过期声明。
  3. 影响范围与严重程度:所有跑 CC ≥ 2.1.301 的 bili claude 用户完全不可用(每个请求 403);codebuddy 同形状潜在受影响(未见报告);旧版 CC 不受影响。
  4. 怎么修复的:在源头修路由卫生(疏不堵)——当写入子进程的 base URL 值确实是 bili 自己的 /bili/ 包装形式时,把 loopback 三件套并入子进程 NO_PROXY/no_proxy(并集语义,用户已有条目按大小写不敏感去重后保留,绝不覆盖),复用既有的 LAUNCHER_LOOPBACK_NO_PROXY 常量与 jcode/aider/zed/qwen 的既有模式;同时修正 en/zh 文档里过期的「undici 忽略 HTTPS_PROXY」表述。该腿从此直连,不再依赖客户端版本行为、也不再依赖 fix: serve self-addressed absolute-form requests locally instead of self-denying them (ZCode, #3245) #3251 先发。
  5. 是否有回归问题:逐项清点过——唯一被触碰的既有行为是 codebuddy [Suggestion] 建议 launcher 一并覆盖常见小写代理变量(http_proxy / https_proxy) #890 继承代理剥离测试的期望值,[Suggestion] 建议 launcher 一并覆盖常见小写代理变量(http_proxy / https_proxy) #890 不变量完整保留(继承的非 loopback 条目仍被剥离,launcher 只追加自己的三件套);codex/gemini/iflow/qoder 等 lane 不变。一处小观察(非阻塞):gemini/iflow/antigravity 也是 baseUrlKeys lane(proxy:false)——默认 https 上游走 raw 路径不会触发;但若用户给这些 client 配了 plain-http base URL,合并会生效,此时子进程没有任何 proxy 变量,NO_PROXY 纯惰性无害,只是 PR 表格「other lanes unchanged」一行没覆盖到这个角落。无 fail-fast→吞错、无阈值/时序/输出格式漂移;wire/压缩/kernel 均未触碰(launcher-only,两种压缩模式平凡成立)。
  6. 是否破坏缓存:不涉及。
  7. 是否改了设计方向:不涉及——沿用既有 NO_PROXY 先例,无新机制。
  8. 是否引入了新的配置:无(PR 已声明 config surface: none)。

行为变更披露(PR 正文已有 old→new 表,我核对属实):claude lane 子进程 env 从无 bili 自有 NO_PROXY/no_proxy(裸继承)→ 两个 key 均设为「既有值 ∪ localhost,127.0.0.1,::1」;codebuddy lane 从全剥光无 NO_PROXY → 追加三件套。原因:保证子进程能直连 bili 自己的 listener,loopback-only 排除不影响任何真实上游/公司代理的路由。

测试有效性:7 个新测试都是精确值断言(合并三件套、双大小写变体并集+去重保序、幂等、raw-https 胜出时不合并、codex 不受碰、codebuddy 对等),bug 回归能被抓住;#890 更新后的断言同时钉住「launcher 三件套存在」与「继承 .corp 条目仍被剥离」。不是假测试。

我顺手修了一个小问题(独立标注 commit):PR 在更新 #890 测试时把断言失败信息里的参数写成了 seenEnv.NODE_EXTRA_CERTS(tests/launcher.test.ts:6382),失败时会打印 undefined 而不是真实的 NODE_EXTRA_CA_CERTS 值——已修为正确字段,push 为 a505801fc,不影响任何逻辑。

验证证据:本地(分支上,先建 kernel/pi-subagents dist)node --import tsx --test tests/launcher.test.ts tests/launcher-gemini-family.test.ts tests/fix-1292-windows-claude-settings.test.ts tests/launcher-plugin-mode.test.ts → 351 tests / 349 pass / 0 fail / 2 skipped;npm run typecheck 干净。CI:旧 head 上静态门禁全绿、ubuntu-22 三个 test shard 全绿(windows/ubuntu-24 shard 检查时仍在跑);新 head a505801 的全套 CI 正在跑,一行测试文案改动不影响其他 shard,以新 head 全绿为准。

判定:可合并——方向对(根因层修复)、回归清点干净、测试有牙、diff 整洁、行为变更已披露。等 owner 人工合并 + 新 head CI 全绿即可。

@ranxianglei

Copy link
Copy Markdown
Owner Author

🤖 Powered by ework · qwen3.8-27b

(ai: vllm-qwen/qwen3.8-27b)

CI 跟进:新 head a505801fc 全套 CI 已全绿——39 个 check run 全部完成:27 success + 12 skipped(e2e/registry 等按预期 gate 跳过),0 失败,无任何 in_progress 残留(含 windows-22 两个 shard 与 ubuntu-24 shard)。

结论维持:可合并,等 owner 人工合并即可。

@aolshevskiy

Copy link
Copy Markdown
Contributor

This branch's work continues in #3856: b6b20018 is your commit rebased onto the release merge our fork was on (6deb4547), author preserved, with one conflict resolution — master's #1821 MCP-shell-watch sentence kept in the README claude paragraph alongside your #3446 note — it replays onto current 8a00095d with no conflicts, so a rebase on your side is mechanical. c3f63ef0 on top drops HTTPS_PROXY and NODE_EXTRA_CA_CERTS from the claude child env and hands the auxiliary proxy this instance resolves over as a new auxProxy key on /__bili/health — the follow-up your own root-cause sentence points at, since a lane with no TLS hop and no certificate has nothing for either variable to do.

Two ways to take it, your call:

Either way your own diff needs no re-review: your launcher, test and CONFIGURATION hunks merged as written.

@ranxianglei ranxianglei changed the title fix: keep /bili/ base-URL legs direct when clients honour proxy envs (Claude Code 2.1.301 self-tunnel 403) [PR] fix: keep /bili/ base-URL legs direct when clients honour proxy envs (Claude Code 2.1.301 self-tunnel 403) Oct 19, 2026
@ranxianglei
ranxianglei force-pushed the 2026-10-17_fix-claude-self-tunnel-noproxy branch from 5a17917 to 7dbdd10 Compare October 19, 2026 15:21
@ranxianglei

Copy link
Copy Markdown
Owner Author

🤖 Powered by ework · qwen3.8-27b

(ai: vllm-qwen/qwen3.8-27b)

查重: 不适用——本条是系统冲突转发(merge state dirty)而非新缺陷报告;工作对象就是本 PR 自身。

冲突已处理完毕:PR 分支已 rebase 到最新 master(48d45e777)并 force-push,新 head 7dbdd1098(原 head 5a179172b)。

八问:

  1. 是什么问题:PR 分支与 master 冲突——两侧改了 README(英/中)同一行 claude 条目:master 侧(Hook-model clients (claude/zcode) have no mid-session self-heal when the proxy dies — ECONNREFUSED until next session #1821)在该行插了一句「MCP shell 会话内守护代理、死亡后自行重生」,本 PR 则替换了同行里过期的「CC 的 undici 忽略 proxy env 变量」旧结论。
  2. 什么原因导致:同一行的文本冲突,无语义冲突——两处改动针对同一 bullet 内不同句子,纯先后写入碰撞。
  3. 影响范围与严重程度:仅文档行;代码零影响。合并前唯一后果是 PR 处于 dirty 状态无法合并,无用户面影响。
  4. 怎么修复的:取并集保留双方意图——Hook-model clients (claude/zcode) have no mid-session self-heal when the proxy dies — ECONNREFUSED until next session #1821 守护句与本 PR 的新表述(CC ≥2.1.301 起 CLI 会遵守 HTTPS_PROXY,故 bili claude 走 /bili/ 改写的同时把 loopback 主机并入 NO_PROXY/no_proxy,该腿恒直连,[Bug] bili claude: Claude Code 2.1.301 honours HTTPS_PROXY, so the /bili/ base URL self-tunnels (403 tunnel_destination_denied: self) #3446)都留在该行;随后 rebase 到最新 master。代码区(src/launcher.ts 的 helper/flag、tests/launcher.test.ts)与 master 增量逐一核对为零重叠,auto-merge 安全。
  5. 是否有回归问题:无。既有行为清点:README 的 omp caveat 段([Bug] Anthropic requests leak prompt_cache_key when Cowork transport bypasses native fetch interception #2583/[PR] fix(#2645/#2649/#2583): wire-conformant prompt_cache_key on every egress lane + Cowork lane routing #3556)完好;master 期间新合入的两个 PR(Cold start after provider switch loses the session's compression ledger; refold hits local 413 | [Bug][v0.1.197] 冷启动后切换供应商漏载同一会话的压缩账本,重新折叠后触发本地 413 #3399 跨路由 ledger 恢复、[no-dispatch] Pinned installs get surprise reinstalls: advisory force-install ignores autoUpdate:false, and config-file changes only take effect on restart #3754 安装归因)被 rebase 完整带入——解决过程中 master 又前进了一截,我重新 fetch 后再 rebase 了一次对齐,最终对 master 的 diff 恰好是原来那 6 个文件,无任何多余增删;本地 typecheck 干净、定向 launcher 测试 376 过 / 0 败 / 2 skip。全量套件按 §7.2 以新 head 的远程 CI 为准。
  6. 是否破坏缓存:不涉及(未触碰缓存/重试/游标/去重逻辑)。
  7. 是否改了设计方向:无。
  8. 是否引入新配置:无。

补充:分支在唤醒前已被 squash/rebase 过一次(a505801fc → 5a179172b,内容相同,其时的 CI 全绿);本次再 rebase 到最新 master 得 7dbdd1098。PR 本身的行为变更(claude/codebuddy lane 子进程 env 增加 NO_PROXY/no_proxy loopback 三元组)已在 PR 描述披露,本次 rebase 未改变任何行为。

判定:可合并——意图双保、diff 收敛回 6 文件、本地定向验证通过;待新 head CI 转绿后由 owner 人工合并。

@ranxianglei

Copy link
Copy Markdown
Owner Author

🤖 Powered by ework · qwen3.8-27b

(ai: vllm-qwen/qwen3.8-27b)

查重: 不适用——这是外部贡献者(@aolshevskiy,未验证身份)在 #3856 上的整合请求,不是新缺陷报告。我已逐条只读核实其技术声明,但两条处置路径都不在我可自主执行的范围内,需要 owner 拍板。

核实结果(全部只读验证过):

为什么两条路径我都不自行执行:

  • 「squash [PR] fix(launcher): the claude child stops inheriting a proxy and CA it cannot use (#3446) #3856」= 合并 PR,系统规则 human-only,我做不了;
  • 「关掉本 PR」= 放弃已评审、CI 全绿的交付物,且用未评审的外部副本替换它,方向与评审纪律相反;
  • 「force-push 本分支到外部 fork head」= 未经 review 整体采纳 c3f63ef0——该提交动 /__bili/health wire 面(新增 auxProxy 字段)、claude lane env 语义、以及会话内工具出站行为(不再经 bili MITM 隧道),属 §7.4 human-gated 区域;且请求方在此线程身份未验证,公开渠道的授权声明不构成依据。

八问(决策请求,选项见下表):

  1. 是什么问题:非缺陷——外部贡献者就 [PR] fix(launcher): the claude child stops inheriting a proxy and CA it cannot use (#3446) #3856/[PR] fix: keep /bili/ base-URL legs direct when clients honour proxy envs (Claude Code 2.1.301 self-tunnel 403) #3448 两个 PR 如何归并征求选择。
  2. 什么原因导致:[PR] fix(launcher): the claude child stops inheriting a proxy and CA it cannot use (#3446) #3856 = [PR] fix: keep /bili/ base-URL legs direct when clients honour proxy envs (Claude Code 2.1.301 self-tunnel 403) #3448 工作 rebase 到 release 合并基底 + 一个增量提交;fork 无法推我们的分支,故请我们选归并路径。
  3. 影响范围与严重程度(按选项):A(强推 fork head)——替换已评审 head、基底回退约 20 个合并、夹带未评审 wire 变更,中风险(内容已核实等价,风险在流程绕过 review);B(squash [PR] fix(launcher): the claude child stops inheriting a proxy and CA it cannot use (#3446) #3856)——同 A 再加丢弃本 PR 线程/评审史,且合并本身 human-only;C(维持分列)——零变化,零风险;D(review 后 cherry-pick 并入)——单 PR 承载两笔变更,wire 变更无论走哪条路都需 owner 签核。
  4. 怎么修复的(推荐 C):不动任何分支;[PR] fix(launcher): the claude child stops inheriting a proxy and CA it cannot use (#3446) #3856 单独走一轮正式 review(需要时我来做),合并顺序 [PR] fix: keep /bili/ base-URL legs direct when clients honour proxy envs (Claude Code 2.1.301 self-tunnel 403) #3448 → [PR] fix(launcher): the claude child stops inheriting a proxy and CA it cannot use (#3446) #3856(后者届时 rebase 到新 master 是机械操作,hunk 无重叠)。
  5. 回归风险(按选项):A/B——若 c3f63ef0 有缺陷,会与已评审修复捆在一起难以隔离;C——无(现状保持);D——同 A 减基底回退,但评审面耦合。
  6. 是否破坏缓存:不涉及(各选项均不触碰缓存/重试/游标/去重;c3f63ef0 仅新增只读 health 字段)。
  7. 是否改了设计方向:c3f63ef0 本身是小方向变更(claude lane 彻底不再给子进程代理/CA,改以 auxProxy 交接辅助出站)——值得 owner 独立决策,与整合方式无关。
  8. 是否引入新配置:整合方式本身不引入;c3f63ef0 在 /__bili/health 响应新增 auxProxy 字段(wire 增量,按其测试向后兼容)。
选项 内容 谁可做
A 强推本分支至 fork head + 关 #3856 需 owner 批准 + 先 review c3f63ef0
B squash #3856 + 关本 PR 仅 human 可合并
C(推荐) 维持分列:#3448 原样保留,#3856 独立 review,按序合并 我只需接 review
D review 通过后把 c3f63ef0 以标注增量 commit cherry-pick 进本分支 + 关 #3856 需 owner 批准(wire 面变更)

判定:推荐 C——两笔变更本就是两层工作(已评审的 NO_PROXY 止血 + 未评审的根因清理),分列合并各自留痕最干净;等 owner 拍板,我的分支 7dbdd1098 保持对最新 master 干净可合。

@aolshevskiy

Copy link
Copy Markdown
Contributor

Taking Option C.

Your correction is right and mine was wrong: our base was 6deb4547, older than your 48d45e777, so "force-fast-forward this branch to our head" would have walked your base backwards rather than fast-forwarding it. That offer is withdrawn.

Sequence as you describe it: #3448 merges on its own, #3856 goes through its own review, and once #3448 lands I rebase #3856 onto the post-merge master and collapse it to the single c3f63ef0 change — so your commit does not ride along a second time and the review units stay separate.

In the meantime I rebuilt #3856 on current master 39fb841d, with your 7dbdd1098 as its first commit (44259f9b, author preserved) and ours on top (9dd93750). The branch was several merges stale before this, which is what made the original framing unusable. Verification on the new base: node --import tsx --test over the launcher, admin-probe, aux-proxy and launcher-plugin-mode suites → 359 pass / 0 fail / 2 skipped; check:test-import-graph clean.

Separately, the unused-exports red you will see on #3856 is master's, not ours: INTERNAL_ONLY src/log-mask.ts: maskUrlForPublish, introduced by a4f27307, failing on a clean 8a00095d checkout with nothing else applied. The gate's own prescription — drop the leading export at src/log-mask.ts:121 — clears it for every open PR at once, and I can send that as its own one-line PR if you want the red gone before reviewing either branch.

On §7.4, so the wire delta is on the record for whoever signs it off: the addition is the read-only auxProxy/auxProxySource pair on /__bili/health. A proxy instance started by an older build reports neither key, and the handoff then does nothing rather than guessing at bili's own origin; the child's own proxy variables are never overwritten.

awork added 2 commits October 20, 2026 02:50
…d on master since a4f2730 (#3811)

Drive-by fix for the pre-existing master CI red (unused-exports gate), folded here per the repo's few-line-fix dispatch discipline instead of a second PR. The gate's own prescription: drop the leading export. Verified zero references outside src/log-mask.ts on current master.
@ranxianglei
ranxianglei force-pushed the 2026-10-17_fix-claude-self-tunnel-noproxy branch from 7dbdd10 to 0c8a166 Compare October 19, 2026 19:10
@ranxianglei

Copy link
Copy Markdown
Owner Author

🤖 Powered by ework · qwen3.8-27b

(ai: vllm-qwen/qwen3.8-27b)

查重: 不适用——本线程整合流程的延续(选项 C 确认 + master CI 红处置),非新缺陷报告。

序列确认:按选项 C 执行——#3448 独立合并;#3856 走自己的评审轮,#3448 落地后 rebase 到合并后 master 并收敛为单个 auxProxy 变更。你们的撤回与更正无异议。

核实结果(只读验证):

处置(有范围披露):那个一行修复不需要单独开 PR——按仓库几行级小修调度纪律(CI 失败类小修首选在当前 PR 顺手修掉,避免第二个 PR 修同一行),我已把它作为独立标注 commit 并入 #3448,并顺带把分支 rebase 到最新 master 39fb841d。新 head 0c8a16699,两个 commit:3a3d930b8(#3448 本体,内容不变)+ 0c8a16699(gate 修复,commit message 已标注来由)。本地验证:unused-exports gate 转绿、typecheck 干净。披露:#3448 的 diff 从 6 文件变为 7 文件(新增 src/log-mask.ts 一行,即删掉 maskUrlForPublish 的 export 关键字)——刻意、已标注、纯 gate 修复,无运行时路径变化。CI 会在新 head 上重跑。(推送过程遇出口网络抖动,重试后已成功。)

八问:

  1. 是什么问题:无新缺陷——两条线:① 选项 C 序列确认;② 你们报告的 master 既有 CI 红如何消除。
  2. 什么原因导致:CI 红 = a4f27307([security][web] Diagnostics blob prints private relay hosts verbatim in the config section — the "secrets masked" header only masks values, not hosts | 诊断包 config 段原样输出内网中转地址:标题说"密钥已遮蔽",但只遮值不遮主机 #3811)导出了被 gate 判为 INTERNAL_ONLY 的 maskUrlForPublish,干净 master 即红,波及所有在途 PR 的 gate job。
  3. 影响范围与严重程度:所有 open PR 的 unused-exports job 连带变红,掩盖真实信号;严重度低(仅 gate,无运行时影响)。
  4. 怎么修复的:按 gate 自身处方删行首 export;整树验证无外部引用;以独立标注 commit 并入 [PR] fix: keep /bili/ base-URL legs direct when clients honour proxy envs (Claude Code 2.1.301 self-tunnel 403) #3448(调度纪律:当前 PR 内修 > 再开一个 PR)。
  5. 回归风险:无——函数仅在同文件内部调用,去 export 不改任何代码路径;本地 gate 绿 + typecheck 绿;全量以 CI 为准。
  6. 是否破坏缓存:不涉及。
  7. 是否改了设计方向:无(auxProxy wire 字段的方向性说明留在 [PR] fix(launcher): the claude child stops inheriting a proxy and CA it cannot use (#3446) #3856 线程签核)。
  8. 是否引入新配置:无。

判定:序列不变——等 #3448 在新 head 0c8a16699 上 CI 转绿后由 owner 人工合并(合并后 master 的红随之自愈,无需额外动作);#3856 进入自己的评审轮。

@ranxianglei

Copy link
Copy Markdown
Owner Author

(ai: zhipuai-lb/glm-5.3)

陈旧票清理(第三批动作①):目标 issue #3446 已关。为避免重复劳动关闭本 PR;如判断有误请直接 reopen 并留言。

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Bug] bili claude: Claude Code 2.1.301 honours HTTPS_PROXY, so the /bili/ base URL self-tunnels (403 tunnel_destination_denied: self)

2 participants