@ascenda-one/codex-hooks 0.1.33 → 0.1.35

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/NOTICE ADDED
@@ -0,0 +1,4 @@
1
+ @ascenda-one/codex-hooks
2
+ Copyright 2026 Ascenda One Pty Ltd
3
+
4
+ Licensed under the Apache License, Version 2.0. See LICENSE.
package/README.md CHANGED
@@ -38,7 +38,7 @@ Codex **awaits** command hooks and treats **exit code 2 as blocking** the user's
38
38
  One command pairs Codex, installs the hook binary, and registers the hooks:
39
39
 
40
40
  ```bash
41
- npx -y @ascenda-one/codex-hooks setup --scope user
41
+ npx -y @ascenda-one/codex-hooks setup
42
42
  ```
43
43
 
44
44
  It prints a 6-digit code — confirm it in the Ascenda app under
@@ -53,23 +53,29 @@ credentials file, which is per agent — so pairing Codex cannot disturb a
53
53
  Claude Code or Cursor pairing on the same machine, and a Codex hook launched
54
54
  from the Dock with an empty environment still names itself correctly.
55
55
 
56
- `--scope user` registers machine-wide. Omit it and hooks land in
57
- `<cwd>/.codex/hooks.json`, instrumenting that project only — which is the
58
- default, so pass the flag unless you mean one repo.
56
+ Hooks register machine-wide by default. `--scope project` puts them in
57
+ `<cwd>/.codex/hooks.json` instead, for that project only. Each hook runs
58
+ through a small launcher at `~/.ascenda/bin/ascenda-codex-hook` that finds
59
+ Node 20 or newer itself, so hooks keep working when Codex starts without
60
+ your shell's PATH. `--no-pair` installs without pairing: the screen saver
61
+ and live view work, and nothing is sent.
59
62
 
60
63
  ### 2. Check it
61
64
 
62
65
  ```bash
63
- npx @ascenda-one/codex-hooks status --scope user
66
+ npx @ascenda-one/codex-hooks status
67
+ ~/.ascenda/bin/ascenda-codex-hook doctor
64
68
  ```
65
69
 
66
- Names the pairing, the binary and how many of the 7 events are registered.
67
- Exits non-zero when something is missing, so it can gate a CI step.
70
+ `status` names the pairing, the Node the hooks will run, the last hook Codex
71
+ ran and how many events are registered. It exits non-zero when something is
72
+ missing, so it can gate a CI step. `doctor` also checks the live signal, and
73
+ pings the Waterline screen saver when it is running.
68
74
 
69
75
  To undo everything it wrote:
70
76
 
71
77
  ```bash
72
- npx @ascenda-one/codex-hooks uninstall --scope user
78
+ npx @ascenda-one/codex-hooks uninstall
73
79
  ```
74
80
 
75
81
  ### 3. Restart Codex and review hooks
@@ -127,7 +133,9 @@ event. Check the local event log for `metadata.host: "codex"` and confirm its
127
133
  `toolInstallationId` matches `tools.codex` in the credentials file. The hook
128
134
  always exits `0`, so its exit code alone cannot prove delivery.
129
135
 
130
- Set `ASCENDA_EVENT_LOG_FILE` to also log each payload locally.
136
+ An unpaired install logs every payload to `~/.ascenda/events.jsonl`. On a
137
+ paired one, `setup --event-log` or `ASCENDA_EVENT_LOG_FILE` turns the same log
138
+ on, and `off` turns it off.
131
139
 
132
140
  ## Build from source
133
141