@runcanary/cli 0.1.12 → 0.1.14
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/README.md +7 -0
- package/dist/canary.js +180 -123
- package/package.json +3 -2
package/README.md
CHANGED
|
@@ -31,6 +31,13 @@ After the CLI is gone, `npx -y @runcanary/cli hooks uninstall` removes the same
|
|
|
31
31
|
never touches anything but an agent's push or pull-request call, and lets that through whenever
|
|
32
32
|
Canary cannot answer.
|
|
33
33
|
|
|
34
|
+
On Codex the entry goes in `~/.codex/hooks.json`. Codex before 0.124 also runs no hooks until
|
|
35
|
+
`codex_hooks = true` is set. Canary asks your Codex whether it needs that line, and only when it
|
|
36
|
+
does (or no Codex CLI here can be asked) adds it to `~/.codex/config.toml`: one line marked
|
|
37
|
+
`# added by canary`, after keeping a copy of the file under `~/.canary/backups/`, and named when
|
|
38
|
+
it is added. `canary hooks uninstall` takes it out again. A `hooks` or `codex_hooks` setting of
|
|
39
|
+
your own is never changed.
|
|
40
|
+
|
|
34
41
|
Add `--json` to any command for machine-readable output.
|
|
35
42
|
|
|
36
43
|
Browser login shows an animated Canary while waiting for authorization, then a
|