@akasecurity/ai-tc-codex 0.9.14 → 0.9.16
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/.codex-plugin/plugin.json +1 -1
- package/hooks/hooks.json +1 -1
- package/package.json +5 -5
- package/scripts/apply-suppressions.js +1828 -463
- package/scripts/backfill.js +2406 -518
- package/scripts/content-retention.js +1002 -275
- package/scripts/filescan.js +2323 -435
- package/scripts/firstrun.js +1643 -363
- package/scripts/history-sync.js +1024 -282
- package/scripts/intro.js +385 -178
- package/scripts/onboard.js +985 -260
- package/scripts/post-tool-use.js +2446 -439
- package/scripts/pre-tool-use.js +2350 -434
- package/scripts/query.js +1642 -362
- package/scripts/reconcile.js +2297 -413
- package/scripts/remediate.js +2281 -444
- package/scripts/scan-worker.js +514 -175
- package/scripts/session-start.js +2292 -421
- package/scripts/start-light.js +385 -178
- package/scripts/stop.js +481 -207
- package/scripts/sync.js +2322 -434
- package/scripts/user-prompt-submit.js +2392 -469
- package/skills/setup/SKILL.md +27 -12
package/skills/setup/SKILL.md
CHANGED
|
@@ -806,18 +806,33 @@ watching out for Codex going forward."
|
|
|
806
806
|
Before you finish, confirm every AKA_SHOW region on the path you took was
|
|
807
807
|
relayed to the user. If you summarized one instead of pasting it, paste it now.
|
|
808
808
|
|
|
809
|
-
## Known
|
|
810
|
-
|
|
811
|
-
Live
|
|
812
|
-
|
|
813
|
-
|
|
814
|
-
|
|
815
|
-
|
|
816
|
-
|
|
817
|
-
|
|
818
|
-
|
|
819
|
-
|
|
820
|
-
|
|
809
|
+
## Known limitations
|
|
810
|
+
|
|
811
|
+
Live scanning covers `Bash` shell calls and `apply_patch` file writes before
|
|
812
|
+
they run, and the output of shell calls, Codex's web tool and MCP tools after
|
|
813
|
+
they return. That includes the calls a code-mode `exec` makes: Codex fires the
|
|
814
|
+
hooks for each tool the script calls (confirmed on codex-cli 0.160.0). The
|
|
815
|
+
script itself fires no hook, so it is seen only through those calls, and web
|
|
816
|
+
and MCP tool **inputs** are not scanned on the way in.
|
|
817
|
+
|
|
818
|
+
The full text of every `apply_patch` call is **recorded in the local store**,
|
|
819
|
+
with the values AKA detects masked, whether or not anything was found, the
|
|
820
|
+
same as file writes on the other assistants AKA covers. That record is what a
|
|
821
|
+
later re-scan checks against. Shell commands and tool output are recorded only
|
|
822
|
+
when something is detected. Old bodies are cleared only if local body expiry is
|
|
823
|
+
turned on in the workspace settings. A very large tool result is scanned up to
|
|
824
|
+
a bound (5 million characters or 2,000 pieces, and about 7 seconds), past which
|
|
825
|
+
the rest reaches the model unscanned.
|
|
826
|
+
|
|
827
|
+
On a Codex release that fires these hooks for `Bash` alone, file-write
|
|
828
|
+
**content is not scanned at all** — not live, and not after the fact either.
|
|
829
|
+
The consent-gated historical scan this wizard offers in steps 1/3 reads
|
|
830
|
+
conversation messages only, and the tool-call reconciler records a write's
|
|
831
|
+
changed paths and byte sizes, never the bytes themselves. So there a secret
|
|
832
|
+
written into a file through `apply_patch` is neither redacted before it lands
|
|
833
|
+
nor reported afterwards; only the path is recorded. If the user asks why a
|
|
834
|
+
secret in a file edit wasn't caught, say so plainly rather than implying it is
|
|
835
|
+
picked up somewhere else.
|
|
821
836
|
|
|
822
837
|
A redact policy cannot mask a **shell command**, because rewriting one silently
|
|
823
838
|
changes what runs. What happens in its place is the workspace's **redact fallback** (`redactFallback` in
|