Jia-Ethan/codex-keysmith: README-based editorial guide

Jia-Ethan/codex-keysmith describes itself in the README as "Version-independent Codex instruction deployment with dry-run, backups, hook isolation, and recovery.". This article keeps to facts that can be checked in the repository. Stars, forks, and promotional badges are signals of attention, not proof of quality. Under "README", the README says: Versioned Codex instruction deployment with preview, ownership manifests, hook isolation, and layered uninstall.. That establishes the project's stated boundary, not a production test.

The README's "兼容性与限制" section gives a useful starting point for deciding whether the project fits: Windows：已发布的 v0.1.0 存在已知缺陷（os.utime 失败后触发第二个 PermissionError，会留下无法用旧脚本恢复的 journal）。v0.1.1 及后续版本已重写 Windows 文件系统后端并标记 EXPLICITBETA，可以试用，但还不是正式支持；如果 v0.1.0 留下了 journal，用最新已校验 Release 脚本按 --status → --recover 预览 → --recover --yes → --status. If that problem is not yours, popularity is a poor reason to adopt it. Project names, commands, and component names are kept as written so a reader can return to the primary source without guessing at terminology. Another checkable README item is: 推荐 Python 3.10,3.14；已验证 Codex CLI codex-cli 0.144.1。. It can shape a first test, but it does not replace testing in the intended environment.

The operating model is spread across sections such as "这是什么". The source evidence includes: 这会改变 Codex 的全局行为，不是项目级设置：部署会修改 /.codex/config.toml 里的 modelinstructionsfile，因此影响该配置下的所有新会话；默认还会暂停你现有的整份 hooks.json，直到你显式恢复。内置的示例提示词会让模型不再用拒绝式话术回答，把 reverse shell / keygen / bypass. This article does not turn missing architecture, performance, or security details into claims. A real deployment still needs a look at the repository layout, configuration files, and release history.

Start installation from the README's documented entry point. A command that can be checked in the source is: # 1. 下载并校验（把 vX.Y.Z 换成 Releases 页面上的最新 tag） base='https://github.com/Jia-Ethan/codex-keysmith/releases/download/vX.Y.Z' curl --fail --location --remote-name "$base/codex-instruct-vX.Y.Z.py" curl --fail --location --remote-name "$base/SHA256SUMS" shasum -a 256 -c SHA256SUMS # 2. 先看，不要先信,,确认目标目录、内置提示词来源和将要写入的内容 python3 codex-instruct-vX.Y.Z.py --version python3 codex-instruct-vX.Y.Z.py --codex-dir ~/.codex --status --lang zh-CN python3 codex-instruct-vX.Y.Z.py --codex-dir ~/.codex --dry-run --lan When the README contains no runnable command, this article does not invent one. Open its "这是什么" section and confirm system dependencies, default ports, and first-run initialization before using a public server.