Target runtime or language
Github Copilot CLI
What this proves
I tested Copilot CLI’s hook API locally. Its session and tool hooks appear sufficient for an ACS adapter:
| ACS |
Copilot CLI |
| Session lifecycle |
sessionStart, sessionEnd |
| Tool request |
preToolUse |
| Tool result |
postToolUse, postToolUseFailure |
| Tool decision |
permissionDecision |
| Session ID |
sessionId |
| Workspace |
cwd |
The adapter would mainly need to translate tool names and payloads, Guardian decisions, tool results, and audit events.
A few details still need to be handled carefully, especially tool-name mapping (bash vs. Bash), non-zero shell exits, hook timeouts, and multiple-hook behavior.
Do you intend to implement this yourself
Yes, I want this assigned to me
Current Priority Scope
This is deferred or out of scope and I am filing it to be tracked
Target runtime or language
Github Copilot CLI
What this proves
I tested Copilot CLI’s hook API locally. Its session and tool hooks appear sufficient for an ACS adapter:
sessionStart,sessionEndpreToolUsepostToolUse,postToolUseFailurepermissionDecisionsessionIdcwdThe adapter would mainly need to translate tool names and payloads, Guardian decisions, tool results, and audit events.
A few details still need to be handled carefully, especially tool-name mapping (bash vs. Bash), non-zero shell exits, hook timeouts, and multiple-hook behavior.
Do you intend to implement this yourself
Yes, I want this assigned to me
Current Priority Scope
This is deferred or out of scope and I am filing it to be tracked