Skip to content

Solution for long term memory for agent coding CLIs and to facilitate handoff between different agent vendors

Rust

Merge PR #1068: feat(hooks): add GitHub Copilot CLI as a hooked agent (#1040)

AkitaOnRailsdf4825c87466
diff --cc CHANGELOG.md
index c161c8d6,8fda8773..c417c845
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@@ -153,6 -154,6 +153,19 @@@ and this project adheres to [Semantic V
like other Claude Code-shaped agents. GrizzyBot posts to `/hook` and
`/mcp` itself, so there is nothing to install. Adds migration V72 to extend
the `sessions.agent_kind` CHECK constraint. (#1036)
++- Added GitHub Copilot CLI as a hooked agent: `install-hooks --agent
++ copilot-cli` writes `$COPILOT_HOME/hooks/ai-memory.json` (default
++ `~/.copilot/hooks/ai-memory.json`) with Copilot's flat, matcher-less entries
++ and PascalCase event names, so Copilot sends its VS Code/Claude-compatible
++ payload. Ten events — Claude Code's nine plus `PostToolUseFailure` — with
++ native commands enforcing capture exclusions; tool output is read from
++ `tool_result.text_result_for_llm` and the outcome from
++ `tool_result.result_type`. The `SessionStart` hook delivers the prior
++ session's handoff through Copilot's top-level `additionalContext` (ported
++ from #1069). There is deliberately no `--scope project`. The bare
++ `install-mcp --client copilot` alias keeps meaning VS Code Copilot;
++ `install-mcp --client copilot-cli` and `ai-memory run copilot` follow
++ separately. (#1040)
### Changed
- Documented FutureInfra as an endpoint for the existing `openai-compat`