Introducing the Agents tab in your repository 🗳️

[ebndev]

We've redesigned where you manage Copilot coding agent tasks. We're bringing a new look and feel to your mission control style view directly into your repository with a new Agents tab.

Instead of navigating to a separate page, your agent sessions now live alongside your code, pull requests, and issues. View all sessions for the repository in one place, create new ones, and switch between tasks without leaving your codebase. One-click links make it easy to jump straight to the associated pull request. You can also archive sessions to keep things organized and page through your session history.

Redesigned session logs

Session logs are now easier to read and follow. Similar tool calls are grouped together, reducing noise and making the flow more clear. Tool outputs render inline previews, and file changes appear with the familiar diff views that you can expand with one click. Every tool call has a distinctive icon, and bash commands are now visible for full transparency.

Resume with the Copilot CLI

If you prefer working in your terminal, you can now continue your Copilot session directly in the Copilot CLI. Click Continue in Copilot CLI, copy the command, and pick up right where you left off.

To get started

1. Navigate to a repository.
2. Click on the new Agents tab.
3. Create a task.
4. To open your session in the CLI, click Continue in Copilot CLI.
5. Copy the command and paste into your terminal to get started with the Copilot CLI.

Note: To view the Agents tab, ensure that you have Copilot coding agent enabled for your repository.

🌟Leave a comment!

Join the discussion and leave feedback in the comments below!

[3kh0]

How do I disable this tab?

[elliebennett]

Hi @3kh0 - The Agents tab appears when Copilot coding agent is enabled for your repository. If it is not enabled, it will not appear.

[3kh0]

I see. I am not sure how it got enabled, but I would think that having a checkbox (under the main settings page -> features, like Wiki and Issues) would be a bit easier to access.

[mkushakov]

Even if Copilot is enabled for repository, not all users are having Copilot licenses. It should be a toggle in repository settings similar to Issues, Wikis and Discussions to turn it on or off
https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/disabling-issues

[elliebennett]

@mkushakov Thanks for the feedback on how to make the settings more apparent for you and users like you. The Agents tab also has conditional logic based on if the individual user has a Copilot license.

[lalishansh]

I wasn't able to find it in repository setting so i disabled it GitHub User settings > Sidebar > Copilot > Coding Agent > No repository

[Plasma]

Thanks for the update, I was hoping to start seeing something about defining recurring agent tasks.

For example, to replace Dependabot, "Keep these packages up to date", or "Do this code scan looking for X issues and raise a Security alert or open a PR", run daily/weekly, etc.

[elliebennett]

Thanks @Plasma. We have something in the work on this. If you're interested in providing early feedback, let me know if you would be open to a feedback session to provide your input.

[schneidergithub]

This is possible through workflows already, essentially a cronjob.

[katorly]

For anyone who finds this annoying, disable it account-wide in https://github.com/settings/copilot/coding_agent, or organization-wide in https://github.com/organizations/<your_org_name>/settings/copilot/coding_agent.

[jannes-io]

The only reason anyone is reading this announcement is for this ^

[SteffenBlake]

Im surprised theres only 3 comments on this

I wanna thank yall for the fact this rollout also seems to correspond with fixing a very annoying bug that has been frustrating me for the past few weeks, agents not getting their agent files loaded in subsequent calls

That bug seems to be fixed now and the improvement to how much "smarter" agents feel as a result is palpable, thanks!

I quite like the new UI, though yall did drop the feature of being able to click a specific LOC during the changes to auto copy it into the chat as FileName#nn:nn to quickly point out a line of code while steering the agent

Not a mission critical feature, but definitely one I noticed was missing right away as I use it quite a lot, heres hoping it makes its way back in though, as I loved that one!

[elliebennett]

Thanks for the feedback @SteffenBlake . We're iterating on the best way to enable you to do this. I'll circle back with you when we have an update! Please continue to share feedback, it helps us improve the experience.

[Inscure]

A feature to disable code collapsing so that all code is visible at once would be useful. Currently, I have to keep clicking "Show all X lines", which is a significant inconvenience.

[elliebennett]

Noted! Thank you @Inscure

[angelo-loria]

Putting this new tab directly in the middle of the most heavily used tabs is diabolical

[garyburgmann]

Right next to Actions is the work of the devil himself (we don't have discussions enabled).

All my tiny brain sees is A***s and I must have accidentally clicked it at least 972 times already.

[angelo-loria]

All my tiny brain sees is A***s and I must have accidentally clicked it at least 972 times already.

Same, it's driving me crazy

[eregon]

Right next to Actions is the work of the devil himself (we don't have discussions enabled).

All my tiny brain sees is A***s and I must have accidentally clicked it at least 972 times already.

Yep, same thing for me, this is probably the worst UI change in a while.

I ended up disabling it for my user and my orgs because it's annoying every time I want to see Actions runs.
I might even have tried the new feature, but it gets so much in the way of Actions that I prefer to disable it entirely for now.

This should be opt-in, or put in a more sensible place like at the end or on the side or something.

[dbeattie71]

Configure Environment uses the path repo/.github/workflow/copilot-setup-steps.yml is that correct? Docs say to use repo/github/copilot-setup-steps.yml

[elliebennett]

Hi @dbeattie71 can you point me to the docs you are referencing?

[Inscure]

Thanks for building great software for developers. I’d like to share some feedback regarding the recent changes.

I was disappointed to see that the previously available view of modified files — similar to the Changes tab on pull request pages — was removed from the agent session page. With the new agent session page, viewing the summary of code changes prepared by the agent now requires opening the pull request in a separate web browser tab, which feels less convenient. While these changes may have a rationale internally, they were unexpected for me and have had a negative impact on my workflow.

I also noticed that the agent session window appears to use only about 70% of the available horizontal space, leaving unused space on both the left and right sides. This space could potentially be used to widen the session view or to reintroduce a file change preview, as was available before.

One additional usability issue I’d like to mention concerns text input on tablets. Pressing Enter currently submits the prompt to the agent instead of inserting a new line. This differs from the behavior on platforms like the ChatGPT website, where Enter creates a new line and submission is handled separately. As a result, I’ve accidentally submitted incomplete prompts multiple times and had to consume additional premium requests unnecessarily. Adjusting this behavior would help prevent accidental submissions and make writing longer or more structured prompts on tablets much more comfortable.

[elliebennett]

Thanks @Inscure for your feedback here. We are still iterating on how best to bring the Files Changed tab next to your sessions. Would you be interested in providing early feedback on the direction?

[Inscure]

Thanks @Inscure for your feedback here. We are still iterating on how best to bring the Files Changed tab next to your sessions. Would you be interested in providing early feedback on the direction?

Hi there! I'd definitely be interested in sharing my thoughts on this. Could you let me know what the feedback process looks like? Is it a survey, a user interview, or a beta test? Feel free to contact me.

[elliebennett]

Hi @Inscure - this would a feedback call "user interview". Can I go ahead and reach out to you over the email address in your GitHub bio to schedule?

[BenFCSains]

How do we remove the tab ? Or at the very least move it to the end

[elliebennett]

The Agents tab appears when Copilot coding agent is enabled for your repository. If it is not enabled, it will not appear.

[ejorgensen22]

Was there a reason for its current position? The new tab showing up to the left of the Actions tab is annoying to say the least.

[BenFCSains]

Thank you, I'll look at why that is showing

[younsl]

To disable Copilot coding agent and remove the Agents tab from repositories:

1. Go to GitHub Copilot Coding agent settings, or navigate to Settings > Copilot > Coding agent.
2. In the Policies section, click the Repository access dropdown.
3. Select No repositories.
4. Click Save to apply the changes.

[davepermen]

2026 continuing the 'shove ai into every corner of every ui no matter if users want it there', I see. Glad I left github. Threads like these prove how ignorant this platform has become.

[ClariNerd617]

As usual, Microslop doesn't understand the concept of consent.

[mikebollandajw]

Hey microsoft we really appreciate the pyschological approach to shoving a button where one of the most popular buttons Actions used to be

It really endears us to you when we (every single github user in the world) have to remap our muscle memory because some genius thinks this is how you sell a product

[ipeterov]

I'm annoyed at the button, but I have a slightly different take. I actually use AI to write 95% of my lines of code, and I do it in pair programming mode - I have long dialogs with it where it reads my repo files, we discuss plans, it reads more based off that, and so on. Then I monitor all the edits and constantly steer it whenever I notice suboptimal decisions from it. The feedback loop takes seconds - I see a mistake, I press Esc, tell it to not go there, and it continues.

That's why trying to put AI coding into PRs feels like a hopeless dead end - it lengthens the feedback loop from seconds to potentially hours, and suggests I review the entire changeset instead of steering as it writes code. Every mistake and weird approach can't get corrected in the middle and results in the rest of the code being wasted.

The only thing where PR-based agents can be useful is full tilt vibe coding - you don't even review what it does, there is no feedback loop to lengthen. It has its uses for prototyping, but prototypes often don't even get repos to begin with. Having this tab so prominent promotes vibe coding in places where it's not appropriate. Please let me hide it where I can hide the rest of the tabs (General > Features).

You guys don't need to add AI somewhere just to stay relevant - no matter who writes the code, apps will use version control, and GitHub will stay as the primary provider of git services. Focus on Copilot CLI (which is not a dead end) and maybe making GitHub more stable (another big downtime today) ❤️

[SteffenBlake]

You can still steer PR based agents though? The session in the agent tab can be steered by chatting with it.

PRs are nice necause you can comment the code lines itself with a review, then hit request changes to bulk send all your feedback on precise lines of code back to the agent.

[gabelepoudre]

When I select this tab, it gets stuck in a forever loop of trying to fetch or initialize something. I tried to leave feedback:

It has been this way for a few days at least. I imagine some combination of my organization, repo, and personal account details have it in a broken state. Cannot submit, nothing loads.

EDIT: to be clear, I noticed this tab a few days ago, and it has never worked. This is not a recent development

It may be a good idea to add a link to this discussion when trying to use the tab. I can't imagine I'm the only one to be in this state, but kind of hard for you guys to find out when the feedback doesn't work.