Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
79 commits
Select commit Hold shift + click to select a range
360057d
fix(overflow): recognize the DashScope input-length-range 400 so the …
Zhishulo Oct 22, 2026
0861f40
fix(pi): normalize Fleet CRLF and paint truncated rows
Oct 23, 2026
666141d
fix(window): size a child conversation from its parent's runtime-info…
Oct 25, 2026
6c0079b
fix: release input-only request data before streaming (#4753)
z0d0dOr Oct 25, 2026
4355ee2
fix(handoff): persist a completed reply when the client hangs up
yanhuojiyusheng Oct 26, 2026
ad09789
fix(handoff): drop leftover conflict markers (merge slip)
ranxianglei Nov 13, 2026
6706e61
fix: preserve changed user instructions during reconciliation
j0nsh1n Oct 25, 2026
d26b8d2
test: address instruction-preservation review findings
j0nsh1n Oct 25, 2026
d0fcba7
fix(reconcile): recover exact user text after line wrapping
j0nsh1n Oct 27, 2026
8aee685
fix(loop): retry stalled bare-announcement terminal turns (#3905)
fathonix Oct 27, 2026
872d07e
refactor(loop): strip #3906 streamMarkers hunks — owned by PR #4934
Oct 27, 2026
5f8e873
fix(degenerate-turn): implement the action-cue + closed-fence gates t…
Oct 27, 2026
1773bf3
test(issue3905): cover plugin chat/responses lanes like the #2303 sib…
Oct 27, 2026
e514661
fix(plugin): announcement-tail detector must read answer prose, not p…
Oct 27, 2026
206180d
fix: arm the pi lane's direct-send window guard so a proxy outage can…
adlternative Oct 28, 2026
852f802
fix: forward toolless structured-output requests as side requests
Oct 28, 2026
cb5f44e
fix(#5074): drop the unused export from requestsStructuredOutput
Oct 29, 2026
bb1ecde
chore: anchor the new side-request rule comments to #5073
Oct 29, 2026
c66905c
fix(hermes): align the #5073 side-call fix with #546/#388/#2500
elight Nov 5, 2026
69ca2dc
fix(hermes): route a plain-http provider base_url through the proxy (…
Oct 29, 2026
f7406e5
sync: decide block liveness by coverage shape, not existence
Oct 29, 2026
1eeddbd
fix: report nested transport timeout diagnostics without assuming idl…
TimBriseby Oct 29, 2026
592dee8
fix(loop): classify proxy tool failures by status line
LkxPro Oct 31, 2026
518f0ce
fix(diagnostics): distinguish size rejections and retain bounded causes
Maziar123 Nov 1, 2026
cbba6b3
fix(diagnostics): strip C1 control chars (incl. NEL) from the bounded…
Nov 1, 2026
f13d9bb
test(ci): issue5152 startReceiver waits for a valid port value, not f…
Nov 6, 2026
65a0794
chore: add redacted Responses WebSocket cache diagnostics
xulongwu4 Nov 3, 2026
6ee4ade
chore: drop the full-request hash from WS cache diagnostics
xulongwu4 Nov 10, 2026
c15d9ce
fix(#5687): a tool-less MAIN turn must not be mistaken for a dsh sidecar
Louie0806 Nov 5, 2026
6c65641
fix: align the single-shot sidecar doc comments with the narrowed res…
Nov 5, 2026
0abde2d
test: update stale side-lane comments and pin hasSingleShotBudget bou…
Nov 5, 2026
f37fd03
fix: identify billion-context in pi extensions
yanhuojiyusheng Nov 5, 2026
49dc5bd
test: align remaining pi-lane e2e + docs to the billion-context.js entry
Nov 5, 2026
740771d
docs: drop stray closing paren in delegate-notify header comment
Nov 5, 2026
fe40084
fix: create dist/agent in write-build-info so the shim write is self-…
Nov 5, 2026
19ba8ad
fix(incremental): continue repeated-content IDs across delta turns
mariopasquali Nov 5, 2026
bc07a9c
test(rolling-marks): compare instances on substance, not wall-clock t…
Nov 5, 2026
d6fb1cc
fix(opencode): ride REAL host msgIds into the incremental lane from b…
Nov 6, 2026
cb28a5f
fix: preserve position fingerprints when reaping folds
mariopasquali Nov 8, 2026
1012e61
fix(google): promote stripped proxy call thoughtSignature onto surviv…
atrokhym Nov 10, 2026
4dba441
fix: recognize dsh 0.2.2's auto-review sidecar shape (#6104)
gongfpp Nov 10, 2026
a6e074f
test: pin the #6104 review shape in the side-lane invariants suite (l…
gongfpp Nov 10, 2026
02c9412
test: pin both ends of the #6104 head window
gongfpp Nov 10, 2026
c837404
fix(omp): default PI_ANTHROPIC_MESSAGE_THREADS=0 so bili sees the ful…
SajjadPSavoji Nov 10, 2026
b64f1cf
docs(omp): document exported PI_ANTHROPIC_MESSAGE_THREADS default (#6…
Nov 10, 2026
38c171f
fix(win-cmd): double trailing backslashes when quoting for cmd.exe
aftabkh4n Nov 11, 2026
4a08498
test(win-cmd): pin the comspec trailing-backslash round-trip in CI
ranxianglei Nov 12, 2026
653df87
fix(#5951): let the OMP host own truncation recovery, keep diagnostic…
vladk1m0 Nov 11, 2026
3e27168
fix(#5951): commandcode truncation record uses single-newline JSONL t…
Nov 12, 2026
f912d91
fix(openai): treat omitted cache fields as zero cached tokens
myNameIsZhangYu Nov 12, 2026
708cef6
fix(storage): serialize archive exports and restore the newest dump
myNameIsZhangYu Nov 12, 2026
30fb96f
fix(update): prefer atomic directory swaps during in-place updates
myNameIsZhangYu Nov 12, 2026
7402629
test: regenerate storage-render goldens for OpenAI cache attribution …
myNameIsZhangYu Nov 12, 2026
ff497a1
perf(storage): skip rewrites when large session columns are unchanged
myNameIsZhangYu Nov 12, 2026
c297463
test(loop): restore #6329 regression — OpenAI cache-field omission is…
Nov 12, 2026
d342342
test: pin #6323 auto_vacuum-before-WAL pragma ordering
ranxianglei Nov 13, 2026
c251e0c
fix(test): remove duplicate buildSessionCacheReport import
myNameIsZhangYu Nov 12, 2026
dcf4ff2
kernel: bridge span-safe gaps at the merge gate so mega-turn islands …
691675122-debug Nov 9, 2026
1559254
fix(generation-boundary): arm the native-compaction rebase on a prove…
sorasoras Nov 12, 2026
7a2376d
kernel: heal unpaired server_tool_use / *_tool_result blocks before f…
raydocs Nov 12, 2026
d19da23
fix: teach direct ACP calls for Codex exec namespaces
xiaozhu1337 Nov 12, 2026
45fccba
test: pin the full Codex exec note constant in the #5592 regression t…
Nov 12, 2026
bdf1ac0
fix(handoff): complete #4753 release-wiring dropped by a marker slip
ranxianglei Nov 13, 2026
6c818b3
fix(test): repair comment/test join dropped by the #5074 union in the…
ranxianglei Nov 13, 2026
65aede1
fix(test): match the #4756 release hook to forward()'s master signature
ranxianglei Nov 13, 2026
3f099ca
fix(loop): restore the streamedMarkers push the #3906 strip mangled
ranxianglei Nov 13, 2026
90ba031
fix(handoff): stop coupling the handoff canSave to res.destroyed (#4861)
ranxianglei Nov 13, 2026
8edc22a
docs(architecture): add src/server/rejection-diagnostics.ts to the mo…
Nov 13, 2026
0271bb4
chore(pi-subagents): bump version 0.2.3 -> 0.2.4 for the fleet-inspec…
Nov 13, 2026
91db32d
chore: re-run kernel guard (kernel-change declaration added to PR body)
ranxianglei Nov 13, 2026
1b15692
kernel: version 0.0.197 (batch4 kernel fixes: #6428 server-tool pair …
ranxianglei Nov 13, 2026
60c66ad
fix(lock): restore root package version 0.1.213 (sed hit the wrong 0.…
ranxianglei Nov 13, 2026
d1e15b0
test(#2817): turn 1 carries the pinned one-shot budget for the narrow…
ranxianglei Nov 13, 2026
7d7631f
Revert "kernel: bridge span-safe gaps at the merge gate so mega-turn …
ranxianglei Nov 13, 2026
d058282
fix(storage): mysql archive restore keeps the NEWEST matching dump line
ranxianglei Nov 13, 2026
f1d696e
Revert "sync: decide block liveness by coverage shape, not existence"
ranxianglei Nov 13, 2026
369be2d
test(notices): delete the CI baseline's BILI_STORAGE_UNIFIED override…
ranxianglei Nov 13, 2026
e484c03
Merge remote-tracking branch 'origin/master' into fix-2817
ranxianglei Nov 13, 2026
d04a8ad
test(#5025): reset the native origin waiter so the suite's static pi-…
Nov 13, 2026
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 3 additions & 0 deletions CHANGELOG.md
Original file line number Diff line number Diff line change
Expand Up @@ -17,6 +17,9 @@ Versions follow the merge of a `*_release-v*` branch; CI publishes to npm on tag
### Fixed
- **dsh 桌面副本自己更新自己时也跑 boot smoke(#2082 后续)**:#2091 的 boot smoke 门只接在 `refreshDshDesktopCopy` 上(别的 bili 进程替桌面副本刷新的那条路)。代理本身就从桌面副本运行时,`hostManagedInstall` 按 #1575 放行,走的是普通自更新路径——周期检查 / `bili update`(`checkForUpdate`)和 advisory 强制安装 / 面板安装(`forceInstallVersion`)——这两处调 `installViaTarball` 没带 `bootSmoke`,入口能解析但加载即抛错的包只过 `node --check` 就被换上去,正是这道门要挡的状态。现在两条路径在安装目录是 dsh 桌面副本时同样启用 boot smoke,失败回滚到旧副本;其他安装布局行为不变。
- **A compress call that folded nothing no longer rewrites every `<acp>` tag on the next request (follow-up to #5608-C/D, #5797).** `applyRanges` armed the deferred one-time ref/ledger alignment (`session.pendingLedgerAlign`) right after committing the kernel's returned state — before the `blocksCreated === 0` returns — so a refused compress (range too small, cannot anchor, already compressed) or a no-op armed it too. The next save then ran `restampRefsToLedger`, which raised `timestampsHighWaterRefSeq` to the highest ref unconditionally: on a session whose refs already sit on their ledger seats (`kept=N restamped=0 rehomed=0`) no number moved, yet every tag minted so far dropped below the mark and lost its `time=` attribute — the whole cached prefix re-billed after a call whose receipt says nothing was folded. Now the marker is armed only once a block was really created; a real fold arms it exactly as before.
- **OMP owns truncation recovery:** Native OMP requests carry an internal recovery-owner marker that is stripped before upstream egress; bili leaves truncation classification and retries to OMP instead of spending a second proxy retry budget.
- Upstream stream truncation errors expose only the retry code to clients; transport causes and upstream trace IDs stay in local proxy logs.
- **Reasoning-only stream recovery (#5951):** OpenAI reasoning identity filters no longer block the existing one-shot retry after an upstream EOF or read error. Pending answer filters, visible answer text, tool calls, and an exhausted retry budget still prevent replay.
- **压缩树图:节点标题不再一闪即逝,点击压缩块能真正看到被压缩的消息内容**:此前树节点只有原生 SVG `<title>` 悬停提示——选中节点或 5s 轮询重画时 DOM 一变提示就消失,实测「显示一下马上消失」;右侧 Block details 里块的消息行虽带消息编号(mNNNNN)但内容全是一句「消息已不在会话中」(宿主原生压缩把消息从上下文剪掉后,字节无处可取)。现在:① 悬停提示改为页面内常驻浮层(.g-tip)——跟随指针、显示完整块号/tier/消息范围/完整主题/tokens/消息数,选中节点或轮询重画都不再打断,离开图形区才隐藏;悬停时节点卡片上的主题行同时原地扩宽(~20 字 → 20 字上限的完整截断,离开复原);② 5s 轮询只回传瘦节点(无主题/摘要/tokens),重画前先与详情富块按 blockId 合并——节点标题、浮层元信息、消息数不再在每次 tick 后退化成光秃秃的块号;③ 服务端新增**冻结快照水合**:压缩块落盘时已把原始消息逐条存进 blockContents(`[role]`/`[role • tool]` 头 + 原文,pi 宿主 user 消息还带 mNNNNN 标记行)——水合按**标记锚定**对齐:pi 宿主打进 user 消息正文的 mNNNNN 标记是身份戳,每个标记用两条独立证据之一锚死——**恒等锚**(标记号=该位当前 ref,从未被重编号)或**冻结 span 算术锚**(标记的冻结编号 − 块冻结 span 起点 = 快照位序;span 与标记同批写入,冷加载 restamp(#5196 parked 段换新号)重编了整块 ref 也照样成立——实测 b27 全块 127 条因此恢复,旧规则因标记号已不在 ref 表里整块拒水合);锚点之间的段仅在条数平衡时按位 zip。标记既非恒等也非算术锚(冻结上下文混入外来消息/span 无法证明)、锚点乱序、无锚非叶块(快照 span 的是 effective 超集)一律拒绝,未证明的位置保留诚实的 missing 标记——宁可不显示,不冒错位张冠李戴的风险(预览 + 点击展开取原文,`/message?ref=` 同享该层)。实测大会话(253 块/9771 个直接消息引用):7789 条(80%)恢复出真实预览与原文,其余保持 missing。回归:tests/web-blocks-tree.test.ts 冻结快照水合 7 用例(按位水合 / 条数不符拒 / 标记移位旧锚 / 宿主剪块中消息的锚定恢复 / restamp 整块恢复 / 算术锚优先于巧合 ref 碰撞 / 无锚标记整块拒(含 click-to-open 双向断言)),源码级断言更新为合并后重画(renderCollapSvg(merged)。
- **交接文档「Compressed block summaries」附录不再被吞进最后一条消息卡片**:客户端 handoff 渲染器只认 `### user/assistant/tool` 三种角色分隔线(#2065 语义,正文内其他 `###` 标题是内容),export 端 #845 追加在对话之后的 `## Compressed block summaries` 整节(长会话可达 80+ 个 `### Block bN` 条目、数百行)因此全部落进最后一个 assistant 卡片,看起来像「压缩消息被追加成一条巨型消息」。现在客户端把 Conversation 之后的 `## ` 级标题识别为独立分节:`### Block bN — topic` 逐条渲染为小块卡片(mono 块号 + 主题截断标题 + tier/token 元行 + Markdown 正文),角色卡片只保留真实对话。回归:tests/web-handoff-roles.test.ts 新增附录分节用例(角色卡片数不膨胀、条目内容保真、#2065 不变量不受影响)。
- **会话历史的「条数」维度与超大未压缩请求:按真实维度拦下,判死信息点名超重字段(#5000 #5794 #5885)**:#5000 的 26,903 条消息会话(55.2MiB)穿过了**所有**字节/token 闸门、在上游死于消息条数上限——因为条数这个维度从来没有任何闸(它无法被任何字节/token 估算表达:每条消息还各带 ~69B 的 m-ref 标记,26,903 条 ≈ 1.8MB 纯标记)。现在新增按上游配置的**条数闸**(`network.maxMessages` / `BILI_MAX_MESSAGES`,默认 0=关闭——不存在全局「通用上限」,条数上限因上游而异):超限直接 413,信息点名 COUNT 维度并给出可执行指引(重启会话或回退到更早的时点;折叠在一轮 preflight 内关不掉 ~20K 条的缺口,所以是纯判死、不做条数折叠),且在 token 触发器**之前**运行——token 达标但条数超标的体(正是 #5000 的形状)也只有这道闸看得见。同时所有超窗判死信息(#5932 的三道计量闸)现在**点名超重的是哪个字段**——按 #554 计量器同源分桶(messages / tools[] / system / other),不再只给一个总数:#5000 的形状会显示 `tools[] ~X`,巨大粘贴/工具结果会显示 `messages ~X`,运维一眼知道该删什么。另新增 **32MiB 解码摄入成本带**(`network.ingestBodyBytes` / `BILI_INGEST_BODY_BYTES`):#5794 的 51.2MiB/29,619 条请求每轮独占事件循环 5.5–7.2s(本机 CPU 54.6% → 747s FATAL 自重启、全员缓存冷),成本带在 JSON 解析扫掠**之前**按解码后字节 413(stage=ingest)——任何可解析的**文本为主**的 32MiB+ 体都已是 ≥~8M token,超出所有真实模型窗口,放行必然烧钱再死。带图片的体在所有车道豁免(base64 像素按设计不进 token 计量——#496/#1800/#857「图片单独计费、绝不在原始字节上判死」;#3909 的 ~48MiB 图片密集 chat 会话与 #3701 的 ~38.5MiB WS 截图体都是受支持工作负载,由槽位预算/收件上限/车道自身的预发送字节预算+丢弃逻辑治理;Responses 车道无论如何整体豁免);并发槽位预算与 5GiB 收件上限继续独立生效。回归:tests/issue5000-count-gate(3 e2e:token 达标+条数超标→413 零上游 / 无 model 路径 / 条数达标照常转发)、tests/issue5794-ingest-cap(3 e2e:超带文本→413 stage ingest / 带内照常 / 超带带图不拦)、tests/side-request-isolation 分桶计量单测;既有 332 用例(含 #3701/#857/#496/#4079/#4185/#2490 全部回归面)全绿。
Expand Down
1 change: 0 additions & 1 deletion CONFIGURATION.md

This file was deleted.

1 change: 0 additions & 1 deletion CONFIGURATION.zh-CN.md

This file was deleted.

5 changes: 3 additions & 2 deletions docs/configuration.md
Original file line number Diff line number Diff line change
Expand Up @@ -2193,6 +2193,7 @@ File keys resolve only when the matching env var is unset. Defaults in parenthes
| `BILI_ENCRYPTION_KEY` | Encrypt session files at rest (#708) for deployments on untrusted nodes. Exactly 32 bytes, hex (64 chars) or base64; unset = unencrypted plain-JSON files (or `BILIZSTD1` when `BILI_PERSIST_ZSTD=1` — see `BILI_PERSIST_ZSTD`). When set: every session file is written as `BILIENC1` AES-256-GCM over JSON that is zstd-compressed only when `BILI_PERSIST_ZSTD=1` (zstd on Node ≥ 22.15, raw body otherwise) — enabling compression also shrinks the file ~5–10×. Encryption and compression are now independent knobs (#1080). The key comes ONLY from this environment variable — never written to disk or logs — so keep it out of the same filesystem's reach. Invalid values abort startup (fail fast, never silently unencrypted). Booting with the wrong key skips the affected sessions as corrupt (logged, no crash). Losing the key makes encrypted sessions permanently unreadable. Symmetric by design (the same process encrypts and decrypts). Existing unencoded files are never rewritten at boot — they encrypt organically on their next save (downgrade safety; see `BILI_PERSIST_ZSTD`). Threat model (#708, owner-confirmed): it defends against **offline/mechanical** file acquisition — provider disk swaps, offline disk snapshots after node-image drift, stolen volumes, leaked backups, cloud-synced state dirs — where an offline third party cannot read the content without the key. It does NOT defend against targeted adversaries with live access to the node; for that tier move the trust root out of the proxy (KMS / TEE / confidential VMs, hardened permissions) instead of solving it inside the proxy — at that level far more than the key is exposed, so proxy-level key handling is not the boundary to hold (`BILI_PERSIST=0` disables persistence entirely). Double-encrypting the key with a second key from the same process/environment adds nothing: in every offline-theft scenario the attacker lacks exactly one artifact — your off-disk secret — whether it is called the data key or the wrapping key; only a wrapping key in a different trust domain (KMS/TPM/TEE) raises the bar, and that is scenario 2 above. |
| `BILLION_CONTEXT_PROXY` | Exported by the launcher; client-side bili plugins/extensions detect it and self-disable their own compression (no double compression). |
| `PI_PROXY_ANTHROPIC` | Exported by the `bili omp` launcher (only when neither `PI_PROXY` nor `PI_PROXY_ANTHROPIC` comes from the user's environment): points OMP's Cowork anthropic transport at the proxy so those requests ride the compressible lane instead of node:https direct (#2583/#3556). User-set values always win. |
| `PI_ANTHROPIC_MESSAGE_THREADS` | Exported as `0` by the `bili omp` launcher and set by the omp-native extension on load (only when the user has not set a non-blank value): OMP ≥ 18.18 otherwise sends official-URL Claude turns as Anthropic message threads, where every request carries only the newest message(s) and the upstream holds the history — bili never sees the conversation, so nothing folds (#6088). User-set values always win; pinning it yourself keeps threads on, and the proxy logs one warning per base session for such requests. |
| `BILLION_CONTEXT_PLUGIN` | Set `0` to disable plugin mode entirely (wire-level tool injection resumes). |
| `BILI_LAUNCHER_MODEL_WINDOWS` | Internal: the launcher hands the client's own per-model context windows (pi `models.json`, omp `models.yml`, opencode `models.<id>.limit`, codex `model_context_window`) to the spawned proxy as JSON, so the nudge denominator matches the real window for self-hosted models. Only the launcher sets it — no user configuration. |
| `BILI_LAUNCHER_LANE` | Internal: the launcher hands its client's lane name (pi / codex / claude / …) to the spawned proxy, which records it in the instance file (#1225). Reuse is identity-based: two instances with *different declared* lanes never attach to each other; an instance without a declared lane is a manually-started user-zone daemon — attachable by default (#1660). Only the launcher sets it — no user configuration. |
Expand Down Expand Up @@ -2435,7 +2436,7 @@ How each client is pointed at the proxy (set automatically in the child env):
| Client | Redirect | CA trust |
|---|---|---|
| pi | `HTTPS_PROXY` + `BILI_PROVIDER_REWRITES` env manifest (extension `registerProvider`) | `NODE_EXTRA_CA_CERTS` |
| omp | `HTTPS_PROXY` + `BILI_PROVIDER_REWRITES` env manifest (extension `registerProvider`) + `PI_PROXY_ANTHROPIC=<proxy>` when neither `PI_PROXY` nor `PI_PROXY_ANTHROPIC` is user-set (routes OMP's Cowork anthropic lane through the proxy instead of node:https direct, #2583/#3556) | `NODE_EXTRA_CA_CERTS` |
| omp | `HTTPS_PROXY` + `BILI_PROVIDER_REWRITES` env manifest (extension `registerProvider`) + `PI_PROXY_ANTHROPIC=<proxy>` when neither `PI_PROXY` nor `PI_PROXY_ANTHROPIC` is user-set (routes OMP's Cowork anthropic lane through the proxy instead of node:https direct, #2583/#3556) + `PI_ANTHROPIC_MESSAGE_THREADS=0` when unset (otherwise OMP ≥ 18.18 keeps the conversation history server-side, invisible to bili, #6088) | `NODE_EXTRA_CA_CERTS` |
| codex | `HTTPS_PROXY` + `-c key=value` overrides | `SSL_CERT_FILE` → `combined-ca.pem` |
| claude | `ANTHROPIC_BASE_URL` = `/bili/` URL (Vertex: `ANTHROPIC_VERTEX_BASE_URL`, when `CLAUDE_CODE_USE_VERTEX=1`; + `NO_PROXY`/`no_proxy` loopback merge, #3446) | none needed |
| opencode | `HTTPS_PROXY` + isolated `OPENCODE_CONFIG` | `NODE_EXTRA_CA_CERTS` |
Expand Down Expand Up @@ -2520,7 +2521,7 @@ bili plugin list # install status for every supported host
bili plugin remove pi # undo (original files backed up to *.bili-bak once)
```

`install pi` also replaces any **legacy** billion-context entries (old `npm:billion-context-pi` references, stale `npm:billion-context@x.y.z`, leftover dev-checkout paths) so exactly one bili plugin stays live; when it drops entries the output also reminds you that a **project-scope** entry (`pi install -l`, written to `<project>/.pi/settings.json`) is outside this global settings and must be removed by hand. With an npm-installed bili the written entry is the pi-managed spec `npm:billion-context` — pi installs it into `~/.pi/agent/npm/` automatically (also on startup if missing) and `pi update` upgrades it, so the entry survives node prefix moves across machines; a dev/checkout install keeps the machine-local abs path (pi loads local package dirs directly). Both load the `pi` manifest → `dist/agent/pi-native.js`, the self-spawning native entry — bare `pi` gets full plugin-mode compression with no launcher (#519).
`install pi` also replaces any **legacy** billion-context entries (old `npm:billion-context-pi` references, stale `npm:billion-context@x.y.z`, leftover dev-checkout paths) so exactly one bili plugin stays live; when it drops entries the output also reminds you that a **project-scope** entry (`pi install -l`, written to `<project>/.pi/settings.json`) is outside this global settings and must be removed by hand. With an npm-installed bili the written entry is the pi-managed spec `npm:billion-context` — pi installs it into `~/.pi/agent/npm/` automatically (also on startup if missing) and `pi update` upgrades it, so the entry survives node prefix moves across machines; a dev/checkout install keeps the machine-local abs path (pi loads local package dirs directly). Both load the `pi` manifest → `dist/agent/billion-context.js`, which delegates to the self-spawning native entry `dist/agent/pi-native.js` — bare `pi` gets full plugin-mode compression with no launcher (#519).

**Coexistence with the standalone `billion-context-pi` extension.** The two are mutually exclusive — both active means double compression. Three nets: the installer strip above (global settings), the `BILLION_CONTEXT_NATIVE=pi` marker the native entry sets synchronously at load (`billion-context-pi` **0.1.72+** re-reads it on every event and refuses; 0.1.71 and older check `BILLION_CONTEXT_PROXY` only at load time, before the native proxy exists), and a runtime scan: once its proxy is up, the pi-native entry reads both pi settings files and warns loudly about any co-resident legacy entry the installer never saw (project scope, or installed after the fact).

Expand Down
Loading
Loading