How do I use Ward with GitHub Copilot?
Updated
Run ward integrate copilot in your project. Ward writes .github/hooks/ward.json and .github/hooks/ward.sh and checks the code GitHub Copilot CLI writes.
What does the integration install?
| Copilot event | What happens |
|---|---|
PreToolUse (bash, edit, create) |
With the guard enabled, denies protected changes |
PostToolUse (edit, create) |
Runs the quality check. Findings go back as additionalContext |
Stop |
Runs the quality check and spec validation. Findings continue the turn once |
Ward supports GitHub Copilot CLI. The docs do not cover the Copilot features of editors.
Keep ward on your PATH.
What does the agent see when a check fails?
Copilot treats exit 2 after a tool as a warning, so Ward returns findings as additionalContext, which the model reads. When the turn ends, findings continue it once.
How do I install and remove it?
ward integrate copilot
ward integrate copilot --removeGenerated files carry a Ward ownership marker. Ward refreshes only its own files and reports any file you wrote as a conflict.
Is it tested?
The generated files pass tests against Copilot CLI 1.0.98’s documented contract. A live run is not recorded yet. Ward is in alpha, so the CLI and the configuration may change before 1.0.
Where do I go next?
Ready to try it? Install Ward and run ward init in your project.