What GitHub changed
GitHub's changelog entry for November 10, 2026, filed as an Improvement, says many users tried the new dashboard and shared feedback after it launched. The complaints it names are generous padding, wrapped titles, and a low default item count. Together these forced extra navigation just to see what needed attention. The "Agent sessions" section also stayed on screen for people who had no agent sessions.
The update makes four changes:
- Less padding. Spacing is reduced across the pull request, issue, and agent session lists, so more fits on screen.
- Single-line titles. Long titles no longer wrap. GitHub says the full text is still available when you need it.
- Six items by default. Pull requests and issues now show six items instead of three. GitHub says any custom selections you already made are preserved.
- Agent sessions hidden when empty. The section disappears if no agent sessions exist on your account.
GitHub's roadmap tracking issue for this follow-up work gives the same figures. It describes showing six pull requests and issues by default instead of three, reducing visual clutter, and improving session filtering. The roadmap item also mentions improved filtering for agent sessions. The changelog post itself doesn't list that, so treat it as a roadmap goal rather than a confirmed part of this release.
How this fits the October rollout
GitHub's October 1 changelog said the redesigned dashboard, previously a feature preview, was becoming the default experience for everyone. That version put active agent sessions, issues, and pull requests in one place, with filters per section and up to 12 items per list. The Feed moved to its own tab. Users could start work from the dashboard, for example by assigning an issue to Copilot coding agent. People who preferred the old layout could switch back through the dropdown next to "Preview."
The November update changes presentation and defaults. It doesn't change that 12-item ceiling, the Feed tab, or the dashboard actions, and the changelog doesn't say it does.
Reaction to the October switch was mixed. One commenter in GitHub's community thread complained that the new dashboard removed information they found useful and mostly shows pull requests and issues. A density fix doesn't answer that complaint. It only makes the pull request and issue lists less cramped.
Practical impact
For most users, nothing needs to be done. GitHub gives no configuration steps and presents the community discussion as an invitation for feedback, not a requirement.
- Heavy PR and issue users: six rows instead of three means less clicking to see what is waiting. If you already set your own list size, GitHub says that choice stays.
- People who never use coding agents: the empty Agent sessions block should no longer take up space.
- Teams using Copilot coding agent: the section should still appear once your account has agent sessions.
These benefits follow from the layout changes themselves. GitHub hasn't published any measurement of time saved.
What GitHub hasn't said
- It gives no rollout schedule and doesn't say whether every account has the update yet.
- It gives no pixel measurements and doesn't describe how the full title is revealed.
- It doesn't say whether "no agent sessions exist" counts only active sessions or also completed ones.
- It doesn't say how custom selections are stored, or tie the hidden section to licensing or entitlements.
If your dashboard still looks like the old layout, the changelog gives no explanation. A browser refresh is a reasonable first check, but that is general advice, not GitHub guidance.
Why it matters
GitHub is pushing the dashboard toward being a work queue that includes agent output. That makes density a real usability question, because you want to see what needs review without scrolling. Hiding an empty module is a sensible default. Doubling the default list length is a modest adjustment, and it suggests GitHub is tuning the layout based on user feedback.
Is six the right number? It's better than three, and still well short of 12. Users who want more can raise the count themselves, since existing custom selections are kept.