GitHub's redesigned dashboard with agent sessions becomes the default for all users

GitHub has made its redesigned dashboard the default view for every user, promoting it out of feature preview status. According to a changelog entry published on October 1, 2026, the redesign reorganizes the service's landing page around work that needs attention — including Copilot agent sessions — and moves the activity feed into a tab of its own. The change drew attention after reaching Hacker News's front page.

A work list, not a feed

The redesigned dashboard consolidates three kinds of items into a single view: active agent sessions, issues, and pull requests. Each section supports filters so users control what appears there, with a ceiling of 12 items per list. GitHub's stated aim is to help people concentrate on important work and figure out what to handle next.

The activity feed that used to dominate the page now lives in its own Feed tab, keeping repository updates separate from the task-focused dashboard. In practice, this splits the dashboard's old double role: it is no longer trying to serve as an inbox and a social stream at the same time.

Agent sessions become a first-class work item

The most consequential detail is what sits in those lists. Agent sessions now appear alongside issues and pull requests, meaning automated, Copilot-driven work is treated with the same standing as tasks a human owns.

The dashboard also serves as a launch point. GitHub says work can begin on the dashboard itself — handing an issue to the Copilot coding agent, or opening a pull request in Copilot Chat — without first navigating into a repository. For teams already using agentic workflows, the dashboard effectively doubles as a control surface for delegated work; for everyone else, the agent section simply stays thin.

An escape hatch remains

Users who prefer the previous layout are not stuck with the redesign. A dropdown next to "Preview" restores the old experience whenever needed, and GitHub is collecting reactions in a community discussion linked from the changelog post.

Why it matters

Defaults shape behaviour. A feature preview only changes the experience for people who opt in; a default changes what every user sees the moment they sign in. GitHub is using that position to redefine what counts as work in progress on its platform.

Placing agent sessions at the top of the dashboard — beside the issues and pull requests developers have tracked for years — is a deliberate signal about where GitHub expects software development to go. The same applies to dashboard shortcuts that hand work straight to Copilot: they tie GitHub's hosting product more closely to its AI products, and they make agentic coding a routine option rather than an experiment tucked into a settings page.

The presence of a switch-back option suggests GitHub anticipates some friction, and whether that option survives future updates is worth watching. But the direction is clear: the front page of github.com is being recast as a queue of things to act on, and a growing share of those things may be running themselves.