diff --git a/integrations/codex/README.md b/integrations/codex/README.md index 23578811..4e2db6b6 100644 --- a/integrations/codex/README.md +++ b/integrations/codex/README.md @@ -64,7 +64,9 @@ Restart the desktop app, or start a new CLI session. Open the installed ReMe ent ![ReMe installed and enabled in Codex](./figures/plugin-installed.png) --> -In Codex's Hooks settings, review and trust **every ReMe entry** (currently seven). In the CLI, use `/hooks`. +In the desktop app, add and open a local project folder before entering **Settings → Hooks**. +Select **Local** if a host selector is shown, then review and trust **every ReMe entry** (currently seven). +In the CLI, start `codex` from your project folder and use `/hooks`. This enables automatic recording and recall. A healthy service connection alone does not enable them. After an update, review any changed entries again. See [Codex Hook review and trust](https://learn.chatgpt.com/docs/hooks#review-and-trust-hooks). @@ -220,6 +222,7 @@ with the previous address; switch back to retry them. Changes made during consol | Symptom | Check | | --- | --- | | No MCP settings entry | Confirm your desktop version meets the requirement above, then open the installed ReMe detail and its `reme` MCP card; confirm it is enabled and restart. | +| Hooks settings keep loading or do not show ReMe | Open a local project folder and select the local host before reopening Hooks settings; see below. | | Blank status card followed by a plugin feature loading error | Check network access to the Codex sandbox page; see below. | | Connection healthy, no recording or recall | Review every ReMe Hook; check the auto switches and recent activity. Health does not prove Hook execution. | | Turns stay queued | Keep Codex and ReMe running. Check the ReMe model configuration and service logs, and confirm the startup command includes `service.tool_error_on_failure=true`. | @@ -228,6 +231,26 @@ with the previous address; switch back to retry them. Changes made during consol | Unknown configuration fields after upgrading | Back up `~/.codex/reme/config.json`, compare it with the [current configuration example](plugins/reme/config.example.json), and update obsolete fields before reopening settings. | | Python or FastMCP startup error | Check the `python3` environment inherited by Codex, including the desktop app. | +
+Hooks settings keep loading + +Codex lists Hooks in the context of project folders. First add and open a local folder in the desktop +app, select **Local** if a host selector is shown, and reopen **Settings → Hooks**. Use **Reload hooks** +when available. After installing or updating ReMe, restart Codex if the list remains stale. + +If the desktop page still does not load, use the CLI from the same project folder: + +```bash +cd /absolute/path/to/project +codex +``` + +Enter `/hooks`, then review the ReMe entries and their enabled and trusted states. Use the same +`CODEX_HOME` as the desktop app if you have customized it. A desktop page that keeps loading does not +by itself show that Hooks failed to run; check ReMe's recent activity to verify recording and recall. + +
+
The status card is blank or reports a loading error diff --git a/integrations/codex/README_ZH.md b/integrations/codex/README_ZH.md index 1c7e4651..5f85241f 100644 --- a/integrations/codex/README_ZH.md +++ b/integrations/codex/README_ZH.md @@ -61,7 +61,9 @@ codex plugin add reme@reme-codex ![Codex 中已安装并启用 ReMe](./figures/plugin-installed.png) --> -在 Codex 的 Hooks 设置中,审核并信任 **所有 ReMe 条目**(目前共七个);CLI 可使用 `/hooks`。 +桌面端请先添加并打开一个本地项目文件夹,再进入 **Settings → Hooks**。 +如果出现主机选择,选择 **Local**,然后审核并信任 **所有 ReMe 条目**(目前共七个)。 +CLI 请在项目目录启动 `codex`,再使用 `/hooks`。 完成这一步才能自动记录和召回。仅连接服务并不会启用这些能力。 升级后如条目发生变化,需要重新审核。参见 [Codex Hook 审核与信任说明](https://learn.chatgpt.com/docs/hooks#review-and-trust-hooks)。 @@ -214,6 +216,7 @@ ReMe-Example-7319 的评审时间和项目关键词是什么? | 现象 | 检查方式 | | --- | --- | | 找不到 MCP 设置 | 确认桌面端符合上述版本要求,再打开已安装的 ReMe 详情及 `reme` MCP 卡片;确认启用后重启。 | +| Hooks 设置一直加载或没有 ReMe | 先打开本地项目文件夹并选择本机,再重新进入 Hooks 设置;见下方说明。 | | 状态卡片空白,随后提示“插件功能未成功加载” | 检查 Codex 沙箱页面的网络访问;见下方说明。 | | 连接健康,但没有记录或召回 | 检查全部 ReMe Hook 的信任状态、自动开关及最近活动;连接健康不代表 Hook 已执行。 | | 记录一直在队列中 | 保持 Codex 和 ReMe 运行,检查 ReMe 模型配置和服务日志,并确认启动命令包含 `service.tool_error_on_failure=true`。 | @@ -222,6 +225,25 @@ ReMe-Example-7319 的评审时间和项目关键词是什么? | 升级后提示未知配置字段 | 备份 `~/.codex/reme/config.json`,对照[当前配置示例](plugins/reme/config.example.json)更新旧字段,再打开设置。 | | Python 或 FastMCP 启动报错 | 检查 Codex 实际继承的 `python3` 环境,尤其是桌面端的启动环境。 | +
+Hooks 设置一直加载 + +Codex 需要项目目录来列出 Hook。请先在桌面端添加并打开一个本地文件夹,若有主机选择则选择 +**Local**,然后重新进入 **Settings → Hooks**。如果 **Reload hooks** 可用,点击刷新。 +安装或升级 ReMe 后,如果列表仍未更新,重启 Codex。 + +如果桌面端页面仍无法加载,可以在同一个项目目录使用 CLI: + +```bash +cd /absolute/path/to/project +codex +``` + +输入 `/hooks`,查看 ReMe 条目及启用、信任状态。如果自定义过 `CODEX_HOME`,请使用与桌面端 +相同的目录。桌面页一直加载本身不能证明 Hook 没有执行;记录和召回是否生效仍需通过 ReMe 最近活动确认。 + +
+
状态卡片空白或提示加载失败 diff --git a/integrations/codex/figures/README.md b/integrations/codex/figures/README.md index f173cf51..edcd9705 100644 --- a/integrations/codex/figures/README.md +++ b/integrations/codex/figures/README.md @@ -63,11 +63,14 @@ If the card or settings action is missing, check the version and enablement, the ### 2. 审核并信任 Hook / Review and trust Hooks -进入 Hooks 设置,或在新 CLI 会话输入 `/hooks`。逐一审核 ReMe 条目,并由你在 Codex 中启用、信任。 +桌面端先打开本地项目文件夹,再进入 Hooks 设置;若有主机选择,选择 Local。 +也可以在该项目目录启动新 CLI 会话并输入 `/hooks`。逐一审核 ReMe 条目,并由你在 Codex 中启用、信任。 当前共七个条目:`UserPromptSubmit`、`SessionStart`、`SessionEnd` 各一个,`Stop` 和 `SubagentStop` 各两个。 保存为 `hooks-trusted.png`,保留事件名、ReMe 来源及信任状态。 若单页放不下,可另拍 `hooks-trusted-more.png`,按补图步骤在对应位置追加第二张图片。 +Open a local project folder before entering desktop Hooks settings; select Local if a host selector is shown. +Alternatively, start the CLI from that folder and enter `/hooks`. Review and trust the seven ReMe entries yourself. Capture their event names, plugin source, and trust state. Use a second image if the list does not fit legibly; do not shrink the text just to fit everything.