GitHub's new dashboard experience now the default
GitHub has made its redesigned dashboard the default view for all users, replacing the previous feature preview. The new interface consolidates active agent sessions, issues, and pull requests to streamline workflow management. Users retain the option to revert to the old experience if they prefer the previous layout.
- ▪The new dashboard experience is now the default view for all GitHub users.
- ▪The interface allows users to view active agent sessions, issues, and pull requests in a single location.
- ▪Users can start work directly from the dashboard, such as assigning issues to the Copilot coding agent.
- ▪A separate Feed tab keeps updates distinct from the productivity-focused dashboard sections.
- ▪Users can switch back to the previous experience at any time via a dropdown menu.
Hacker News (Front Page) files mainly under programming. We currently carry 2,429 of its stories. Top-voted stories on Hacker News.
Story provenance
Source · retrieval · rights · ranking — open for full record
inspect →
Story provenance
Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.
Record
| Original publisher | The GitHub Blog |
| Canonical URL | https://github.blog/changelog/2026-10-01-new-dashboard-experience-now-the-default/ |
| Publication time | Sat, 03 Oct 2026 09:59:01 +0000 |
| Retrieval time | 2026-10-03T10:58:12.934Z |
| Last seen | 2026-10-03T10:58:12.934Z |
| Headline source | Publisher (no WeSearch rewrite) |
| Excerpt source | publisher body |
| Excerpt method | First ~120 words (~800 chars) of extracted publisher body, fair-use limited. |
| Summary | WeSearch · cerebras-chat (WeSearch summarizer) |
| Summary source text | contentText |
| Citation coverage | Summary is a WeSearch-generated derivative; primary citation is the original publisher URL. |
| Cluster | lEvqgWZXCubI · 1 stories |
| Cluster logic | Grouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison. |
| Ranking reason | Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking. |
| Publisher visit | Yes — open original |
| Substitutes article? | No — link-out required for full text |
Rights status (four layers)
WeSearch handling by dimension
| Indexing | May the item be indexed (stored, ranked, made findable)? | Allowed |
| Snippet | May a short excerpt of the publisher's text be shown? | Allowed |
| AI summary | May WeSearch generate its own short summary of the article? | Limited |
| Retrieval / RAG | May the content be exposed for third-party retrieval-augmented generation? | Not asserted |
| Model training | May the content be used to train AI models? | Not asserted |
| Commercial reuse | May the content be reused commercially? | Not permitted |
Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.
Opening excerpt (first ~120 words) tap to expand
Back to changelog Improvement October 1, 2026 • 1 minute read New dashboard experience now the default The new dashboard experience, previously available as a feature preview, is now the default view for everyone. The redesigned dashboard helps you focus on the work that matters most and makes it easier to find and act on what you need next. You can: View your active agent sessions, issues, and pull requests in one place. Use filters to choose what appears in each section, with up to 12 items in each list. Catch up on updates in the separate Feed tab, keeping your feed distinct from your productivity-focused dashboard. Start work directly from the dashboard, such as assigning an issue to Copilot coding agent or opening a pull request in Copilot Chat.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at The GitHub Blog.
Discussion
0 commentsMore from The GitHub Blog
