Review what durable agents propose, inside the GitHub Copilot app.
Canvas puts an agent's proposed document changes in front of a reviewer. People decide what becomes accepted, Git keeps the document history, and Sessions records how the agent did the work. Document acceptance, action approval and continuation are separate steps, each tied to the work being reviewed.
For developers building human-review workflows, Canvas starts with a Copilot review UI and grows toward shared documents, several agents and multiple reviewers. The goal is a real approver and a replayable decision record.
Pre-1.0: today's local demo uses fictional drafts, real Git/Sessions records and simulated actions. Access: one trusted operator on loopback; signed-in approval and shared access are still being built.
Canvas owns document review. Sessions records durable execution; AgentSuite identifies portable agents; kmx authors, evaluates, packages and deploys them.
See the architecture diagrams for today's local boundaries and the planned hosted assembly.
From a normal checkout with Git and Go 1.27+ (toolchain 1.27.2 downloads enabled):
go run ./cmd/copilot-reviewOpen the printed loopback URL for the browser fallback, or follow the Copilot extension guide to open Northwind Engine Review in a repository session (Node 26 required for its backend). The demo supplies fixed responses using the Northwind definition, so you can try it without a model download, provider key, container or cloud. Use normal checkout modes; the fixture checks its suite inventory.
Create a writer draft, inspect both documents and accept or reject the complete proposal. Then separately request action approval, record a decision and explicitly continue the simulation. Check replay in the evidence controls. The selected demo role is an attribution label; approval authority requires verified identity, separately from Copilot sign-in.
Ctrl-C stops the engine. Private state remains in .state/copilot-northwind;
keep it on your own machine.
See model-backed prerequisites, or use the smaller prerequisite list for the deterministic review demo above.
For model-backed startup with make dev, see local model setup
and the Northwind walkthrough. It selects
Northwind with embedded Sessions and separate .state/northwind state. The
review demo above supplies fixed responses instead. make run and the flagless
Canvas command use the same Northwind default with an already configured model.
Follow the Northwind review steps and worked example.
The football backend and example have been removed. Existing legacy workspaces are not migrated, reset or reactivated; selecting them explicitly is refused. Historical session formats and archived contracts remain readable as described in runtime compatibility. Keep old state private and backed up; see state and backup guidance.
Use the hosted-model configuration guide for endpoint selection, private key files, metadata checks and charge warnings.
Use the metadata-only endpoint checks before starting a model-backed run.
See separate state paths and backups.
Read backup and upgrade precautions before opening existing state with a newer runtime.
See development and verification for test/build requirements, deterministic browser checks and model-qualification limits.
- Docs index: choose the deterministic, model-backed, authoring or recovery path.
- Roadmap: authenticated AKS review, shared work, and later frontend choices.
- Copilot review guide: setup, workflow and trust limits.
- Definition authoring: draft files and validate before activation.
- Generic Canvas: documents, scopes, recovery and exact-snapshot approval.
- Model-backed walkthrough: run the Northwind definition with a model instead of fixed responses.
- Released-suite fixture: agent identity and unsigned evaluation consistency.
- Runtime compatibility: backups and migration limits.
A Copilot authoring plugin and Claude Artifacts front end are planned, not started, after the first public release. Both will use the same engine.
This project welcomes contributions and suggestions. Most contributions require you to agree to a Contributor License Agreement (CLA) declaring that you have the right to, and actually do, grant us the rights to use your contribution. For details, visit Contributor License Agreements.
When you submit a pull request, a CLA bot will automatically determine whether you need to provide a CLA and decorate the PR appropriately (e.g., status check, comment). Simply follow the instructions provided by the bot. You will only need to do this once across all repos using our CLA.
This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact opencode@microsoft.com with any additional questions or comments.
This project may contain trademarks or logos for projects, products, or services. Authorized use of Microsoft trademarks or logos is subject to and must follow Microsoft's Trademark & Brand Guidelines. Use of Microsoft trademarks or logos in modified versions of this project must not cause confusion or imply Microsoft sponsorship. Any use of third-party trademarks or logos are subject to those third-party's policies.