Overview
Copilot agent profiles are Markdown files stored in.github/agents/.
Copilot currently supports project installation scope only. MCP servers,
hooks, skills, and agent profiles are managed through the project
configuration.
Supported capabilities
Setup
1. Install the Observal CLI
2. Authenticate
~/.observal/config.json.
3. Pull an agent into Copilot
Config paths
Copilot MCP configuration uses the
servers key.
Hook spec
Event map
Session parsing and delivery
Copilot uses the built-incopilot-cli server parser while retaining separate source adapters for VS Code Copilot and Copilot CLI. VS Code hook events are durably materialized as JSONL-compatible source records; Copilot CLI discovers its native events.jsonl sessions.
Both adapters route through the shared spool-first delivery engine. Hook execution writes to the durable outbox and defers network work, retries keep stable source indexes, and cursors advance only after contiguous server acknowledgement. Recovery uses the authenticated server checkpoint. Finalization audits the complete source hash and rewinds/replays a mismatched range.
Caveats
Only project scope is supported. Agents are installed into.github/agents/.
Configuration is split across project directories. MCP servers are stored
in .vscode/mcp.json, while hooks and skills live under .github/.
Rules are not supported. Copilot supports agent profiles, MCP servers,
skills, and hooks, but does not expose a rules configuration.
