⚡ workdash

Text-based GitHub work triage dashboard. Pick what to work on next, then jump straight into a review, an AI analysis, or a full coding session in a dedicated worktree.

View on GitHub → Install
workdash TUI showing issues and pull requests pulled from GitHub, with one entry highlighted as the suggested next work item

Your GitHub work, with less friction

GitHub tells you what is waiting. Getting from there to an open editor with the right branch, the right context, and a summary of the thing you are about to touch is the part that eats the morning. workdash compresses that into a single keystroke.

It pulls your authored PRs, review requests, assignments, and tracked issues into one list, suggests what to pick up next, and lets you launch an AI analysis or a full coding session in a dedicated git worktree — each keyed to the GitHub item so context never gets lost between sessions.

One key, one action

oOpen in browser

Jump straight to the issue or pull request on GitHub.

rRefresh

Re-pull authored PRs, review requests, assignments, and tracked items.

aAnalyze

Run Claude or Codex against the item, render the result as HTML, and cache it — keyed by the GitHub updated_at so stale entries invalidate themselves.

cCode

Prepare a dedicated git worktree and launch Claude, Codex, or VSCode Copilot inside it, preloaded with the item's context.

tTerminal

Drop into a terminal in the item's worktree, no agent attached.

--printPrint mode

Same triage, emitted as plain text for scripts, pipes, and agents that want the dashboard without the TUI.

From inbox to code, in three keystrokes

workdash collapses the gap between knowing what to work on and actually working on it. Here is what that looks like for the three things you spend most of your GitHub day on. Click any screenshot to zoom in.

Review a pull request

Skip the "what is this PR even doing?" step and dive into a grounded review.

analyze dialog offering to open a cached analysis or run a fresh one with Claude or Codex against the selected pull request
rendered HTML analysis of a pull request opened in a browser

Workflow

  1. Spot the review requests. PRs waiting on your review are surfaced in the same list as everything else, so they do not get lost in a GitHub notifications tab.
  2. Pick an analysis — a. The analyze dialog offers the cached result or a fresh run with Claude or Codex.
  3. Read the briefing. The analysis is rendered as HTML summarising the change, the intent, and the risky parts. Cached until the PR is updated, so re-opening is free.
  4. Open it in context — o or c. Jump to GitHub to leave comments, or drop into a worktree with the PR checked out to actually run the code.

Tackle an issue

From a fresh bug report to an agent writing the fix — without leaving the terminal.

coding agent running inside the per-item git worktree, preloaded with the issue's context

Workflow

  1. See what's waiting. Authored PRs, review requests, assignments and tracked issues are merged into one list, sorted by last update, with a suggested next item highlighted.
  2. Get a read on it — a. Run Claude or Codex against the issue. The analysis is rendered as HTML and cached so you can revisit it instantly later.
  3. Start coding — c. A git worktree is prepared for the issue and your agent launches inside it, already primed with the cached analysis as context.

Keep up with feedback on your own PRs

Notice which of your open PRs actually need attention today, without scrolling through a GitHub notifications list.

workdash TUI showing authored pull requests alongside other work items, with recently-updated entries in bold and the suggested next item marked with an asterisk

Why it helps

  • Suggested next item. One entry is marked with a *, so you don't re-decide every time.
  • Recent activity in bold. Anything touched in the last 24 hours stands out — fresh review feedback is impossible to miss.
  • Sorted by last update. PRs with new activity float up; quiet ones drop down.
  • Authored, review-requested, assigned — one list. No switching between GitHub filters to see the whole picture.

Access everywhere

workdash runs where your development machine runs. Attach through zellij remote or plain ssh, then keep the same dashboard, worktrees, cached analyses, and agent launch commands available from a laptop, tablet, or phone.

workdash running in a zellij terminal session from a mobile device over a remote connection

Remote workflow

  • Resume the same terminal session. Use zellij remote to reconnect to the dashboard without recreating tabs, panes, or in-progress coding sessions.
  • Fallback to ordinary SSH. When all you have is a shell, start workdash over ssh and keep the full triage loop close at hand.
  • Keep state on the workstation. Worktrees, GitHub credentials, caches, and agent tooling stay on the machine that already has your development environment.

Install

With uv — one isolated install, workdash on your PATH: 

uv tool install workdash

Then generate the configuration interactively:

workdash --configure

Launch the TUI:

workdash

Requirements

Linux and macOS. Not tested on Windows.