Canvases shift AI interaction from text-only chat to a shared, stateful UI. This allows engineers to build custom, bidirectional tools like triage boards or release checklists instantly using natural language, significantly improving collaborative efficiency between humans and AI agents.
Most tools give you a fixed set of screens and ask you to fit your work into them. But what if you could start with the workflow you want instead and have the interface take shape around it?
That’s the idea behind canvases in the GitHub Copilot app. A canvas, also called a canvas extension, is a customizable interface that you and the agent share. It can be a kanban board, an issue triage board, a release checklist, a dashboard, a form, or even a spreadsheet: a UI shaped to how you work.
Because the canvas is bidirectional, the agent can update it as it works, and you can use buttons, cards, filters, and other controls to make changes too. Just like using a live shared whiteboard.
Let’s create one.
To create a canvas, you don’t have to do any coding or design by hand. Just open an agent session, enter the /create-canvas skill, and describe what you want in plain English.
Make sure your prompt covers three things:
For example, you could enter:
/create-canvas Create a release notes canvas for tracking new feature work completed across GitHub Copilot app sessions. Include controls for reviewing and organizing entries and allow the agent to add and update them.
Then, the agent will build the interface and open it in the right-side panel without you having to write files or mess with the layout. One description becomes a custom tool that’s ready to use.
Because the interface is generated from your description, your first version is just a starting point, and you can keep refining until you’re happy.
You could ask the agent to add a column or filter, pull in your open pull requests, or turn the entire canvas into a checklist for your day. The agent will revise the canvas to match. While there isn’t a fixed menu of layouts, if you can describe a workflow, you can likely turn it into a canvas.
Once created, your canvas is saved as an extension, so you can use it again. You can keep it with the project for your team to share or save it as a personal extension just for you.
The real power of a canvas is that you and the agent can both keep working at the same time.
When you click a button, update a field, or move a card, the canvas’ shared state changes immediately. The agent sees the same update without a separate send or sync step.
It works the other way, too. You can ask the agent to use the canvas’ own capabilities—the same actions available to you—to add a release note or move a card, then watch that change appear in the interface. Instead of sending a command and waiting for a response, you’re steering the work together.
Creating a useful canvas starts with three simple questions:
Not sure where to begin? The community has shared ready-made canvas extensions through Awesome Copilot, including release notes tools, kanban boards, issue triage workflows, and more. Install one that’s close to what you need, then ask the agent to customize it for your workflow in the same way you would refine a canvas you created yourself.
Start small: open a session, run /create-canvas, and describe a simple board or checklist for something you’re working on now.
The post GitHub Copilot app for Beginners: How to build custom workflows with canvases appeared first on The GitHub Blog.
Continue reading on the original blog to support the author
Read full articleExperienced engineers demonstrate that AI tools are most effective when integrated with established practices like TDD and custom personas. This shift toward "agentic engineering" allows developers to focus on high-level design and architectural integrity while maintaining code quality.
This workflow bridges the gap between AI-driven code generation and manual engineering, allowing developers to leverage AI for bulk tasks while maintaining full control over local testing, debugging, and final code quality within their primary IDE.
This shift to agentic workflows and ambient intelligence redefines the developer experience. It moves the focus from syntax and manual tasks to high-level intent and judgment, requiring engineers to master context management and AI steering to maintain productivity and code quality.
Providing AI with codebase context reduces repetitive prompting and ensures generated code follows team standards. By using custom instructions and MCP servers, engineers can automate complex workflows and integrate external tools directly into their AI-assisted development cycle.