A shared interface for agent work
GitHub’s guide, published on 25 September, explains canvases in the GitHub Copilot app. A canvas is an interface shared by a developer and an agent. GitHub lists boards, issue lists, release checklists, dashboards, forms and spreadsheets as examples.
According to GitHub, both participants can change the canvas. A developer can move a card or update a field, while an agent can perform actions supported by that canvas. GitHub says these changes appear in shared state without a separate message or manual sync step.
Describe the workflow and its controls
The guide starts with an agent session and the /create-canvas skill. Your description should cover three things: the workflow, the controls you want to use, and the actions you want the agent to perform. GitHub says the agent then builds the interface in the side panel without requiring you to design the layout or write files by hand.
You can ask for changes after the first version appears. GitHub gives examples such as adding a column or filter, bringing open pull requests into the view, or changing a board into a checklist.
Save a canvas or start with a shared example
GitHub says a created canvas is saved as an extension for reuse. You can keep it with a project to share with a team or save it as a personal extension.
The guide also points to community extensions in Awesome Copilot, including release-note tools, boards and issue workflows. Its suggested starting point is a small board or checklist that you refine through further instructions.
Our assessment
For a first trial, choose a task you can easily check, such as organising an internal issue list. Decide which fields you will change and which actions the agent may take. If both can update the same card, test what happens when their changes overlap.
The guide does not report measured reliability or explain repository access rules for every extension. Check the app and extension permissions before connecting a canvas to release work. We have not tested these canvases. Treat a convenient shared interface as one part of the workflow, and verify the actions behind its controls.
Source: GitHub original publication.
Read the original material
GitHub (opens in a new tab)The article date belongs to Agentic Horizon. The source publication date is listed separately. Vendor claims remain attributed; we have not independently tested the reported capability.
