Back to Signal Feed
CodeTracked since May 18, 2026

Fix Copilot CLI hook compatibility so PeonPing no longer drops key agent events

The PR replaces the Copilot integration path with a unified event-handling fix: Copilot hooks are written directly under `~/.copilot/hooks` when available, the Copilot adapters now use explicit per-event translation instead of implicit remaps, and incoming payloads are normalized from camelCase aliases to the expected snake_case fields so events like `permissionRequest` are detected instead of being silently ignored.

PeonPingGitHub Copilot CLI 1.0.48-1copilot hooksadapters/copilot.sh

What Happened

  • The PR replaces the Copilot integration path with a unified event-handling fix: Copilot hooks are written directly under `~/.copilot/hooks` when available, the Copilot adapters now use explicit per-event translation instead of implicit remaps, and incoming payloads are normalized from camelCase aliases to the expected snake_case fields so events like `permissionRequest` are detected instead of being silently ignored.
  • The PR replaces the Copilot integration path with a unified event-handling fix: Copilot hooks are written directly under `~/.copilot/hooks` when available, the Copilot adapters now use explicit per-event translation instead of implicit remaps, and incoming payloads are normalized from camelCase aliases to the expected snake_case fields so events like `permissionRequest` are detected instead of being silently ignored.
  • 1 evidence item attached for review.

What is Different

Before

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

Now

Implemented a compatibility and routing fix for Copilot CLI events: direct hook auto-wiring in install/uninstall scripts, explicit event mapping in adapters, and camelCase payload fallback (13 aliases) in both shell and PowerShell execution paths. This turns previously dropped events—especially `permissionRequest`—into detectable events for PeonPing.

Why Track This

Why It Matters

Copilot CLI users of PeonPing now receive audible cues for completion, permission prompts, and failure/notification signals again, reducing the chance of missing critical workflow prompts during agent sessions; this also makes behavior more predictable for operators who rely on these hooks for task oversight. The change works by replacing brittle event remaps with explicit translation and a compatibility shim for upstream payload drift, while preserving existing handled event coverage. Watch for whether future Copilot CLI payload schema changes introduce new field-name variants beyond the 13 aliases and whether any unhandled event names appear in real traffic.

Impact

Copilot CLI users of PeonPing now receive audible cues for completion, permission prompts, and failure/notification signals again, reducing the chance of missing critical workflow prompts during agent sessions; this also makes behavior more predictable for operators who rely on these hooks for task oversight. The change works by replacing brittle event remaps with explicit translation and a compatibility shim for upstream payload drift, while preserving existing handled event coverage. Watch for whether future Copilot CLI payload schema changes introduce new field-name variants beyond the 13 aliases and whether any unhandled event names appear in real traffic.

What To Watch Next

  • Watch whether PeonPing becomes a repeated pattern.
  • Track follow-up changes around Tool Calling.
  • Compare future signals against this evidence trail.
  • Re-check risk flags: copilot_cli_upstream_payload_drift, uncovered_new_hook_events.
Open Topic TimelineOpen Technical EventOpen Original Sourcecopilot_cli_upstream_payload_drift / uncovered_new_hook_events / auto_wiring_skip_path_regression

Supporting Evidence