You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Custom agents lost web fetch, search, questions, the browser, and the session tools in VS Code agent-host (Copilot SDK) sessions, because the runtime drops every VS Code tool name it cannot resolve (github/copilot-cli#4594). Every agent now declares the runtime name next to each VS Code name, and the agents that are not contained get a common web, search, question, and session-tool baseline. Contained agents gain only grep, glob, and ask_user for tools they already had.
The Copilot CLI variant of software-engineer mapped web and search to the web and search aliases, which enable no tool. It now emits web_fetch, grep, and glob.
Block-RemoteMutation now allows the tool call with a warning when the hook payload is not valid JSON, as its message always said. It exited 1, which the Copilot SDK host treats as a denial, so a payload schema change would have blocked every tool call.
Hook launchers failed on Windows when HOME was unset, which blocked every tool call in Copilot SDK sessions and dropped the SessionStart context.
Preserve unambiguous trigger replies with mixed capitalization or no space after the colon; keep multiline or contradictory replies invalid. Classify query errors structurally and repair the schema-checked sample query IDs.
Bound evaluation definitions, samples, and replies to 1 MiB per file by default (-MaxInputBytes can opt into larger inputs), and provide stable timeout diagnostics. See grading contracts.
Harden the bundled evaluation gates against false success: validate case definitions and path-safe IDs, match contains literally, require complete numbered samples, bound regex matching, reject malformed trigger replies, and return failing exit codes without dropping incomplete queries from split totals. See grading contracts.
Restore the published v5.0.0 release history and align the static plugin manifest with that release, so post-release builds and plugin update discovery use the recorded version.
Set the plugin manifest to the released version in the automated changelog pull request, so a release rollover no longer fails its own manifest version check (CI run 36549550887). Pushes to main that change only CHANGELOG.md or plugin.json are validated without republishing the Customization module.