This article explains how to use the GitHub Copilot app's 'My work' pane to streamline task management. By centralizing issues and PRs and linking them directly to AI agent sessions, engineers can reduce context switching and improve productivity when handling complex development workflows.
This is the third post in our GitHub Copilot app for Beginners series. If you’re just joining us, check out, GitHub Copilot app for beginners: Getting started, where we introduced the app and how it helps you work across multiple agent sessions. Our second post goes deeper on working within a session. Here, we’ll look at how to keep all of the requests and work being done on a project organized in one place.
If you’ve been following along in this series, you know that real development is rarely a straight line. You fix a bug here, review a pull request there, and chase down a new idea somewhere in between. As you continue to assign tasks to Copilot and create new pull requests, you’ll quickly find yourself with several proverbial balls in the air.
Being able to manage everything from one centralized location is key, and that’s exactly why the My work pane exists. Below, we’ll cover how you can use it to manage what’s currently in flight, what’s completed, and what’s next.
When you open the My work tab, you’ll see three tabs waiting for you. The first is All, which shows all of your pull requests and issues in one place.
This list is automatically filtered based on the projects you’ve touched inside the Copilot app. It’s not every repo you have access to. If there’s a repo you’d like to see here, just create a quick session pointing to that repo, and it’ll show up.
Alongside All, you’ll find three more built-in views:
These give you an at-a-glance sense of what needs your attention right now versus what’s already wrapped up.
The built-in views are a great start, but you can also create your own. Select New view, and you’ll get the familiar “New view” placeholder name, which you can rename to something like “My issues.”
From here, you can build your filter. You can type it out using the angle-bracket syntax you might recognize from GitHub, or use the UI, which is often the friendlier option when you’re getting started.
For your My issues view, you can add a filter for Is: Issue to grab all issues, then add one more filter for Assignee: Me. Select Save, and now this view shows every issue that’s been assigned to you.
You can also do some quick filtering. Select the filter at the top and you’ll get the same interface. Maybe instead of sorting by Recently updated, you’d rather flip it to Ascending so the oldest items float to the top. From there, save your changes to a brand-new view, update the view you’re currently on, or discard the changes to revert back.
By default, your items show up in a list view, which feels a bit like a set of cards. It’s a clean, approachable way to scan through your work.
If you’d like a little more control, switch to the table view. The table unlocks a few extra features you won’t find in the list: choose which columns to display, move them around, and resize them to fit how you like to work.
And don’t worry about experimenting: you can always reset everything back to the way it was before, and switch right back to the list view whenever you’d like.
Here’s where things really come together. You can bring up any item by selecting it, and from there, start a brand-new session on it. Just tell Copilot, “Hey, let’s get to work on this,” it’ll get to work, using the issue as its context.
Back in the list view, you can select multiple items at once, choose Actions, and create new sessions from them. This is useful in a couple of ways:
In either case, you can change the repo that the Copilot app uses for its session, which is perfect for those situations where the repo hosting the issue is separate from the one hosting the code.
Near the top of the pane, you’ll find two more helpful buttons.
The first is your repository filter, which is set to All Repositories by default. Remember, even “all” here is automatically scoped to the repos you’ve touched inside the Copilot app.
The second is New issue, which lets you create an issue right on the spot. For example, if you want to add a light mode toggle, select Create and you can kick off a brand-new session that starts with that issue as its context.
The My work pane gives you a single, centralized place to manage all of your pull requests and issues. You can create custom views, search to find exactly what you need, and quickly assign tasks to Copilot, so you can stay organized and focus your attention where it’s needed most.
Learn more by exploring the rest of the videos in this series, or by visiting gh.io/app. We’ll see you in the next post!
The post GitHub Copilot app for Beginners: Managing your work appeared first on The GitHub Blog.
Continue reading on the original blog to support the author
Read full articleParallel agent sessions boost productivity by automating multiple tasks simultaneously. Using Git worktrees for isolation, engineers can handle features, reviews, and tests in parallel without manual context switching or environment conflicts.
As AI shifts from chat interfaces to autonomous agents, developers must master new architectural patterns like loop engineering and harnesses. Understanding these terms helps teams build reliable AI-native systems while managing costs and performance.
This article highlights the shift in open-source maintenance caused by AI. It explores how to manage high-volume, AI-generated contributions while maintaining security and community trust, offering a blueprint for future projects in the age of automated development.
As AI agents handle complex tasks, chat interfaces become bottlenecks. Canvases provide the state management and visibility needed for multi-step engineering workflows, reducing cognitive load and ensuring human-in-the-loop governance for critical code changes.
