~/.copilot profile.
Runtime checks
Copilot CLI
/envshows the goal-system extension or plugin surface./skills info goalshows the goal skill.- Starting
/goal <real task>creates a persisted goal instead of only acknowledging the skill. goal_system_statusshows the same goal ID after a new prompt in the same session.- A subagent receives main-session-only boundary text and cannot use goal tools.
- After five non-goal tool calls without
goal_system_update, a sixth non-goal tool is denied. - Trying to stop with an open goal is blocked by the hook.
goal_system_closerefusescompletewhen required evidence is missing.goal_system_closeacceptscompleteonly after inspection, resolution, verification, coverage, no remaining work, no blockers, and completion audit are recorded.
VS Code Copilot Chat
MCP: List ServersshowsgoalSystem.MCP: Reset Cached Toolsrefreshes thegoal_system_*tools after install or update.- The
Goal Systemcustom agent appears in Copilot Chat. - The
GitHub Copilot Chat Hooksoutput channel shows goal hooks running. - Starting
/goal <real task>through theGoal Systemcustom agent creates a persisted goal with the injectedsessionIdandcwd. - Asking to continue a single same-directory active goal in a fresh VS Code Chat session loads that persisted goal instead of starting from memory.
Stopblocks while an open goal remains active.SubagentStartgives subagents the boundary text without full goal details.
Fixture prompt
Run this inside Copilot after install:Known limits
Local tests cannot prove a specific Copilot CLI or VS Code build invokes every documented hook. Verify/env, MCP server registration, hook output, and one real /goal session after installing.