#Features

Every merge request in the current scope, in one table, with approvals, pipeline status, diff size, and the reason it cannot merge.

Every merge request waiting on your review, across the whole instance, from a single query.

GitLab's 24 merge-status values in plain words, in the row. Conflicts, a red pipeline, and a missing approval read differently.

Train position in the row, and a merge prompt that says the merge request will queue.

CI as a view of its own, with the same scope, the same table, and the same keys as merge requests.

Every pipeline in a nested group tree from one query. 945 pipelines across 50 projects return in about four seconds.

The jobs that failed, and the last meaningful lines of each, without opening a log.

Full traces, with live follow, search, folding, and one key from a failed pipeline to the error.

Watch a pipeline until it reaches a terminal state, then take a desktop notification when it lands.

The screen labdash opens on: the reviews waiting on you, your own merge requests, and your failing pipelines.

Your GitLab group tree in the terminal, with GitLab's own ranking of the groups and projects you use at the top.

/ narrows the rows already loaded. f opens a typed filter bar that completes from your instance.

One key turns the scope and filter you are looking at into a tab that is still there tomorrow.

GitLab's to-do list as a working queue, with mark done, mark all done, and a count on the view switcher.

Check out a merge request's branch in your own clone or in a worktree, and open the project in your editor.

Your work GitLab and gitlab.com in one dashboard, each with its own TLS, proxy, and failure isolation.

Concurrent fetches, stale-while-refreshing, a warm disk cache, and an offline mode, with the measured timings behind each.

Issues as another queue you browse, filter, and pin, in the same table with the same keys.

What is deployed where across a group, with review-app URLs one key away.