Build a dev dashboard

Most developers have the same small set of questions every morning: what's waiting on me, what should I work on next, and how long until lunch. The dev dashboard is butter set up to answer those questions in a single glance. Ten minutes end-to-end; ten seconds a day after.

The build

Five widgets (six with Pro), arranged so the most actionable items sit where your eye lands first. The full layout:

Or drop an AI Inbox across the top instead — it triages both feeds into a ranked list, so you can keep GitHub and Linear small or even collapse them. Free gets one triage a day; Pro removes the cap.

Step by step

1. Start fresh. If you've already got widgets in the way, press E and X each one out — five seconds, no undo, but you can export first if you'd like a safety net.
2. Add GitHub. Press A , pick GitHub. Click Connect — the auth-worker handles the OAuth handshake. Leave the filter on Review requested; that's the question this widget is for.
3. Stretch GitHub to 8 wide. Drag the right edge until it snaps to eight columns. The PR titles read on one line and you can fit ten or so PRs before scrolling.
4. Add Pomodoro. Drop it to the right of GitHub. The default 4×4 size fits cleanly in the remaining four columns. Open its settings if you want a longer focus phase or a different alarm.
5. Add Linear. Place it underneath GitHub at 8 wide. Connect via OAuth, leave the filter on Assigned to me.
6. Add Quick Links. Drop it under Pomodoro at 4 wide. Replace the starter links with the dashboards / docs you open all day — your team's Sentry, your build server, your design system, whatever.
7. Press Esc . Edit mode off. You're done.

Tuning the filters

The defaults are fine for most people, but a few tweaks are worth knowing:

• GitHub: repo allow-list. If a single team's monorepo drowns your review queue, open the GitHub widget's settings and paste the repos you actually care about (one owner/name per line). Leave empty for any.
• GitHub: drafts. Most days you can leave Include drafts on — drafts show with a small chip and you can scan past them. Turn off if your team uses drafts as "definitely not ready yet."
• Linear: priority floor. Set Priority to Urgent + High on busy days. Switch back to Any priority for triage Fridays.
• Linear: team scope. If you live across two teams but only really act on one, type that team's prefix (e.g. ENG) into the Teams field. Comma-separate for multiple.

The AI path: AI Inbox up top

The AI Inbox is also a strong thing to put at the top of this layout. It takes the same data the GitHub and Linear widgets show, plus the small bit of metadata each provides (state, priority, age, draft flag) and ranks the lot in one list — with a one-line why next to every entry.

Free gets one daily triage; Pro removes the cap. Either way, a clean layout: AI Inbox at 12 wide across the top (a single eye-level strip), GitHub and Linear shrunk to 6 wide each underneath, Pomodoro and Quick Links smaller below.

A few habits that pair well

• One Pomodoro per task. Click into a Linear issue, start a focus phase, ship the work, take the short break. The widget's mid-screen position is a tiny nudge to do this.
• Refresh sparingly. The GitHub and Linear widgets cache for five minutes. If something feels stale, hit the refresh icon — but don't hammer it. New PRs aren't going anywhere.
• Sync your dev links. Quick Links sits in the synced layout, so once you set this up on one Chrome, your build server bookmark follows to others.