@akasecurity/ai-tc-codex 0.9.10 → 0.9.12
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/package.json +4 -4
- package/scripts/apply-suppressions.js +1766 -952
- package/scripts/backfill.js +2091 -1176
- package/scripts/content-retention.js +33995 -0
- package/scripts/filescan.js +2148 -1101
- package/scripts/firstrun.js +1992 -1066
- package/scripts/history-sync.js +1943 -1037
- package/scripts/intro.js +532 -122
- package/scripts/onboard.js +1750 -927
- package/scripts/post-tool-use.js +2246 -1333
- package/scripts/pre-tool-use.js +2093 -1171
- package/scripts/query.js +1997 -1071
- package/scripts/reconcile.js +2050 -1157
- package/scripts/remediate.js +2139 -1177
- package/scripts/scan-worker.js +388 -74
- package/scripts/session-start.js +2123 -1211
- package/scripts/start-light.js +530 -120
- package/scripts/stop.js +566 -150
- package/scripts/sync.js +2144 -1099
- package/scripts/user-prompt-submit.js +2082 -1167
- package/skills/setup/SKILL.md +15 -4
package/skills/setup/SKILL.md
CHANGED
|
@@ -797,10 +797,11 @@ what happened, show the one-liner so they can retry later, and continue the
|
|
|
797
797
|
wizard normally. The plugin is already fully set up and works on its own; a
|
|
798
798
|
failed CLI install changes nothing about that.
|
|
799
799
|
|
|
800
|
-
**Close the wizard.** The first-run summary already confirmed the saved posture
|
|
801
|
-
and pointed at the aka-
|
|
802
|
-
|
|
803
|
-
warm close: "That's it — I'm
|
|
800
|
+
**Close the wizard.** The first-run summary already confirmed the saved posture,
|
|
801
|
+
reported the health score, and pointed at the aka-dashboard and aka-scan
|
|
802
|
+
skills. Whichever way the CLI offer went — installed, declined, or a failed
|
|
803
|
+
install you already reported — end with one warm close: "That's it — I'm
|
|
804
|
+
watching out for Codex going forward."
|
|
804
805
|
|
|
805
806
|
Before you finish, confirm every AKA_SHOW region on the path you took was
|
|
806
807
|
relayed to the user. If you summarized one instead of pasting it, paste it now.
|
|
@@ -818,6 +819,16 @@ neither redacted before it lands nor reported afterwards; only the path is
|
|
|
818
819
|
recorded. If the user asks why a secret in a file edit wasn't caught, say so
|
|
819
820
|
plainly rather than implying it is picked up somewhere else.
|
|
820
821
|
|
|
822
|
+
A redact policy cannot mask a **shell command**, because rewriting one silently
|
|
823
|
+
changes what runs. What happens in its place is the workspace's **redact fallback** (`redactFallback` in
|
|
824
|
+
`~/.aka/settings/settings.json`, or pinned for a machine by an administrator). It ships as **warn**, which means the command
|
|
825
|
+
**runs with the value unmasked** and AKA says so in the session. Set it to
|
|
826
|
+
**block** to get the older behaviour, where the call is denied and the message
|
|
827
|
+
explains what to remove. The `apply_patch` field is different: it is stored
|
|
828
|
+
text rather than a command, so it is masked in place and keeps true redaction at
|
|
829
|
+
either setting. Whichever applies, the finding records the action that actually
|
|
830
|
+
happened, never a "redact" that did not.
|
|
831
|
+
|
|
821
832
|
The reversible secret vault is not yet wired for Codex sessions, so this wizard
|
|
822
833
|
does not offer the vault-consent step: everything AKA redacts here is one-way
|
|
823
834
|
(the safe direction), and nothing this plugin captures is ever vaulted — even
|