afucontext 0.0.0-stage → 0.1.18

package/LICENSE

@@ -0,0 +1,201 @@
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

package/README.md

@@ -1,3 +1,183 @@
-# Temporary Holding Version
+# AFU Context · Local asynchronous context compression
 
-This version is a temporary placeholder for this package. An operational version to replace this has been submitted for review and is awaiting a staged release.
+**English** · [简体中文](README.zh-CN.md) · [npm](https://www.npmjs.com/package/afucontext) · [Install](#install) · [Results](#results) · [Dashboard](#dashboard)
+
+In a long session, the same tool output can travel with every model request. AFU uses the host’s selected model to summarize completed history in the background. Once ready, the summary can replace that history on a later request while preserving newer tool calls and messages.
+
+## How AFU compacts a session
+
+| When | What AFU does |
+| --- | --- |
+| A session reaches its threshold | Prepares a summary in the background while the session continues. |
+| The host next needs the history | Checks that the covered prefix still matches before replacing it. |
+| After replacement | Records a successful upstream response or a host commit so the dashboard can distinguish generation from application. |
+
+<a id="install"></a>
+
+## Quick start
+
+Install and sign in to your host first. You need npm, Node.js **22.19+ (22.x) or 24+** and Python **3.11+** on `PATH`. Pick one row, run the install command in your terminal, then use the launch command.
+
+| Host | System | Install | Launch after installation | Tested version |
+| --- | --- | --- | --- | --- |
+| <a id="afu-claude"></a>Claude Code | macOS / Linux | `npx --yes --registry=https://registry.npmjs.org afucontext@0.1.18 install claude` | `claude` | 2.1.293 |
+| <a id="afu-codex"></a>Codex CLI | macOS / Linux | `npx --yes --registry=https://registry.npmjs.org afucontext@0.1.18 install codex` | `codex` | 0.153.4 |
+| <a id="afu-pi"></a>Pi | macOS / Linux | `npx --yes --registry=https://registry.npmjs.org afucontext@0.1.18 install pi` | `pi` | 0.84.4, 1.5.0 |
+| <a id="afu-dsh"></a>DSH | macOS / Linux | `npx --yes --registry=https://registry.npmjs.org afucontext@0.1.18 install dsh --profile YOUR_PROFILE` | `dsh --profile YOUR_PROFILE` | 0.2.2-rc.1 |
+| Codex CLI | Windows 10/11¹ | `npx.cmd --yes --registry=https://registry.npmjs.org "afucontext@0.1.18" install codex` | `codex` | preview, not yet tested; official in the next release |
+| Pi | Windows 10/11¹ | `npx.cmd --yes --registry=https://registry.npmjs.org "afucontext@0.1.18" install pi` | `pi` | preview, not yet tested; official in the next release |
+| DSH | Windows 10/11¹ | `npx.cmd --yes --registry=https://registry.npmjs.org "afucontext@0.1.18" install dsh --profile YOUR_PROFILE` | `dsh --profile YOUR_PROFILE` | preview, not yet tested; official in the next release |
+
+Supported on macOS (Apple Silicon) and Linux x64. Start a new session after installing.
+
+¹ Windows: Codex CLI, Pi and DSH are implemented but not yet tested on Windows hardware; this release is a preview, and Windows support becomes official in the next release. Run the commands in PowerShell; `npx.cmd` and the quotes around the package name are required there. Claude Code on Windows is not supported yet.
+
+ See [Installation notes](https://code.alipay.com/med_ai/afu_context_liwu/blob/master/docs/install-notes.md) for verification scope, versions and mirrors, startup after reboot, Pi / DSH options and known issues.
+
+<a id="results"></a>
+
+## Commands
+
+The terminal commands (`afuctx …`) are placed in `~/.local/bin` by the first install; if that folder is not on `PATH`, use `npx --yes --registry=https://registry.npmjs.org afucontext@latest` in place of `afuctx`. Install, upgrade and remove replace the runtime itself, so they always run through npx.
+
+| Command | What it does |
+| --- | --- |
+| `npx --yes --registry=https://registry.npmjs.org afucontext@latest install claude\|codex\|pi\|dsh` | Install for a host; for DSH add `--profile NAME` |
+| `npx --yes --registry=https://registry.npmjs.org afucontext@latest install dsh --runtime-only` | Prepare only the runtime, for use with `dsh plugin --profile NAME add afucontext-dsh-plugin` |
+| `npx --yes --registry=https://registry.npmjs.org afucontext@latest update` | Upgrade every host installed on this machine to this version |
+| `npx --yes --registry=https://registry.npmjs.org afucontext@latest remove HOST` | Remove; host settings return to their state before installation. For DSH, `--profile NAME` removes one profile |
+| `afuctx status` | Whether each host is connected, how far the context is from the trigger, compactions applied; `--json` for the full record |
+| `afuctx dashboard` | Open the local dashboard (same as `afuctx-admin`); `--prices FILE` estimates costs with your prices |
+| `afuctx repair codex --network` | Find and verify the proxy route to the model again (`repair claude` for Claude Code) |
+| `afuctx gc --dry-run` | List old runtimes and logs that can be removed; without `--dry-run` it removes them |
+| `afuctx --version` / `afuctx --help` | Version / help |
+
+Inside a host session:
+
+| Host | Status | Dashboard |
+| --- | --- | --- |
+| Claude Code | `/afuctx:status` | `/afuctx:dashboard` |
+| Codex | `$afuctx-status` | `$afuctx-dashboard` |
+| Pi / DSH | `/afuctx-status` | `/afuctx-dashboard` |
+
+## Benchmark results
+
+In a LongBench V2 replay of 39 history questions (20 agent histories and 19 dialogue histories), AFU’s asynchronous strategy answered **23 correctly** with an average context of **15.9k tokens**.
+
+| Replay strategy | First-answer accuracy | Mean context tokens |
+| --- | ---: | ---: |
+| No compaction | 19/39 (48.72%) | 72.6k |
+| Codex Compact Sync | 20/39 (51.28%) | 21.7k |
+| DSH Compact Sync | 18/39 (46.15%) | 26.1k |
+| Pi Compact Sync | 13/39 (33.33%) | 21.6k |
+| **AFU Compact Async** | **23/39 (58.97%)** | **15.9k** |
+
+**4.56×** is the ratio of mean context tokens without compaction to those with AFU. The replay used DeepSeek-V3.2 for both answers and summaries, a 131,072-token logical window, and a 20k AFU trigger with a one-turn delay. Synchronous strategies replayed their respective prompts and policies, with at least one compaction for the context-size comparison. This metric excludes answer output and does not measure total API cost or production savings for the npm release.
+
+<a id="dashboard"></a>
+
+## Web dashboard
+
+### Open the dashboard
+
+| Where | Type |
+| --- | --- |
+| In a Claude Code session | `/afuctx:dashboard` |
+| In a Codex session | `$afuctx-dashboard` |
+| In a Pi or DSH session | `/afuctx-dashboard` |
+| In a terminal | `afuctx dashboard` |
+
+- The dashboard runs in the background and does not occupy a terminal; opening it again reuses the same one, and it exits after 30 minutes without an open page.
+- It opens in the dark theme; switch to light, follow-system or English/Chinese in the top-right corner.
+- The terminal commands are placed in `~/.local/bin` by the installer (only when that folder is already on `PATH`; shell startup files are never edited and existing commands of the same name are kept) and are removed with the last integration.
+
+### Check the current session
+
+Type `/afuctx:status` in Claude Code, `$afuctx-status` in Codex, `/afuctx-status` in Pi or DSH, or run `afuctx status` in a terminal. It shows whether AFU is connected, the current context against the compaction threshold, and how many compactions have been applied.
+
+Without the terminal commands (for example when `~/.local/bin` is not on `PATH`), use the full npx commands. For Codex; for another host replace `codex` with `claude`, `pi` or `dsh`:
+
+```sh
+npx --yes --registry=https://registry.npmjs.org afucontext@0.1.18 status codex --brief
+npx --yes --registry=https://registry.npmjs.org afucontext@0.1.18 ui
+```
+
+### What the dashboard shows
+
+- **Overview**: tokens saved and compactions applied, plus conversation input, cache hit rate, compaction cost and active sessions; below, one row per conversation with its title, compaction state and a bar showing how far the context is from the compaction trigger.
+- **Session detail**: the context drop after each compaction, how long each one took and what it saved, and cache hit rates. A conversation the host split into segments (sub-agents, title requests, its own compaction) lists them here.
+- **Status**: integrations, versions and issues.
+
+Each compaction is recorded in three steps: **request observed → summary ready → summary applied**. For Claude Code and Codex, "applied" means a request carrying the summary received a complete successful response; for Pi it means a model request was sent with the summary in place of the history it covers; for DSH it means the host committed the summary to session history. Summaries run in the background and never delay the conversation. Unreported cache usage is shown as unknown; savings are calibrated against the token counts the model service reports for requests sent without a summary, and like costs they are estimates, not provider bills. To estimate cost, supply per-session input, output and cache prices; see [Dashboard and costs](https://code.alipay.com/med_ai/afu_context_liwu/blob/master/docs/local-dashboard.md).
+
+![AFU local dashboard overview (dark)](https://code.alipay.com/med_ai/afu_context_liwu/raw/master/docs/assets/dashboard-overview.en.jpg)
+
+*Demo data.*
+
+## Models and thresholds
+
+All four integrations reuse the conversation’s model and authentication. When the context passes the trigger, AFU summarizes earlier messages in the background with the current model, and later requests use the compacted history. Trigger = model window × trigger ratio. Defaults:
+
+| Model window | Default ratio | Example trigger |
+| --- | --- | --- |
+| 1,000,000 tokens or more | 50% | 1,000,000 window → 500,000 |
+| Under 1,000,000 tokens | 60% | 272,000 window → 163,200; 200,000 window → 120,000 |
+
+The model window is detected automatically:
+
+| Host | Where the window comes from |
+| --- | --- |
+| Claude Code | The window Claude Code passes to its status line command. AFU wraps that command to read it; your own status line keeps running unchanged |
+| Codex | Codex's local model catalog cache |
+| Pi / DSH | The model and window the host has selected |
+
+If a window is still unknown, chat continues and `/afuctx:status` or `$afuctx-status` says so.
+
+### Set the window or ratio manually
+
+Run the same install command with options, then start a new session. For Codex; for another host replace `codex` with `claude`, `pi` or `dsh`.
+
+| To | Option |
+| --- | --- |
+| Compact earlier or later | `--ratio 0.3` (between 0 and 1) |
+| Set the model window | `--context-window 200000` |
+| Restore automatic settings | `--context-window auto --ratio auto` |
+
+```sh
+# Trigger at 30% of a manually set 200,000-token window (60,000 tokens)
+npx --yes --registry=https://registry.npmjs.org afucontext@0.1.18 install codex --context-window 200000 --ratio 0.3
+# Restore automatic settings
+npx --yes --registry=https://registry.npmjs.org afucontext@0.1.18 install codex --context-window auto --ratio auto
+```
+
+For frequent use, run `npm install -g --registry=https://registry.npmjs.org afucontext@0.1.18` and use `afuctx` in place of the full `npx` invocation. For example, `afuctx dashboard --prices ./afu-prices.json` opens the dashboard with your price file to estimate costs.
+
+## Upgrade and remove
+
+After upgrading a Claude Code or Codex integration, start a new session to use the new gateway. To uninstall, remove the host integration first, then restart the host. Use the appropriate command below.
+
+To move every installed integration (Claude Code, Codex, Pi and each DSH profile) to the latest release in one step, run `update` with `@latest`. It upgrades them one by one with the settings they were installed with and prints the version change for each:
+
+```sh
+npx --yes --registry=https://registry.npmjs.org afucontext@latest update
+```
+
+To check which version you have, run `--version` (the launcher), or `status --brief`, which shows the installed version of each host:
+
+```sh
+npx --yes --registry=https://registry.npmjs.org afucontext@latest --version
+npx --yes --registry=https://registry.npmjs.org afucontext@latest status --brief
+```
+
+To upgrade or remove one host:
+
+```sh
+npx --yes --registry=https://registry.npmjs.org afucontext@0.1.18 upgrade codex
+npx --yes --registry=https://registry.npmjs.org afucontext@0.1.18 remove codex
+```
+
+Use `remove pi` or `remove dsh` for those integrations. In Windows PowerShell, use `npx.cmd` and double-quote the package name.
+
+The dashboard listens on loopback. Logs record usage and receipts, and Pi/DSH also persist summaries in local session state. Generating summaries uses model tokens. Savings depend on subsequent reuse and actual cache hits.
+
+[Apache-2.0](LICENSE)

package/README.zh-CN.md

@@ -0,0 +1,183 @@
+# AFU Context · 本地异步上下文压缩
+
+[English](README.md) · **简体中文** · [npm](https://www.npmjs.com/package/afucontext) · [一键安装](#install) · [评测效果](#results) · [Web 面板](#dashboard)
+
+长对话里，同一段工具输出可能随每次请求反复发送。AFU 用宿主当前的模型在后台整理已经结束的对话。摘要就绪后，下一次合适的请求可以用摘要替换旧历史，同时保留之后发生的工具调用和新消息。
+
+## AFU 如何压缩对话
+
+| 时机 | AFU 的行为 |
+| --- | --- |
+| 达到压缩阈值 | 后台生成摘要，当前会话可以继续。 |
+| 下一次使用历史 | 检查摘要覆盖的对话前缀是否仍然匹配，匹配才替换。 |
+| 使用之后 | 记录模型请求成功回执或宿主提交结果，面板区分已生成与已应用。 |
+
+<a id="install"></a>
+
+## 快速开始
+
+先安装并登录要使用的宿主，准备 npm、Node.js **22.19+（22.x）或 24+** 和 Python **3.11+**（需在 `PATH` 中）。选一行，在终端执行安装命令，然后用最后一列的命令启动。
+
+| 宿主 | 系统 | 一键安装 | 安装后启动 | 实测版本 |
+| --- | --- | --- | --- | --- |
+| <a id="afu-claude"></a>Claude Code | macOS / Linux | `npx --yes --registry=https://registry.npmjs.org afucontext@0.1.18 install claude` | `claude` | 2.1.293 |
+| <a id="afu-codex"></a>Codex CLI | macOS / Linux | `npx --yes --registry=https://registry.npmjs.org afucontext@0.1.18 install codex` | `codex` | 0.153.4 |
+| <a id="afu-pi"></a>Pi | macOS / Linux | `npx --yes --registry=https://registry.npmjs.org afucontext@0.1.18 install pi` | `pi` | 0.84.4、1.5.0 |
+| <a id="afu-dsh"></a>DSH | macOS / Linux | `npx --yes --registry=https://registry.npmjs.org afucontext@0.1.18 install dsh --profile YOUR_PROFILE` | `dsh --profile YOUR_PROFILE` | 0.2.2-rc.1 |
+| Codex CLI | Windows 10/11¹ | `npx.cmd --yes --registry=https://registry.npmjs.org "afucontext@0.1.18" install codex` | `codex` | 预览，未实测，下一版本正式提供 |
+| Pi | Windows 10/11¹ | `npx.cmd --yes --registry=https://registry.npmjs.org "afucontext@0.1.18" install pi` | `pi` | 预览，未实测，下一版本正式提供 |
+| DSH | Windows 10/11¹ | `npx.cmd --yes --registry=https://registry.npmjs.org "afucontext@0.1.18" install dsh --profile YOUR_PROFILE` | `dsh --profile YOUR_PROFILE` | 预览，未实测，下一版本正式提供 |
+
+支持 macOS（Apple Silicon）和 x64 Linux；安装后新开会话即可。
+
+¹ Windows：Codex CLI、Pi、DSH 已实现，但尚未在 Windows 实机测试，本版本仅供预览，下一版本正式提供。请在 PowerShell 中执行，命令里的 `npx.cmd` 和包名两侧的双引号都不能省。Claude Code 暂不支持 Windows。
+
+验证范围、版本与镜像、重启后的启动方式、Pi / DSH 参数和已知问题见 [安装说明](https://code.alipay.com/med_ai/afu_context_liwu/blob/master/docs/install-notes.zh-CN.md)。
+
+<a id="results"></a>
+
+## 命令一览
+
+终端命令（`afuctx …`）在首次安装后放到 `~/.local/bin`；该目录不在 `PATH` 时，把 `afuctx` 换成 `npx --yes --registry=https://registry.npmjs.org afucontext@latest`。安装、升级、移除这类会替换运行时本身的命令，始终用 npx 执行。
+
+| 命令 | 作用 |
+| --- | --- |
+| `npx --yes --registry=https://registry.npmjs.org afucontext@latest install claude\|codex\|pi\|dsh` | 安装到指定宿主；DSH 加 `--profile 名称` |
+| `npx --yes --registry=https://registry.npmjs.org afucontext@latest install dsh --runtime-only` | 只准备运行时，配合 `dsh plugin --profile 名称 add afucontext-dsh-plugin` 使用 |
+| `npx --yes --registry=https://registry.npmjs.org afucontext@latest update` | 把本机已装的所有宿主一次升级到这个版本 |
+| `npx --yes --registry=https://registry.npmjs.org afucontext@latest remove 宿主` | 移除，宿主配置恢复成安装前的样子；DSH 可加 `--profile 名称` 只移除一个 profile |
+| `afuctx status` | 各宿主是否接入、当前上下文离触发线多远、已压缩几次；加 `--json` 输出完整信息 |
+| `afuctx dashboard` | 打开本地面板（同 `afuctx-admin`）；`--prices 文件` 用自己的单价估算费用 |
+| `afuctx repair codex --network` | 重新查找并验证连到模型服务的代理（Claude Code 用 `repair claude`） |
+| `afuctx gc --dry-run` | 查看可清理的旧版本运行时和日志；去掉 `--dry-run` 才会真正清理 |
+| `afuctx --version` / `afuctx --help` | 版本号 / 帮助 |
+
+宿主会话里也可以直接用：
+
+| 宿主 | 查看状态 | 打开面板 |
+| --- | --- | --- |
+| Claude Code | `/afuctx:status` | `/afuctx:dashboard` |
+| Codex | `$afuctx-status` | `$afuctx-dashboard` |
+| Pi / DSH | `/afuctx-status` | `/afuctx-dashboard` |
+
+## 评测效果
+
+在 LongBench V2 的 39 道历史问答回放中（20 道 Agent 历史、19 道对话历史），AFU 异步压缩答对 **23 道**，平均上下文为 **15.9k tokens**。
+
+| 回放策略 | 首次回答正确率 | 平均上下文 tokens |
+| --- | ---: | ---: |
+| 无压缩 | 19/39 (48.72%) | 72.6k |
+| Codex Compact Sync | 20/39 (51.28%) | 21.7k |
+| DSH Compact Sync | 18/39 (46.15%) | 26.1k |
+| Pi Compact Sync | 13/39 (33.33%) | 21.6k |
+| **AFU Compact Async** | **23/39 (58.97%)** | **15.9k** |
+
+**4.56×** 是无压缩与 AFU 的平均上下文 token 之比。回放使用 DeepSeek-V3.2 回答和压缩，逻辑窗口为 131,072 tokens，AFU 在 20k 触发，摘要延迟一轮使用。同步策略按各自提示词和策略回放，比较上下文规模时至少压缩一次。此指标不含回答输出，也不能直接换算成 API 总费用或当前 npm 版本的线上收益。
+
+<a id="dashboard"></a>
+
+## Web 面板：查看压缩是否生效
+
+### 打开面板
+
+| 在哪里 | 输入 |
+| --- | --- |
+| Claude Code 会话里 | `/afuctx:dashboard` |
+| Codex 会话里 | `$afuctx-dashboard` |
+| Pi / DSH 会话里 | `/afuctx-dashboard` |
+| 终端里 | `afuctx dashboard` |
+
+- 面板在后台运行，不占用终端；再次打开会复用同一个面板，30 分钟没有页面打开时自动退出。
+- 默认暗色主题，右上角可切换亮色、跟随系统和中英文。
+- 终端命令由安装程序放在 `~/.local/bin`（已在 `PATH` 中时才放，不改 shell 配置，不覆盖你已有的同名命令），移除最后一个接入时一并删除。
+
+### 查看当前会话
+
+Claude Code 输入 `/afuctx:status`，Codex 输入 `$afuctx-status`，Pi 和 DSH 输入 `/afuctx-status`，终端里运行 `afuctx status`。会显示 AFU 是否已接入、当前上下文距离压缩触发线还有多少，以及已经生效的压缩次数。
+
+没有上面的终端命令时（例如 `~/.local/bin` 不在 `PATH` 中），可以用完整的 npx 命令。以 Codex 为例，其它宿主将 `codex` 换成 `claude`、`pi` 或 `dsh`：
+
+```sh
+npx --yes --registry=https://registry.npmjs.org afucontext@0.1.18 status codex --brief
+npx --yes --registry=https://registry.npmjs.org afucontext@0.1.18 ui
+```
+
+### 面板内容
+
+- **总览**：节省的 token 和生效的压缩次数，以及对话输入、缓存命中率、压缩消耗和活跃会话；下方每个对话一行，显示标题、压缩状态，以及距离触发压缩还差多少的进度条。
+- **会话详情**：上下文在每次压缩后的回落、每次压缩的耗时和节省量，以及缓存命中率。宿主把一个对话分成多段时（子代理、起标题请求、宿主自己压缩后），这里会列出各段。
+- **运行状态**：接入情况、版本和异常记录。
+
+每次压缩分三步记录：**请求已接入 → 摘要已生成 → 摘要已应用**。Claude Code 和 Codex 的“已应用”表示替换历史后的请求已收到完整成功响应；Pi 表示已有模型请求用摘要替换了它覆盖的历史；DSH 表示宿主已把摘要写入会话历史。摘要在后台生成，不影响对话。模型未返回的缓存用量显示为未知；节省量按模型服务对未压缩请求报告的实际 token 数校准，与费用一样都是估算，不是供应商账单。需要估算费用时，可按会话提供输入、输出和缓存单价，见[面板与费用](https://code.alipay.com/med_ai/afu_context_liwu/blob/master/docs/local-dashboard.zh-CN.md)。
+
+![AFU 本地面板的总览页（暗色）](https://code.alipay.com/med_ai/afu_context_liwu/raw/master/docs/assets/dashboard-overview.jpg)
+
+*截图为演示数据。*
+
+## 模型与压缩阈值
+
+四个平台都复用主对话的模型和认证。上下文超过触发线时，AFU 在后台用当前模型生成摘要，之后的请求改用压缩后的历史。触发线 = 模型窗口 × 触发比例，默认如下：
+
+| 模型窗口 | 默认触发比例 | 触发线示例 |
+| --- | --- | --- |
+| 1,000,000 tokens 及以上 | 50% | 1,000,000 窗口 → 500,000 |
+| 小于 1,000,000 tokens | 60% | 272,000 窗口 → 163,200；200,000 窗口 → 120,000 |
+
+模型窗口自动获取，不需要手动配置：
+
+| 宿主 | 窗口从哪来 |
+| --- | --- |
+| Claude Code | Claude Code 传给状态栏命令的模型窗口。AFU 包装这条命令来读取，你原来的状态栏照常运行、显示不变 |
+| Codex | Codex 本地的模型目录缓存 |
+| Pi / DSH | 宿主当前选择的模型和窗口 |
+
+窗口仍未知时聊天照常进行，`/afuctx:status` 或 `$afuctx-status` 会提示。
+
+### 手动指定窗口和调整比例
+
+用同一条安装命令加参数即可，改完后新开会话生效。下面以 Codex 为例，其它宿主将 `codex` 换成 `claude`、`pi` 或 `dsh`。
+
+| 想做的事 | 参数 |
+| --- | --- |
+| 提前或推迟压缩 | `--ratio 0.3`（取值 0 到 1 之间） |
+| 手动指定模型窗口 | `--context-window 200000` |
+| 恢复自动 | `--context-window auto --ratio auto` |
+
+```sh
+# 在 30% 触发，并手动指定 200,000 的窗口（即 60,000 触发）
+npx --yes --registry=https://registry.npmjs.org afucontext@0.1.18 install codex --context-window 200000 --ratio 0.3
+# 恢复自动设置
+npx --yes --registry=https://registry.npmjs.org afucontext@0.1.18 install codex --context-window auto --ratio auto
+```
+
+如果经常使用 AFU，可运行 `npm install -g --registry=https://registry.npmjs.org afucontext@0.1.18`，以后用 `afuctx` 代替完整的 `npx` 命令。例如，`afuctx dashboard --prices ./afu-prices.json` 用自己的单价文件打开面板估算费用。
+
+## 升级与移除
+
+升级 Claude Code 或 Codex 接入后，新开会话即可使用新版网关。需要移除时，先撤销对应宿主的接入，再重启宿主。以下两条命令分别用于升级和移除。
+
+想把已装的所有接入（Claude Code、Codex、Pi 和每个 DSH profile）一次升级到最新版，用 `@latest` 执行 `update`。它会按安装时的设置逐个升级，并打印每个接入从哪个版本升到哪个版本：
+
+```sh
+npx --yes --registry=https://registry.npmjs.org afucontext@latest update
+```
+
+查看版本：`--version` 显示启动器版本，`status --brief` 显示每个宿主当前装的版本：
+
+```sh
+npx --yes --registry=https://registry.npmjs.org afucontext@latest --version
+npx --yes --registry=https://registry.npmjs.org afucontext@latest status --brief
+```
+
+只升级或移除某一个宿主：
+
+```sh
+npx --yes --registry=https://registry.npmjs.org afucontext@0.1.18 upgrade codex
+npx --yes --registry=https://registry.npmjs.org afucontext@0.1.18 remove codex
+```
+
+Pi 和 DSH 可分别用 `remove pi` 或 `remove dsh` 撤销。Windows PowerShell 请使用 `npx.cmd` 并将包名放在双引号中。
+
+本地面板只监听回环地址。日志记录用量和回执，Pi/DSH 的本地会话状态还会保存摘要。生成摘要本身会调用模型，节省多少取决于后续复用和实际缓存命中。
+
+[Apache-2.0](LICENSE)