@akasecurity/ai-tc-copilot 0.9.20 → 0.9.21
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 +1 -1
- package/package.json +6 -6
- package/plugin.json +1 -1
- package/scripts/content-retention.js +83 -16
- package/scripts/fail-open-count.js +30 -9
- package/scripts/history-sync.js +287 -26
- package/scripts/post-tool-use.js +479 -120
- package/scripts/pre-tool-use.js +470 -118
- package/scripts/scan-worker.js +25 -2
- package/scripts/session-start.js +428 -134
- package/scripts/sync.js +679 -138
- package/scripts/user-prompt-submit.js +480 -121
- package/skills/setup/SKILL.md +55 -30
package/skills/setup/SKILL.md
CHANGED
|
@@ -58,10 +58,12 @@ Limits of this install:
|
|
|
58
58
|
- **The CLI warns that this install route is deprecated.** It says direct
|
|
59
59
|
installs from a path are being replaced by `plugin@marketplace` installs.
|
|
60
60
|
A marketplace install of this plugin has not been measured.
|
|
61
|
-
- **Hook notices
|
|
62
|
-
|
|
63
|
-
logging enabled (`--log-level debug --log-dir <dir>`).
|
|
64
|
-
|
|
61
|
+
- **Hook notices may not be on the screen yet.** In a recorded `-p` session on
|
|
62
|
+
Copilot CLI 1.0.98, AKA's messages appeared only in the CLI's debug log, with
|
|
63
|
+
debug logging enabled (`--log-level debug --log-dir <dir>`). AKA now also
|
|
64
|
+
sends each one as a hook progress line, which the Copilot hooks reference
|
|
65
|
+
documents as shown in the CLI timeline. That has not been observed on a real
|
|
66
|
+
install, in `-p` mode or in an interactive session.
|
|
65
67
|
- **Windows is unconfirmed.** The plugin has not been installed and run against
|
|
66
68
|
a real Copilot CLI on Windows, so whether its hook commands survive that
|
|
67
69
|
platform's shell is untested.
|
|
@@ -110,11 +112,12 @@ finding on the dashboard; **neither can be withheld or masked.** A `block` or
|
|
|
110
112
|
`redact` policy on one of those is recorded as a finding and the text goes to
|
|
111
113
|
the model unchanged. Under VS Code AKA returns the notice as a hook message,
|
|
112
114
|
and it appears only in VS Code's "GitHub Copilot Chat Hooks" output channel: in
|
|
113
|
-
the recorded session the chat showed nothing from AKA. On the CLI it
|
|
114
|
-
notice
|
|
115
|
-
|
|
116
|
-
|
|
117
|
-
|
|
115
|
+
the recorded session the chat showed nothing from AKA. On the CLI it sends the
|
|
116
|
+
notice as a hook progress line, which the hooks reference documents as shown in
|
|
117
|
+
the CLI timeline, and writes a copy to stderr. Neither has been seen on screen:
|
|
118
|
+
in a recorded `-p` session the stderr copy appeared only in Copilot's debug log,
|
|
119
|
+
with debug logging enabled (`--log-level debug`), and that session predates AKA's
|
|
120
|
+
use of progress lines. It never pretends it enforced.
|
|
118
121
|
|
|
119
122
|
The reason is that neither host has a channel for it that has been seen to
|
|
120
123
|
work: the CLI's `modifiedPrompt` and `modifiedResult` are documented and were
|
|
@@ -147,7 +150,13 @@ the only trace is a message.
|
|
|
147
150
|
notice that a redact fell back to warn, as a hook message. In the recorded
|
|
148
151
|
session VS Code accepted it and showed it only in the "GitHub Copilot Chat
|
|
149
152
|
Hooks" output channel, so the user never saw it, and a warn there is hard to
|
|
150
|
-
tell from `monitor`.
|
|
153
|
+
tell from `monitor`. VS Code's documentation lists that message field as shown
|
|
154
|
+
to the user only for its older local hook harness. For the Copilot harness,
|
|
155
|
+
which it describes as the default for new sessions from VS Code 1.143, it says
|
|
156
|
+
the field is not part of the documented contract. That is a reading of the
|
|
157
|
+
docs: no newer VS Code has been recorded. AKA sends no progress line there,
|
|
158
|
+
because VS Code documents none and an unrecognised line could cost a deny or a
|
|
159
|
+
rewrite. A redact on `run_in_terminal`'s `explanation` or `goal`
|
|
151
160
|
takes the same fallback as one on its command, because rewriting them would
|
|
152
161
|
need an allow that approves the command too. Set `redactFallback` to `block` if
|
|
153
162
|
a redact on a terminal call has to be visible; a VS Code deny itself was never
|
|
@@ -173,19 +182,34 @@ what it guarantees is that no path exits non-zero.
|
|
|
173
182
|
verdict that the tool executes, so printing one per clean call would suppress
|
|
174
183
|
the approval prompts your own Copilot settings would have raised. AKA emits a
|
|
175
184
|
verdict only to deny, rewrites arguments only through `modifiedArgs`, and
|
|
176
|
-
otherwise stays out of the way. A warning it has
|
|
177
|
-
the CLI documents no message field on this event.
|
|
178
|
-
|
|
179
|
-
|
|
180
|
-
|
|
181
|
-
|
|
182
|
-
|
|
183
|
-
|
|
184
|
-
|
|
185
|
-
|
|
186
|
-
log
|
|
187
|
-
|
|
188
|
-
|
|
185
|
+
otherwise stays out of the way. A warning it has goes out as a hook progress
|
|
186
|
+
line, because the CLI documents no message field on this event. The hooks
|
|
187
|
+
reference says the CLI removes progress lines before it reads the decision, so
|
|
188
|
+
a progress line on its own is still no verdict.
|
|
189
|
+
|
|
190
|
+
**On the CLI a warn is a progress line, and nobody has seen one on screen
|
|
191
|
+
yet.** The hooks reference describes stderr surfacing for a FAILING hook
|
|
192
|
+
("logged as a hook failure") and says nothing about one that exits 0.
|
|
193
|
+
Observed on Copilot CLI 1.0.98 in `-p` mode: a successful hook's stderr
|
|
194
|
+
appears nowhere in the CLI's own output, and only in the debug log
|
|
195
|
+
(`--log-level debug --log-dir <dir>`), as `[rust:hooks] [hook stderr] …`
|
|
196
|
+
lines. So AKA now also sends every notice as a hook progress line, which the
|
|
197
|
+
same reference documents as display-only status text in the CLI timeline.
|
|
198
|
+
Whether it shows in `-p` mode, in an
|
|
199
|
+
interactive session, or on the cloud coding agent has not been measured. Until
|
|
200
|
+
it has, treat a warn under `redactFallback: warn` (the shipped default) as
|
|
201
|
+
possibly invisible: the call goes through and the notice may reach only that
|
|
202
|
+
log, which makes a warn hard to tell from `monitor`. Set `redactFallback` to
|
|
203
|
+
`block` if a redact on command text has to be visible: a deny carries its
|
|
204
|
+
reason, and the CLI was recorded printing it.
|
|
205
|
+
|
|
206
|
+
**This needs Copilot CLI 1.0.55 or later.** The hooks reference dates the
|
|
207
|
+
progress line, and the CLI removing it before reading the decision, to that
|
|
208
|
+
release. AKA can write a progress line beside a decision, such as a rewritten
|
|
209
|
+
description or a deny. How an older CLI reads that has not been measured, and
|
|
210
|
+
if it reads the whole output as one object, it would ignore the decision. The
|
|
211
|
+
call would then go through unmasked or undenied. The builds recorded here are
|
|
212
|
+
1.0.83 and 1.0.98. Check yours with `copilot --version`.
|
|
189
213
|
|
|
190
214
|
**The cloud coding agent is captured only where the repository asks for it.**
|
|
191
215
|
It reads `.github/hooks/*.json` on the **default branch** and nowhere else, and
|
|
@@ -195,13 +219,13 @@ it has no local store of its own.
|
|
|
195
219
|
attached to the organization's control plane, the Claude Code and Codex plugins
|
|
196
220
|
print one line at session start: forwarding everything, forwarding for the
|
|
197
221
|
enrolled repository the session is in, or local-only. This adapter's
|
|
198
|
-
session-start hook has no message field on either surface
|
|
199
|
-
line
|
|
200
|
-
newer AKA binary is on the machine than
|
|
201
|
-
block and redact categories were kept at
|
|
202
|
-
|
|
203
|
-
|
|
204
|
-
|
|
222
|
+
session-start hook has no message field on either surface. On the CLI it sends
|
|
223
|
+
that line as a hook progress line, with a copy on **stderr**, together with its
|
|
224
|
+
other once-per-session notices: that a newer AKA binary is on the machine than
|
|
225
|
+
this plugin, that a warn-era store's block and redact categories were kept at
|
|
226
|
+
warn, and that the store path is redirected. It writes no hook output. The
|
|
227
|
+
progress line has not been seen on screen yet (see above). Under VS Code these
|
|
228
|
+
lines go to stderr only.
|
|
205
229
|
`aka status` shows whether this machine is attached, whether it sends
|
|
206
230
|
everything or only enrolled repositories, and which repositories are enrolled.
|
|
207
231
|
|
|
@@ -212,6 +236,7 @@ everything or only enrolled repositories, and which repositories are enrolled.
|
|
|
212
236
|
| cli | preToolUse | bash.command | block | yes | A deny on stdout with exit 0 blocks the call; masking command text would change what runs, so a redact policy follows redactFallback instead of rewriting. |
|
|
213
237
|
| cli | preToolUse | bash.description | rewrite | yes | Model-authored prose that rides along with the call, rewritten in place through modifiedArgs. Scanned for secrets and PII only: the command-risk rules judge bash.command, never this prose. |
|
|
214
238
|
| cli | preToolUse | apply_patch.input | rewrite | no | No payload for this tool was recorded, so the argument name is unverified; a wrong name costs a silent skip rather than a wrong answer. |
|
|
239
|
+
| cli | preToolUse | warn notice | warn | no | Sent as a hook progress line, which the hooks reference documents as display-only text in the CLI timeline and strips before reading the decision, so the call still goes to the host permission flow. Never observed on screen; the stderr copy reached only the debug log in a recorded 1.0.98 -p session. Every other AKA hook notice on every CLI event takes the same route; the degraded-scan line from the SDK is the exception and still goes to stderr only. |
|
|
215
240
|
| cli | sessionStart | session | none | yes | Opens the session root every later capture hangs off, and records the host, harness and project inventory. It decides nothing and emits nothing — there is no verdict to reach on a session start. |
|
|
216
241
|
| cli | userPromptSubmitted | prompt | none | yes | Captured and scanned; nothing can be stopped or rewritten. modifiedPrompt is documented and was not observed from a command hook, so a block or redact policy is recorded and the prompt is sent unchanged. |
|
|
217
242
|
| cli | postToolUse | toolResult | none | yes | Captured and scanned; nothing can be withheld. The tool has already run, and modifiedResult is documented but was not observed replacing what the model sees, so a finding is recorded and the output reaches the model unchanged. |
|