Back to Signal Feed
CodeTracked since May 19, 2026

agentmemory adds first-class GitHub Copilot CLI MCP support

This update makes GitHub Copilot CLI a first-class supported agent by adding official MCP plugin wiring and a dedicated connect path in agentmemory, enabling Copilot users to onboard with the same integration model already used by other coding agents instead of custom, error-prone setup.

GitHub Copilot CLIMCPagentmemory connectplugin manifest

What Happened

  • This update makes GitHub Copilot CLI a first-class supported agent by adding official MCP plugin wiring and a dedicated connect path in agentmemory, enabling Copilot users to onboard with the same integration model already used by other coding agents instead of custom, error-prone setup.
  • This update makes GitHub Copilot CLI a first-class supported agent by adding official MCP plugin wiring and a dedicated connect path in agentmemory, enabling Copilot users to onboard with the same integration model already used by other coding agents instead of custom, error-prone setup.
  • 1 evidence item attached for review.

What is Different

Before

Scattered source updates, isolated context, and manual follow-up across multiple feeds.

Now

Implemented native Copilot CLI onboarding in agentmemory by introducing plugin assets (`plugin/plugin.json`, `.mcp.copilot.json`, hook event config), adding a command path (`agentmemory connect copilot-cli`) that merges into Copilot MCP config while preserving existing keys, and normalizing Copilot camelCase event fields so observations flow through existing hook adapters—this removes a major integration gap and lowers the barrier to using Copilot CLI in the same agentmemory workflows.

Why Track This

Why It Matters

Developers can now hook Copilot CLI into agentmemory with a supported setup path instead of ad-hoc config edits, so teams can capture Copilot tool events more consistently and reduce onboarding friction and config mistakes in local workflows. The change works by adding MCP-first plugin/install configuration plus idempotent CLI config merging and hook-field normalization, which should make Copilot integrations easier to operate across environments; watch for drift in Copilot event schemas, edge-case MCP-config merge conflicts when multiple servers are present, and Windows-specific command wrapping behavior that could reintroduce setup failures on some developer machines.

Impact

Developers can now hook Copilot CLI into agentmemory with a supported setup path instead of ad-hoc config edits, so teams can capture Copilot tool events more consistently and reduce onboarding friction and config mistakes in local workflows. The change works by adding MCP-first plugin/install configuration plus idempotent CLI config merging and hook-field normalization, which should make Copilot integrations easier to operate across environments; watch for drift in Copilot event schemas, edge-case MCP-config merge conflicts when multiple servers are present, and Windows-specific command wrapping behavior that could reintroduce setup failures on some developer machines.

What To Watch Next

  • Watch whether GitHub Copilot CLI becomes a repeated pattern.
  • Track follow-up changes around Agent Orchestration Platforms.
  • Compare future signals against this evidence trail.
  • Re-check risk flags: copilot_payload_schema_drift, mcp_config_merge_conflicts.
Open Topic TimelineOpen Technical EventOpen Original Sourcecopilot_payload_schema_drift / mcp_config_merge_conflicts / windows_copilot_command_compatibility / hook_field_normalization_regression

Supporting Evidence

GITHUB PULL REQUESTHigh Trust

rohitg00/agentmemory PR #534: Add GitHub Copilot CLI support

The PR adds a Copilot CLI plugin manifest plus an `agentmemory connect copilot-cli` flow and hook-payload normalization so Copilot tool events can be ingested by existing observation hooks with minimal manual setup.