Agent activity in GitHub Issues and Projects

We shipped two new features that bring agent activity directly into your planning workflows.

Agent sessions under assignees in GitHub Issues

When a coding agent (e.g., Copilot, Claude, or Codex) is assigned to an issue, its session now appears directly under the assignee in the sidebar. Each session shows a live status: "queued", "working", "waiting for review", or "completed". Click any session to jump straight into the session logs.

agents_issues.mp4

This is now generally available for all repositories with access to coding agents.

Agent sessions in project table and board views

Agent sessions now surface directly in project table and board views. You can see at a glance which items have attached agent sessions, their current status, and how work is progressing across a large body of work.

projects_agents.mp4

To try this out, open the View menu and turn on Show agent sessions.

[sunzhuoshi]

After assigning an issue to Copilot agent, the issue link text disappeared from PR description, which broke auto-close linked issue after the PR was merged.

there's no such issue yesterday.

[TylerDixon]

👋 Hey there, thank you for the report! This has now been remedied for future PRs created by agents, but you will have to manually reference PRs created in the last 12 hours to the issues they should close. Apologies for the inconvenience.

[sunzhuoshi]

thank you for your quick response, the issues are gone now.

[abalchev-qb]

I observed another issue that was not present before. We do have an automation that assigns Copilot to issues so it immediately starts working on them. But now with the same automation that creates the issue, Copilot faces an error and cannot start working on it.

The payload is per the docs

"assigneeIds": [""],
"agentAssignment": {
  "targetRepositoryId": "",
  "customAgent": "",
  "customInstructions": "",
  "baseRef": "",
  "model": ""
}

What we observed is that via the UI the agent gets nested below a user assignee. Whereas when we do the issue creation with the API, the Copilot stays in the same hierarchy and produces the error which is non-debuggable (or at least as a user without admin access to the repos I cannot see).

Is there a change in the API that we need to use now so that new flow works properly?

[TylerDixon]

Thank you for the report! This should be working as expected now, but please let us know if it is not. Any details you could provide about your automation would also be helpful.

[abalchev-qb]

Nope, it's even worse now - even through the UI when I assign Copilot as a normal assignee and after I fill the dialog that pops up it immediately fails with:

The agent encountered an error and was unable to start working on this issue: Please try again later, or contact support if the problem persists.

[abalchev-qb]

OK, I guess it was either a bug that was fixed or intermittent service issues, but it seems to be working now both via the API and via the UI. :)

[teerawad020841]

We shipped two new features that bring agent activity directly into your planning workflows.

Agent sessions under assignees in GitHub Issues

When a coding agent (e.g., Copilot, Claude, or Codex) is assigned to an issue, its session now appears directly under the assignee in the sidebar. Each session shows a live status: "queued", "working", "waiting for review", or "completed". Click any session to jump straight into the session logs.

agents_issues.mp4

This is now generally available for all repositories with access to coding agents.

Agent sessions in project table and board views

Agent sessions now surface directly in project table and board views. You can see at a glance which items have attached agent sessions, their current status, and how work is progressing across a large body of work.

projects_agents.mp4

To try this out, open the View menu and turn on Show agent sessions.

[teerawad020841]