@kyun.si/codex-polish 0.0.1-beta.2 → 0.0.1-beta.3
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/CHANGELOG.md +5 -0
- package/CONTRIBUTING.en.md +4 -4
- package/CONTRIBUTING.md +4 -4
- package/README.en.md +11 -4
- package/README.md +11 -4
- package/docs/technical.en.md +10 -4
- package/docs/technical.md +10 -4
- package/evaluation/README.en.md +3 -3
- package/evaluation/README.md +3 -3
- package/package.json +1 -1
- package/plugins/codex-polish/.codex-plugin/plugin.json +1 -1
- package/plugins/codex-polish/hooks/preferences.mjs +9 -9
- package/plugins/codex-polish/skills/codex-polish/SKILL.md +21 -19
- package/plugins/codex-polish/skills/codex-polish/references/acp.md +2 -3
- package/plugins/codex-polish/skills/codex-polish/scripts/text_guard.mjs +14 -2
- package/plugins/codex-polish/skills/codex-polish-setup/SKILL.md +3 -1
package/CHANGELOG.md
CHANGED
|
@@ -2,6 +2,11 @@
|
|
|
2
2
|
|
|
3
3
|
[中文使用说明](README.md) · [English README](README.en.md)
|
|
4
4
|
|
|
5
|
+
## 0.0.1-beta.3
|
|
6
|
+
|
|
7
|
+
- 聊天里先显示 Gemini 润色版,再附上完整的 GPT 原稿。Gemini 返回原文时会注明,正文只显示一次。跳过或失败时会说明原因并保留原稿。可以单独要求只看润色后的正文。
|
|
8
|
+
- Replies show the Gemini rewrite followed by the complete original GPT draft. An unchanged reply appears once with a review label. If polishing skips or fails, the reply identifies the outcome and shows the original. You can ask for just the polished text.
|
|
9
|
+
|
|
5
10
|
## 0.0.1-beta.2
|
|
6
11
|
|
|
7
12
|
- 项目没有指定润色模式时,普通提问也会自动触发润色。使用前,在 Codex 中信任插件的 `UserPromptSubmit` 钩子。已选“只在我要求时”或“关闭”的项目会沿用该选择。
|
package/CONTRIBUTING.en.md
CHANGED
|
@@ -22,7 +22,7 @@ mkdir -p dist
|
|
|
22
22
|
npm pack --ignore-scripts --pack-destination dist
|
|
23
23
|
```
|
|
24
24
|
|
|
25
|
-
`npm pack` writes version `0.0.1-beta.
|
|
25
|
+
`npm pack` writes version `0.0.1-beta.3` of `@kyun.si/codex-polish` to `dist/kyun.si-codex-polish-0.0.1-beta.3.tgz`. Default tests need no API key. Native installer tests use a temporary Codex profile. A separate opt-in test makes four billable OpenAI requests. See the [live test instructions](docs/technical.en.md).
|
|
26
26
|
|
|
27
27
|
## Reporting Bugs
|
|
28
28
|
|
|
@@ -36,11 +36,11 @@ Open a GitHub pull request with the reason for the change, steps to reproduce or
|
|
|
36
36
|
|
|
37
37
|
## Publishing a beta
|
|
38
38
|
|
|
39
|
-
Set the version in both `package.json` and the plugin manifest to `X.Y.Z-beta.N`. Commit the change and push the matching Git tag. For example, to publish `0.0.1-beta.
|
|
39
|
+
Set the version in both `package.json` and the plugin manifest to `X.Y.Z-beta.N`. Commit the change and push the matching Git tag. For example, to publish `0.0.1-beta.3`:
|
|
40
40
|
|
|
41
41
|
```sh
|
|
42
|
-
git tag v0.0.1-beta.
|
|
43
|
-
git push origin v0.0.1-beta.
|
|
42
|
+
git tag v0.0.1-beta.3
|
|
43
|
+
git push origin v0.0.1-beta.3
|
|
44
44
|
```
|
|
45
45
|
|
|
46
46
|
GitHub Actions tests the tagged code, publishes the package to npm with the `beta` tag, and creates a GitHub prerelease. If a step fails, run the publishing workflow again from the Actions tab and enter the existing tag.
|
package/CONTRIBUTING.md
CHANGED
|
@@ -21,7 +21,7 @@ mkdir -p dist
|
|
|
21
21
|
npm pack --ignore-scripts --pack-destination dist
|
|
22
22
|
```
|
|
23
23
|
|
|
24
|
-
`npm pack` 会把 `@kyun.si/codex-polish` 的 `0.0.1-beta.
|
|
24
|
+
`npm pack` 会把 `@kyun.si/codex-polish` 的 `0.0.1-beta.3` 版打包为 `dist/kyun.si-codex-polish-0.0.1-beta.3.tgz`。默认测试无需 API 密钥,原生安装测试会使用临时 Codex 配置。另有一项在线测试需要显式开启,会向 OpenAI 发出四次付费请求。[运行在线检查](docs/technical.md)
|
|
25
25
|
|
|
26
26
|
## 反馈问题
|
|
27
27
|
|
|
@@ -35,11 +35,11 @@ npm pack --ignore-scripts --pack-destination dist
|
|
|
35
35
|
|
|
36
36
|
## 发布 beta
|
|
37
37
|
|
|
38
|
-
将 `package.json` 和插件清单中的版本一同改为 `X.Y.Z-beta.N`,提交后推送同名 Git 标签。例如发布 `0.0.1-beta.
|
|
38
|
+
将 `package.json` 和插件清单中的版本一同改为 `X.Y.Z-beta.N`,提交后推送同名 Git 标签。例如发布 `0.0.1-beta.3` 时运行:
|
|
39
39
|
|
|
40
40
|
```sh
|
|
41
|
-
git tag v0.0.1-beta.
|
|
42
|
-
git push origin v0.0.1-beta.
|
|
41
|
+
git tag v0.0.1-beta.3
|
|
42
|
+
git push origin v0.0.1-beta.3
|
|
43
43
|
```
|
|
44
44
|
|
|
45
45
|
GitHub Actions 会测试这个标签的代码,将安装包发布到 npm 的 `beta` 标签,并创建 GitHub 预发布版。如果某一步失败,可以在 Actions 中选择发布工作流,用已有标签重试。
|
package/README.en.md
CHANGED
|
@@ -2,12 +2,19 @@
|
|
|
2
2
|
|
|
3
3
|
**English** | **[简体中文](README.md)**
|
|
4
4
|
|
|
5
|
-
Codex Polish uses Gemini through Antigravity’s `agy acp` to polish Codex’s final replies. Projects default to automatic mode. Once you trust the plugin hook and start a new chat, ordinary questions trigger polishing.
|
|
5
|
+
Codex Polish uses Gemini through Antigravity’s `agy acp` to polish Codex’s final replies. When you get a rewrite, the chat shows Gemini’s version first, followed by the full original GPT draft for comparison. Projects default to automatic mode. Once you trust the plugin hook and start a new chat, ordinary questions trigger polishing.
|
|
6
6
|
|
|
7
7
|
In one test, Codex had to report that the export button was fixed and had passed local tests. A production check was still pending. Both texts below are translated from that test.
|
|
8
8
|
|
|
9
|
-
|
|
10
|
-
|
|
9
|
+
**Polished by Gemini**
|
|
10
|
+
|
|
11
|
+
The export button is fixed and passed local tests. It still needs to be checked in production.
|
|
12
|
+
|
|
13
|
+
**Original GPT draft**
|
|
14
|
+
|
|
15
|
+
Regarding progress with the export button fix, let me explain the actual situation. The export button has now been fixed, local tests have passed, and production verification has not yet been done.
|
|
16
|
+
|
|
17
|
+
To see just the rewrite for one reply, say **“Only show the polished text.”** If you ask for plain JSON, a command, or a verbatim quotation, the reply keeps that exact format.
|
|
11
18
|
|
|
12
19
|
## Quick Start
|
|
13
20
|
|
|
@@ -54,7 +61,7 @@ For a rewrite, Google receives your current question and reply draft. The plugin
|
|
|
54
61
|
|
|
55
62
|
## If a Reply Stays Unchanged
|
|
56
63
|
|
|
57
|
-
|
|
64
|
+
If Gemini returns the same text, the reply says it left the draft unchanged and shows the text once. If polishing was skipped before sending the draft, the request failed to finish, or the rewrite failed a check, the reply says what happened and shows the original GPT draft. Ask **“Why wasn’t my last reply polished?”** for that turn’s reason, or **“Check Codex Polish setup”** to troubleshoot the connection.
|
|
58
65
|
|
|
59
66
|
## Check, Update, or Uninstall
|
|
60
67
|
|
package/README.md
CHANGED
|
@@ -2,14 +2,21 @@
|
|
|
2
2
|
|
|
3
3
|
**简体中文** | [English](README.en.md)
|
|
4
4
|
|
|
5
|
-
Codex Polish 通过 Antigravity 的 `agy acp` 请 Gemini 润色 Codex
|
|
5
|
+
Codex Polish 通过 Antigravity 的 `agy acp` 请 Gemini 润色 Codex 的最终回复。采用改稿时,聊天里会先显示 Gemini 润色版,再显示完整的 GPT 原稿,方便逐句对照。项目默认使用自动模式,信任插件的 hook 并新开聊天后,像平常一样提问即可触发。
|
|
6
6
|
|
|
7
7
|
## 改写示例
|
|
8
8
|
|
|
9
9
|
一次测试里,Codex 要告诉用户导出按钮修好了,本地测过了,线上还没验。
|
|
10
10
|
|
|
11
|
-
|
|
12
|
-
|
|
11
|
+
**Gemini 润色版**
|
|
12
|
+
|
|
13
|
+
导出按钮目前已经修复,本地测试也已通过,不过线上还没有验证。
|
|
14
|
+
|
|
15
|
+
**GPT 原稿**
|
|
16
|
+
|
|
17
|
+
关于导出按钮的修复进度,这里向你说明一下实际情况。目前导出按钮已经修复,本地测试已经通过,线上还没有验证。
|
|
18
|
+
|
|
19
|
+
这轮只想看改稿,可以说 **“只给我润色后的正文”**。如果指定只输出 JSON、命令或逐字引文,回复会遵守指定格式。
|
|
13
20
|
|
|
14
21
|
## 三步快速开始
|
|
15
22
|
|
|
@@ -56,7 +63,7 @@ Codex Polish 通过 Antigravity 的 `agy acp` 请 Gemini 润色 Codex 的最终
|
|
|
56
63
|
|
|
57
64
|
## 为什么还是原稿?
|
|
58
65
|
|
|
59
|
-
|
|
66
|
+
如果 Gemini 返回的文字和原稿相同,回复会注明 Gemini 已返回原文,正文只显示一次。如果在发送前跳过、请求未完成或改稿没通过检查,回复会说明本轮实际情况,并附上 GPT 原稿。需要排查时,可以问 **“为什么上条回复没润色?”** 或 **“检查回复润色环境”**。
|
|
60
67
|
|
|
61
68
|
## 检查、更新与卸载
|
|
62
69
|
|
package/docs/technical.en.md
CHANGED
|
@@ -2,7 +2,7 @@
|
|
|
2
2
|
|
|
3
3
|
[简体中文](technical.md) · [Overview](../README.en.md)
|
|
4
4
|
|
|
5
|
-
Codex Polish `0.0.1-beta.
|
|
5
|
+
Codex Polish `0.0.1-beta.3` is a Codex plugin for macOS and Linux. Its local scripts use built-in Node.js modules and require Node.js 22.16 or newer. The [rewrite skill](../plugins/codex-polish/skills/codex-polish/SKILL.md) polishes eligible final replies. The [setup skill](../plugins/codex-polish/skills/codex-polish-setup/SKILL.md) checks the environment and manages project settings.
|
|
6
6
|
|
|
7
7
|
## Project Settings and Inheritance
|
|
8
8
|
|
|
@@ -29,12 +29,18 @@ When `.codex/codex-polish.language` is `auto`, chat prompts match the user's cur
|
|
|
29
29
|
| 2. Style check | Direct ACP proceeds immediately. With Decisions enabled, the protected current question and draft must score `P(needs rewrite) >= 0.80`. |
|
|
30
30
|
| 3. ACP rewrite | The agent launches `agy acp` in a temporary workspace under a dedicated editor role, opens a session with the configured Antigravity identity, reads the live model list, and verifies the project model. It rejects tool permission requests and requires a complete `end_turn` matching the request ID. |
|
|
31
31
|
| 4. Placeholder check | Every placeholder must appear in its original order. After restoring protected spans, the script verifies fixed tokens, numbers, units, and supported Markdown structures. |
|
|
32
|
-
| 5. Meaning check and delivery | Direct ACP
|
|
32
|
+
| 5. Meaning check and delivery | Direct ACP accepts the rewrite after local checks. With Decisions enabled, a changed candidate must also score `P(substantive change) <= 0.05` in the meaning check. Any stage failure returns the original draft, and user cancellation ends the turn. |
|
|
33
33
|
|
|
34
34
|
During a rewrite, `agy` connects to Google. The plugin's Node.js scripts contact a provider only for the optional OpenAI Decisions checks. The current Codex agent starts and cleans up the ACP process, selects the model, and exchanges protocol messages. [ACP operating instructions](../plugins/codex-polish/skills/codex-polish/references/acp.md)
|
|
35
35
|
|
|
36
36
|
The plugin requires the official Antigravity CLI 1.2.1 or later. By default it reuses the existing Antigravity sign-in on the machine and OS account running Codex. To use an AI Studio key or an enterprise identity, set `CODEX_POLISH_AGY_AUTH` to `gemini-api-key` or `agent-platform`, respectively. [Sign-in guide](../plugins/codex-polish/skills/codex-polish-setup/references/credentials.en.md) · [Google ACP authentication](https://antigravity.google/docs/ide/extensions/acp)
|
|
37
37
|
|
|
38
|
+
## What Appears in the Final Reply
|
|
39
|
+
|
|
40
|
+
When Codex adopts a rewrite, it uses ordinary Markdown labels within one final chat message. **Polished by Gemini** introduces the accepted text with protected details restored. **Original GPT draft** introduces the complete draft from before polishing. Both bodies appear verbatim.
|
|
41
|
+
|
|
42
|
+
If Gemini returns identical text, the reply says it left the draft unchanged and shows the text once. A skip before sending, an incomplete request, or a rejected rewrite gets a brief status based on what happened, followed only by the original. Asking for “only the polished text” gives you just the selected body. Requests for plain JSON, a single command, or other exact output receive the requested content without labels or status.
|
|
43
|
+
|
|
38
44
|
## Outgoing Content, Hooks, and Limits
|
|
39
45
|
|
|
40
46
|
For automatic polishing, trust the plugin's `UserPromptSubmit` hook in Codex (**Settings → Hooks** or `/hooks` in the CLI), then start a fresh chat. Explicit requests to polish the current question and draft work without the hook in both automatic and manual mode. Including earlier exchanges requires the trusted hook in either mode. [Codex plugins](https://developers.openai.com/plugins/build/plugins) · [Codex hooks](https://learn.chatgpt.com/docs/hooks#where-codex-looks-for-hooks)
|
|
@@ -85,7 +91,7 @@ Using Node.js 22.16 and Antigravity CLI 1.5.12, the Codex agent selected `gemini
|
|
|
85
91
|
|
|
86
92
|
### Checks still open
|
|
87
93
|
|
|
88
|
-
- Verify a complete rewrite in the T3 chat interface. Exercise both routes with authorized, de-identified samples. Compare the tool trace with the selected model, completed output, and process cleanup.
|
|
94
|
+
- Verify a complete rewrite in the T3 chat interface. Exercise both routes with authorized, de-identified samples. Compare the tool trace with the selected model, completed output, and process cleanup. Check the status and section order in the native final message and again after reopening the chat. Compare each displayed body with its source.
|
|
89
95
|
- Run Chinese drafts over 4 KiB in two chats simultaneously and check that each keeps its own text, placeholders, and session ID. Check fallback for an unavailable model, a permission request, cancellation, and a truncated stream.
|
|
90
96
|
- Collect at least 200 delivered real samples across the calibration and blind splits. Use the blind split to measure preference rates, severe fact reversals, missed workflows, verbatim display match, and end-to-end latency. Current thresholds are initial defaults, and `evaluation/example.jsonl` contains synthetic records (`demo_only`). See the [evaluation specification](../evaluation/README.en.md) and [contribution guide](../CONTRIBUTING.en.md).
|
|
91
97
|
|
|
@@ -95,4 +101,4 @@ Once the beta is published to npm, install it with `npx @kyun.si/codex-polish@be
|
|
|
95
101
|
|
|
96
102
|
Both `setup` and `update` accept `--install-agy` to install the Google CLI when needed. Updates preserve `.codex` project settings and the plugin’s enabled state. Re-running `update` with the same version replaces the build or recovers an interrupted update.
|
|
97
103
|
|
|
98
|
-
If you packed version `0.0.1-beta.
|
|
104
|
+
If you packed version `0.0.1-beta.3` locally, you can also run `npx --yes file:./kyun.si-codex-polish-0.0.1-beta.3.tgz uninstall` in the directory containing the archive. Uninstall removes the plugin and its marketplace, clears cooldowns and session pointers for the active Codex profile, and prints the backup path for any manually edited installation files. It keeps shared `agy` binaries and project `.codex` files.
|
package/docs/technical.md
CHANGED
|
@@ -2,7 +2,7 @@
|
|
|
2
2
|
|
|
3
3
|
[English](technical.en.md) · [项目首页](../README.md)
|
|
4
4
|
|
|
5
|
-
`codex-polish` 的 `0.0.1-beta.
|
|
5
|
+
`codex-polish` 的 `0.0.1-beta.3` 版包含两个 Codex 技能。[改写技能](../plugins/codex-polish/skills/codex-polish/SKILL.md) 在最终答复交付前润色草稿,[设置技能](../plugins/codex-polish/skills/codex-polish-setup/SKILL.md) 检查运行环境并保存项目设置。
|
|
6
6
|
|
|
7
7
|
## 模式、配置文件与查找规则
|
|
8
8
|
|
|
@@ -28,10 +28,16 @@
|
|
|
28
28
|
| 2. 风格判定 | 直接 ACP 路径在本地检查通过后立即进入改写。开启 Decisions 时,只有 `P(需要改写) ≥ 0.80` 才进入改写,原本清楚的草稿直接保留。 |
|
|
29
29
|
| 3. ACP 改写 | 在临时工作区启动关闭了默认内置工具的专用编辑角色,使用已配置的 Antigravity 身份建立会话,核对项目选中的模型,拒绝全部权限请求,且只接收请求 ID 匹配的完整 `end_turn`。 |
|
|
30
30
|
| 4. 固定内容还原 | 占位符必须按顺序逐一对应。还原后再次校验固定内容、数值与单位、控制字符、疑似凭据以及受支持的 Markdown 结构。 |
|
|
31
|
-
| 5. 原意复核与交付 | 直接 ACP 路径通过本地校验即采用改稿。开启 Decisions
|
|
31
|
+
| 5. 原意复核与交付 | 直接 ACP 路径通过本地校验即采用改稿。开启 Decisions 时,有改动的候选还需满足 `P(实质变化) ≤ 0.05`。任一阶段未通过均回退原稿,用户取消则直接结束本轮。 |
|
|
32
32
|
|
|
33
33
|
相关接口规范见 [Google ACP 认证](https://antigravity.google/docs/ide/extensions/acp)、[Decisions API](https://developers.openai.com/api/reference/resources/decisions/methods/create) 与 [Antigravity 角色的工具配置](https://github.com/google-antigravity/antigravity-cli/releases/tag/1.2.1)。
|
|
34
34
|
|
|
35
|
+
## 最终回复如何显示
|
|
36
|
+
|
|
37
|
+
采用改稿时,Codex 在同一条最终消息中用普通 Markdown 标出 **Gemini 润色版** 和 **GPT 原稿**。前一段逐字显示通过检查并还原后的改稿,后一段逐字显示交给插件前的草稿。
|
|
38
|
+
|
|
39
|
+
如果 Gemini 确实返回了相同的文字,回复会说明 Gemini 返回了原文,正文只显示一次。在发送前跳过、请求未完成或改稿被拒绝时,回复说明可确认的原因,只显示原稿。明确要求“只给润色后的正文”时只交付选定的正文。JSON、单条命令及其他逐字输出按用户要求直接交付,不加标题或状态。
|
|
40
|
+
|
|
35
41
|
## 隐私边界、文本保护与历史限制
|
|
36
42
|
|
|
37
43
|
本轮问题和待润色草稿在外发给 OpenAI 或 Google 之前都会先做字面量占位符替换。这些占位符保护代码、命令、路径、链接和数字等固定片段。服务商仍可读取普通正文。
|
|
@@ -63,7 +69,7 @@
|
|
|
63
69
|
|
|
64
70
|
`setup` 和 `update` 支持 `--install-agy`,在缺少 Antigravity CLI 时可自动安装。更新会保留项目设置与插件启用状态。同一版本号的新构建也能用 `update` 覆盖或重试中断的更新。
|
|
65
71
|
|
|
66
|
-
手头有本地打包的 `0.0.1-beta.
|
|
72
|
+
手头有本地打包的 `0.0.1-beta.3` 版时,也可以在压缩包所在目录运行 `npx --yes file:./kyun.si-codex-polish-0.0.1-beta.3.tgz uninstall`。卸载会清理该插件与专用市场,按当前 Codex 配置清除冷却记录和会话指针,保留各项目的 `.codex/` 配置和共用的 `agy`,并提示被手动修改过的安装文件备份位置。
|
|
67
73
|
|
|
68
74
|
## 已验证记录与真机验收
|
|
69
75
|
|
|
@@ -88,4 +94,4 @@ CODEX_POLISH_TEST_LIVE_DECISIONS=1 node --test --test-name-pattern='live fidelit
|
|
|
88
94
|
|
|
89
95
|
1. 分别在无 OpenAI 密钥和开启 Decisions 的项目中核对工具轨迹,确认只有当前 agent 持有 ACP 进程、模型选择准确且结束后进程回收干净。
|
|
90
96
|
2. 用超过 4 KiB 的中文长文在两个 Codex 会话中并发运行,确认正文、占位符和会话 ID 不串线,并核对缺模型、权限请求、取消和断流时的回退表现。
|
|
91
|
-
3.
|
|
97
|
+
3. 在原生最终消息和重开会话后的记录中核对状态、两版顺序及正文。采用改稿时分别对照还原后的改稿和原始草稿。统计盲评偏好、严重事实反转、漏调率、选定正文的逐字一致率和端到端延迟。统计门槛要求校准集和盲评集合计至少 200 个已交付的真实样本。[验收数据格式和指标](../evaluation/README.md)
|
package/evaluation/README.en.md
CHANGED
|
@@ -13,7 +13,7 @@ node --test tests/evaluation.test.mjs
|
|
|
13
13
|
|
|
14
14
|
1. Obtain permission to use the samples and remove sensitive content. Assign a stable `case_id` to each original prompt and draft. Record the variants and votes for that case in one JSONL row, assigned to a single split. A repeated ID in any row or split stops the script with the offending line number.
|
|
15
15
|
2. Label independently whether each original draft needs rewriting, then select thresholds on the calibration split. Freeze the plugin settings, model, and concise prompt used for the prompt-only baseline, and use that frozen setup across all blind samples. Each report corresponds to one frozen configuration.
|
|
16
|
-
3. Record the host tool trace, the selected reply text, and the native final message. For
|
|
16
|
+
3. Record the host tool trace, the selected reply text, and the native final message. Use the complete message to check the status, labels, section order, and original draft. For blind rating, take only the displayed body of the selected reply, omitting the plugin’s labels and status. Generate a prompt-only baseline reply using the same task, Codex model, and context with only a concise style instruction added. For samples that adopt a rewrite, also pair the rewrite against the original draft.
|
|
17
17
|
4. Randomize each pair into A and B. Raters see only the user prompt, required context, and two anonymous replies, choosing A, B, or a tie. After unblinding, record `plugin_side` and `pick`. An independent fact checker compares the original draft against the delivered reply and flags any severe fact reversal, such as turning "tests were not run" into "tests passed." The script consumes the collected records, while the data provider verifies authorization, split assignment, and blinding.
|
|
18
18
|
|
|
19
19
|
## JSONL Record Fields
|
|
@@ -26,11 +26,11 @@ node --test tests/evaluation.test.mjs
|
|
|
26
26
|
| `workflow_expected`, `workflow_ran` | Whether the turn should run through the plugin, and whether the host trace shows it actually ran. Turns skipped by rule can be `false` |
|
|
27
27
|
| `triggered` | `true` when the check decides to trigger an external rewrite, even if a failure happens afterward |
|
|
28
28
|
| `outcome` | `original` when delivering the initial draft, `adopted` when using the rewrite, `fallback` when delivering the original draft after a workflow error or validation rejection, `cancelled` when the user cancels and nothing is delivered |
|
|
29
|
-
| `selected_text`, `final_text` |
|
|
29
|
+
| `selected_text`, `final_text` | Take the first from the chosen rewrite or original draft. Independently take the second from its corresponding body in the native final message. Use the polished body when both versions appear, or the sole body when one appears. Exclude plugin labels and status. Preserve punctuation, spaces, and newlines within the body. Omit or set to `null` when cancelled |
|
|
30
30
|
| `elapsed_ms` | Total milliseconds from draft ready to native final message display. Set to `null` when unmeasured or cancelled |
|
|
31
31
|
| `severe_fact_reversal` | Human fact-check result for the delivered reply. Set `true` if a severe reversal is found, `false` if checked and none is found, or `null` if unchecked or cancelled |
|
|
32
32
|
| `vs_original` | One vote for each blind record that adopted a rewrite. `{"plugin_side":"B","pick":"A"}` means the rewrite appeared on side B and the rater chose the original draft. Use `"pick":"tie"` for a tie |
|
|
33
|
-
| `vs_prompt_only` | One vote for each delivered blind record. The plugin side
|
|
33
|
+
| `vs_prompt_only` | One vote for each delivered blind record. The plugin side shows `final_text` and the other side shows the prompt-only baseline, using the same format. Omit or set to `null` when missing or not applicable |
|
|
34
34
|
|
|
35
35
|
## Reading the Report
|
|
36
36
|
|
package/evaluation/README.md
CHANGED
|
@@ -13,7 +13,7 @@ node --test tests/evaluation.test.mjs
|
|
|
13
13
|
|
|
14
14
|
1. 取得使用授权并去除敏感信息。每条原始问题与草稿分配一个稳定的 `case_id`。同一个原稿及其变体使用同一 ID,划分时只进一个集合。脚本遇到重复 ID 会报行号并退出。
|
|
15
15
|
2. 独立标注原稿是否需要改写,再用校准集选择阈值。冻结插件配置、模型和仅提示对照的简洁提示,将这组配置用于全部盲评样本。每份报告对应一次冻结配置。
|
|
16
|
-
3.
|
|
16
|
+
3. 记录宿主实际工具轨迹、选定的正文和原生最终消息。在整条消息中核对状态、来源标签、版本顺序和原稿。盲评只取实际显示的选定正文,去掉插件标签和状态。每条盲评样本用同一任务、同一 Codex 模型和上下文生成仅加简洁提示的对照答复。对采用改稿的样本,再与原稿配对比较。
|
|
17
17
|
4. 每对随机排列成 A/B。评分者只看到用户问题、必要上下文和两篇匿名答复,分别选 A、B 或平局。揭盲后合并 `plugin_side` 和 `pick`。由独立核事实的人对照原稿和交付文本标出严重事实反转,例如把「没跑测试」改为「测试通过」。脚本消费采集结果,数据提供者负责核实授权、分组和盲法。
|
|
18
18
|
|
|
19
19
|
## 一行记录的字段
|
|
@@ -26,11 +26,11 @@ node --test tests/evaluation.test.mjs
|
|
|
26
26
|
| `workflow_expected`、`workflow_ran` | 该回合是否应走插件,以及从宿主轨迹观察到是否实际运行。按约定跳过的回合可填 `false` |
|
|
27
27
|
| `triggered` | 判定触发外部改写时为 `true`,即使随后发生故障 |
|
|
28
28
|
| `outcome` | `original` 交付初稿,`adopted` 采用改稿,`fallback` 工作流出错或校验驳回后交付原稿,`cancelled` 用户取消且本轮未交付 |
|
|
29
|
-
| `selected_text`、`final_text` |
|
|
29
|
+
| `selected_text`、`final_text` | 前者取自选定的改稿或原稿,后者独立取自原生最终消息中对应的正文。双版本回复只取润色版正文,单版本回复取唯一正文。排除插件添加的标签和状态,保留正文自身的标点、空格和换行。取消时省略或填 `null` |
|
|
30
30
|
| `elapsed_ms` | 草稿就绪到原生最终消息显示的总毫秒数。缺测或取消填 `null` |
|
|
31
31
|
| `severe_fact_reversal` | 对已交付正文的人工结论。发现严重反转填 `true`,已检查且无反转填 `false`,未检查或取消填 `null` |
|
|
32
32
|
| `vs_original` | 盲评中采用改稿的记录填写一票。用 `{"plugin_side":"B","pick":"A"}` 表示改稿放在 B,评分者选了原稿。平局为 `"pick":"tie"` |
|
|
33
|
-
| `vs_prompt_only` |
|
|
33
|
+
| `vs_prompt_only` | 所有已交付的盲评记录各填一票。插件一侧放 `final_text`,另一侧放仅提示对照。格式同上。缺失或不适用的票省略或填 `null` |
|
|
34
34
|
|
|
35
35
|
## 读报告
|
|
36
36
|
|
package/package.json
CHANGED
|
@@ -271,15 +271,15 @@ function runHook() {
|
|
|
271
271
|
if (event?.hook_event_name !== 'UserPromptSubmit') return;
|
|
272
272
|
const [mode, scope] = projectSettings(event.cwd);
|
|
273
273
|
rememberHistorySource(event, mode);
|
|
274
|
-
if (mode
|
|
275
|
-
|
|
276
|
-
|
|
277
|
-
|
|
278
|
-
|
|
279
|
-
|
|
280
|
-
|
|
281
|
-
|
|
282
|
-
}
|
|
274
|
+
if (mode !== 'auto') return;
|
|
275
|
+
const lang = language(event.cwd);
|
|
276
|
+
const paused = workflowCooldown(scope, decisionsSettings(event.cwd).decisions_enabled);
|
|
277
|
+
const additionalContext = paused
|
|
278
|
+
? tr('自动润色因上次服务故障暂时暂停。常规回复请在最终消息里注明本轮未润色,再给出 GPT 原稿。遵守用户的格式要求;若本轮明确点名润色,可按技能手动重试。',
|
|
279
|
+
'Automatic polishing is temporarily paused after a service failure. For ordinary replies, mark the final answer as unpolished and show the original GPT draft. Honor the requested format. An explicit polish request can still use the skill.', lang)
|
|
280
|
+
: tr('本项目已开启自动改写。完成任务后,在发送最终回复前使用已安装的 codex-polish:codex-polish 技能。常规回复请在最终消息中显示润色结果和完整 GPT 原稿,两版相同时注明并只显示一次。遵守用户指定的输出格式、取消或禁止外发的要求。',
|
|
281
|
+
'Automatic rewriting is on for this project. Before sending the final answer, use the installed codex-polish:codex-polish skill. In ordinary replies show the result and the full original GPT draft. If identical, label it and show it once. Honor the requested format, cancellations, and requests to keep content local.', lang);
|
|
282
|
+
console.log(JSON.stringify({ hookSpecificOutput: { hookEventName: 'UserPromptSubmit', additionalContext } }));
|
|
283
283
|
}
|
|
284
284
|
|
|
285
285
|
const commands = {
|
|
@@ -5,32 +5,34 @@ description: Polishes Codex's final reply with Gemini when you ask or a trusted
|
|
|
5
5
|
|
|
6
6
|
# 润色本轮回复
|
|
7
7
|
|
|
8
|
-
|
|
8
|
+
先完成用户任务,准备一份可以直接发出的完整回复,作为本轮的 GPT 原稿。保留这份原稿直到交付。只在最终答复前运行一次,不润色工具调用、进度消息或待原样交付的文件。
|
|
9
9
|
|
|
10
|
-
##
|
|
10
|
+
## 触发与输出格式
|
|
11
11
|
|
|
12
|
-
用本文件的安装位置定位 `scripts/`、`references/` 和 `../../hooks/preferences.mjs
|
|
12
|
+
用本文件的安装位置定位 `scripts/`、`references/` 和 `../../hooks/preferences.mjs`。记住本轮开始时的绝对工作目录(可以是仓库子目录),后面的 `--cwd` 始终用它。用户本轮主动点名时用 `--trigger explicit`。普通提问只有收到本轮受信任的 `UserPromptSubmit` 提醒才用 `--trigger auto`。重复的提醒只处理一次。
|
|
13
13
|
|
|
14
|
-
|
|
14
|
+
用户取消就结束。用户禁止外发或要求 JSON、命令、补丁、逐字引用等固定格式时,按用户要求直接答复。用户明确只想看润色后的正文时,走下述润色流程,最终只交付选定的正文。其他情况下,润色结果与原稿都要在**用户可见的最终消息**中交代。
|
|
15
15
|
|
|
16
|
-
|
|
16
|
+
用 Node.js 22.16 或更新版本运行 `node …/hooks/preferences.mjs check --cwd "<原项目目录>"`。模式为 `off`,或仅由提醒触发且模式为 `manual` 时,按普通回复交付。记下 `gemini_model`(默认 `gemini-4-hydrogen`)、`google_auth_method` 和本轮的显示语言。状态和标题使用项目设置的中文或英文。语言为自动时跟随本轮用户的语言,无法判断时用 `check.ui_language`。原稿和改稿保持原稿的语言。
|
|
17
17
|
|
|
18
|
-
|
|
18
|
+
材料不适合外发、执行工具不能持续读写并回收同一子进程、Node.js 或帮助脚本不可用、`blockers` 非空、自动触发且 `cooldown` 非空时,按下文“保留原稿”交付。CLI 能否找到 `codex` 供安装排查参考,正在运行的宿主可以直接提供执行工具。
|
|
19
19
|
|
|
20
|
-
|
|
20
|
+
## 判定与改写
|
|
21
21
|
|
|
22
|
-
|
|
23
|
-
2. 看本轮 `check.decisions_enabled`。为真时选择 `decisions`,为假时选择 `acp`。运行 `node …/hooks/preferences.mjs decision judge --cwd "<原项目目录>" --trigger <auto或explicit> --route <所选路由>`,等待 `action: "rewrite"`。保存返回的 `route` 和可能的 `recovery_token`。两条路径的输入如下。
|
|
24
|
-
- `acp`:这个入口只在本地检查项目模式、依赖和冷却状态,标准输入留空。符合条件就继续改写,即便原稿已经很通顺。
|
|
25
|
-
- `decisions`:从标准输入提供受保护的 `question` 和 `draft`,供 OpenAI 做风格判定。需要改写的概率达到 0.80 才继续。
|
|
26
|
-
3. 读取 [ACP 操作步骤](references/acp.md)。**你就是 ACP 客户端。** 在本轮用你的持久执行工具启动官方 `agy acp`,对同一个进程逐条收发。按步骤用 acp_payload.mjs 组装一次改写请求,由当前 agent 将它直接交给同一个进程。不要委派给子 agent,不写或启动 ACP 驱动脚本、MCP 代理或后台服务。发送 prompt 前再运行第一个 `check`,确认原项目仍允许本次调用、Decisions 路由与第 2 步一致、`gemini_model` 与建立 ACP 会话前相同且本轮要求仍有效,再提交一次。当前要求仅允许外发本轮内容时,按 ACP 步骤省略历史。发生服务故障且用户仍在等待时,按操作步骤收尾,用 `node …/hooks/preferences.mjs note-failure <固定故障码> --cwd "<原项目目录>"` 记录原因,再交付原稿。记录失败也交付原稿。
|
|
27
|
-
4. 调用 `scripts/text_guard.mjs restore`,输入原始 `question`、原始 `draft` 和受保护的 `candidate`。仅当返回 `ok: true`,才保留还原的 `text`。若 `route` 为 `decisions` 且它与原稿相同,可以直接交付原稿。
|
|
28
|
-
5. 调用 `node …/hooks/preferences.mjs decision verify --cwd "<原项目目录>" --trigger <auto或explicit> --route <第2步返回的route>`。第 2 步返回了恢复标记时传入 `--recovery-token <标记>`。
|
|
29
|
-
- `acp`:标准输入留空。本地确认项目仍允许改写后,返回 `action: "accept"` 即逐字交付第 4 步还原的正文。这条路径没有模型原意复核。
|
|
30
|
-
- `decisions`:从标准输入提供受保护的 `question`、`draft` 和 ACP 返回的 `candidate`。仅在 OpenAI 判断实质变化概率不超过 0.05 且返回 `action: "accept"` 时交付还原稿。
|
|
22
|
+
脚本从标准输入读取 UTF-8 JSON,输出 JSON。使用宿主的安全 stdin。只有 shell 可用时,用 JSON 序列化器生成单行 JSON,再用单引号 heredoc 分隔符送入脚本。不要把正文当作 shell 代码执行,不写草稿到项目文件。检查退出状态、完整结果和返回字段,失败时保留原稿。
|
|
31
23
|
|
|
32
|
-
|
|
24
|
+
1. 调用 `scripts/text_guard.mjs prepare`,输入 `{"question":问题,"draft":原稿}`。两项只含本轮问题及其当前要求和完整原稿,不加入展示用的标题。若 `bypass` 为真,保留原稿,固定格式按用户要求直接交付。保存返回的 `protected_question` 和 `protected_draft`。
|
|
25
|
+
2. `check.decisions_enabled` 为真时选择 `decisions`,否则选择 `acp`。运行 `node …/hooks/preferences.mjs decision judge --cwd "<原项目目录>" --trigger <auto或explicit> --route <所选路由>`。只在 `action: "rewrite"` 时继续。保存返回的 `route` 和可能的 `recovery_token`。
|
|
26
|
+
- `acp` 的标准输入留空。此入口在本地检查项目模式、依赖和冷却状态。通过就继续,即便原稿已经很通顺。
|
|
27
|
+
- `decisions` 从标准输入接收受保护的 `question` 和 `draft`。OpenAI 判断需要改写的概率达到 0.80 才继续。`reason: "already_clear"` 时保留原稿,并说明 OpenAI 判断无需润色。
|
|
28
|
+
3. 读取 [ACP 操作步骤](references/acp.md)。**你就是 ACP 客户端。** 用本轮的持久执行工具启动官方 `agy acp`,对同一进程逐条收发。默认 `existing-session` 使用已有登录,显式指定 API key 或企业身份才发送对应认证请求。发送 prompt 时,在同一个工具调用中把 `acp_payload.mjs` 的 stdout 直接重定向到已打开的 ACP 输入(见参考命令)。不要先打印整帧再抄到下一次调用。不要委派给子 agent,不写或启动 ACP 驱动脚本、MCP 代理或后台服务。脚本按项目设置自动附上最近完整问答,默认 2 轮、最多 10 轮。不要自行查阅、挑选或概括。若本轮要求省略历史,按操作步骤只发本轮材料。提交 prompt 前再运行第一个 `check`,确认原项目仍允许调用、Decisions 路由和所选模型一致、用户要求仍有效,只提交一次。服务故障按步骤收尾,用 `node …/hooks/preferences.mjs note-failure <固定故障码> --cwd "<原项目目录>"` 记录,再保留原稿。记录失败也保留原稿。
|
|
29
|
+
4. 调用 `scripts/text_guard.mjs restore`,传入最初的原始 `question`、`draft` 和受保护的 `candidate`。常规回复同时传入 `display_language`(`zh` 或 `en`)。用户明确只看润色正文时省略此字段。只有 `ok: true` 才保留已经还原的 `text` 及常规回复的 `display_text`。确保工具输出预算足以取得完整结果,优先在宿主内解析后只取需要展示的字段。候选校验不通过时只交付原稿。若 `route` 为 `decisions` 且还原后的 `text` 与原稿逐字相同,进入交付,无需再请求 OpenAI。
|
|
30
|
+
5. 否则运行 `node …/hooks/preferences.mjs decision verify --cwd "<原项目目录>" --trigger <auto或explicit> --route <第2步返回的route>`。有恢复标记时传 `--recovery-token <标记>`。直接 `acp` 路径标准输入留空,本地核对项目仍允许改写。`decisions` 从标准输入接收受保护的 `question`、`draft` 与 ACP 返回的 `candidate`,实质变化概率不超过 0.05 才采用。只在 `action: "accept"` 时交付候选。路由变化、检查未通过或失败时保留原稿。
|
|
33
31
|
|
|
34
|
-
|
|
32
|
+
## 在最终消息中交付
|
|
35
33
|
|
|
36
|
-
|
|
34
|
+
- **常规回复**逐字发送第 4 步的 `display_text`。有改动时,其中先是 Gemini 润色版,再是最初的完整 GPT 原稿。两版逐字相同时,其中只出现一次正文,标题说明 Gemini 返回了相同原稿。不要另写前言、摘要或差异说明,不要让用户去工具日志查原稿。
|
|
35
|
+
- **保留原稿**时,在最初的完整原稿前用界面语言说明本轮的实际结果。发送前跳过可写“本轮未润色,以下是 GPT 原稿。”OpenAI 判断无需改写可写“OpenAI 判断无需润色,以下是 GPT 原稿。”请求失败写“润色未完成,以下是 GPT 原稿。”改稿被拒写“润色稿未通过检查,以下是 GPT 原稿。”只说明有证据的原因,不展示被拒的内容、占位符、凭据或服务端原始报错。
|
|
36
|
+
- **只看润色正文**时,采用候选就逐字发送 `text`,否则逐字发送最初的原稿。不加标题、状态或对照。固定格式、关闭、取消继续遵守前述规则。
|
|
37
|
+
|
|
38
|
+
不为展示多调用一次模型,不重发结果不明或失败的付费请求。若上下文恢复后无法确认先前的请求状态,放弃候选。用户中途修正要求就丢弃旧候选,回答最新要求。排查故障时可报告阶段、固定故障码和剩余等待时间。
|
|
@@ -20,7 +20,7 @@
|
|
|
20
20
|
3. 对输入管道逐次写入一条完整的 JSON 行,然后从同一运行句柄读返回值。用执行工具在临时目录执行 `printf '%s\n' '<已安全引用的一帧>' > .acp-in`;有参数的文本始终交给 JSON 序列化器和安全引用,不拼入命令代码。若管道写入阻塞,限定在同一控制请求的期限内中断本次写入并回收服务。每帧通过 JSON 序列化器生成,末尾追加一个换行。正文中的换行属于 JSON 字符串;不可拆成多个请求或把正文当作 shell 命令执行。先发下列帧并等待对应的 `id`:
|
|
21
21
|
|
|
22
22
|
```json
|
|
23
|
-
{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":1,"clientCapabilities":{},"clientInfo":{"name":"codex-polish","version":"0.0.1-beta.
|
|
23
|
+
{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":1,"clientCapabilities":{},"clientInfo":{"name":"codex-polish","version":"0.0.1-beta.3"}}}
|
|
24
24
|
```
|
|
25
25
|
|
|
26
26
|
确认 `result.protocolVersion == 1`。生产中若服务端提供 `agentInfo.name`,应与官方 `Antigravity ACP Server` 一致,身份或协议版本冲突记 `acp_protocol_error`。
|
|
@@ -58,10 +58,9 @@
|
|
|
58
58
|
发送 prompt 前,用 [请求组装脚本](../scripts/acp_payload.mjs) 的绝对路径和**原项目目录**。脚本通过标准输入接收 `{"sessionId":"<本次 ACP 会话>","question":"<受保护的本轮问题>","draft":"<受保护的原稿>"}`。在本轮临时目录执行以下命令,将返回的一条 JSON-RPC 帧直接交给已经打开的官方进程。用本轮真实值替换示例内容。命令只把历史保存在内存中,不要先打印帧、让模型复述历史或把帧写入文件。
|
|
59
59
|
|
|
60
60
|
```sh
|
|
61
|
-
|
|
61
|
+
node "<插件内 acp_payload.mjs 的绝对路径>" --cwd "<原项目绝对路径>" > .acp-in <<'CODEX_POLISH_INPUT'
|
|
62
62
|
{"sessionId":"<本次 ACP 会话>","question":"<受保护的问题>","draft":"<受保护的原稿>"}
|
|
63
63
|
CODEX_POLISH_INPUT
|
|
64
|
-
) && printf '%s\n' "$frame" > .acp-in
|
|
65
64
|
```
|
|
66
65
|
|
|
67
66
|
使用原生 stdin 通道时,在同一工具调用内部将脚本成功返回的完整 stdout 直接写入进程句柄,输出预算须足以容纳整帧。截断、脚本报错或传输结果不明时沿用原稿,不尝试重发。用户本轮禁止附带历史时,省略 `--cwd`;禁止外发时跳过整个流程。
|
|
@@ -27,7 +27,8 @@ const EXACT = new RegExp([
|
|
|
27
27
|
/(?:只要|仅需)\s*(?:一(?:条|行|个)\s*)?(?:命令|代码|json|补丁)/.source,
|
|
28
28
|
/(?:原样|逐字|一字不改地?)\s*(?:输出|返回|复述|引用|复制)/.source,
|
|
29
29
|
/(?:固定|严格按(?:照)?|完全按照|严格遵守)(?:指定|以下|下面|这个|此)?格式/.source,
|
|
30
|
-
|
|
30
|
+
// A final "return only the polished text" clause requests a rewrite without headings.
|
|
31
|
+
/\b(?:return|output|reply with|give me|print)\s+(?:exactly\b|only\b(?!\s+(?:the\s+)?polished\s+(?:text|reply|answer|version|prose|body)[.!?]?\s*$))/.source,
|
|
31
32
|
/\b(?:json|yaml|code|commands?|patch|diff)\s+only\b|\bverbatim\b/.source,
|
|
32
33
|
].join('|'), 'iu');
|
|
33
34
|
|
|
@@ -65,6 +66,10 @@ const FENCE = /^ {0,3}(`{3,}|~{3,})/;
|
|
|
65
66
|
const FROZEN_LINE = /^(?:[ \t]*>| {4,}\S|\t\S|[ \t]*\[[^\]]+\]:|[ \t]*\|.*\||[ \t]*(?:-{3,}|\*{3,}|_{3,})[ \t]*$|[ \t]*(?:\$ |PS> )\S)/;
|
|
66
67
|
const COMMAND_LINE = new RegExp('^[ \\t]*(?:' + COMMANDS + /(?:[ \t]+[ -~]*)?|(?:\.\/|~\/|\/)[A-Za-z0-9_./-]+[ \t]+[ -~]+/.source + ')$');
|
|
67
68
|
const STRUCTURE = /^([ \t]*)(#{1,6}(?=\s)|[-*+](?=\s)|[0-9]+[.)](?=\s)|>|\||`{3,}|~{3,}|\[[^\]]+\]:)/;
|
|
69
|
+
const DISPLAY_LABELS = {
|
|
70
|
+
zh: { polished: 'Gemini 润色版', original: 'GPT 原稿', unchanged: 'Gemini 已核对,和 GPT 原稿相同' },
|
|
71
|
+
en: { polished: 'Polished by Gemini', original: 'Original GPT draft', unchanged: 'Gemini reviewed the GPT draft and left it unchanged' },
|
|
72
|
+
};
|
|
68
73
|
|
|
69
74
|
class Skip extends Error {}
|
|
70
75
|
|
|
@@ -183,7 +188,14 @@ export function run(action, payload) {
|
|
|
183
188
|
if (!isDeepStrictEqual([...actual.values()], [...literals.values()])) throw new Skip('literal_changed');
|
|
184
189
|
if (!isDeepStrictEqual(structure(text), structure(payload.draft)) || STRUCTURED.test(text))
|
|
185
190
|
throw new Skip('structure_changed');
|
|
186
|
-
|
|
191
|
+
const { draft, display_language } = payload;
|
|
192
|
+
if (display_language === undefined) return { ok: true, text };
|
|
193
|
+
if (display_language !== 'zh' && display_language !== 'en') throw new Skip('invalid_input');
|
|
194
|
+
const labels = DISPLAY_LABELS[display_language];
|
|
195
|
+
const display_text = text === draft
|
|
196
|
+
? `**${labels.unchanged}**\n\n${draft}`
|
|
197
|
+
: `**${labels.polished}**\n\n${text}\n\n**${labels.original}**\n\n${draft}`;
|
|
198
|
+
return { ok: true, text, display_text };
|
|
187
199
|
} catch (error) {
|
|
188
200
|
if (!(error instanceof Skip)) throw error;
|
|
189
201
|
return action === 'prepare' ? { bypass: true, reason: error.message } : { ok: false, reason: error.message };
|
|
@@ -47,6 +47,8 @@ Show every returned Gemini name in provider order. Mark the **project's saved ch
|
|
|
47
47
|
|
|
48
48
|
Use the guide in the conversation's language for Antigravity sign-in, optional OpenAI key creation, or enterprise identities. Never ask users to paste keys in chat. `existing-session` uses Antigravity's own login. If ACP reports authentication required, ask the user to open `agy` in a terminal on the machine running Codex and sign in. Google AI Studio keys apply only when the user explicitly selects `gemini-api-key`. Offer the English or Chinese guide for that exact case.
|
|
49
49
|
|
|
50
|
-
For “为什么没改写 / Why wasn't my reply polished?”,
|
|
50
|
+
For “为什么没改写 / Why wasn't my reply polished?”, use the status and available trace for that turn. The original can appear because Gemini returned the same text, the draft was never sent, the request failed, or the candidate failed a check. Report only the stage you can establish. A successful rewrite normally shows both versions in the final reply. A user who requests only the polished text sees one body, and exact-output requests keep their required format. For a cooldown, give the remaining time and remedy.
|
|
51
|
+
|
|
52
|
+
A request to **test the connection** authorizes the ACP initialize handshake and cleanup without a draft. A successful handshake establishes connectivity. Successfully opening a session and reading the model menu also checks the signed-in account. Do not use a writing request to test setup without the user asking.
|
|
51
53
|
|
|
52
54
|
Use `project-hook` only when the host has not loaded the plugin hook and the user asks for a project hook. Merge it into `.codex/hooks.json` without duplicating an existing handler. The user trusts it in Codex.
|