#Pinned views

▍pinned-tabs120×32

pinned-tabsA tab bar showing Home followed by four pinned views named Needs my review, platform failing, Release, and Mine, each with its row count.

#The three keys

A view is built by browsing, filtering, and pinning rather than by editing a file.

#What a pin remembers

• The scope, meaning the group or project you were standing in, subgroups included.
• The filter, as typed values rather than a string.
• The sort order, and how often the view refreshes.
• Which GitLab instance it came from, once you have more than one.

#Managing pins

Key	Action	Key	Action
P	pin the current view	h l	move between tabs
P	on a pinned tab, unpin it, with undo	r	refresh this one

Unpinning always offers an undo, because one key is easy to press twice.

Each view carries its own refresh interval. A "failed today" tab polls every thirty seconds while a "merged this quarter" tab checks hourly. See refresh and caching.

#The state file

labdash writes your pins to a state file beside your settings. The application owns that file:

• labdash writes it, you do not. It has no documented schema.
• It is written atomically. A crash during a write cannot cost you your pins.
• It migrates silently. A new version reads a file written by an older one.
• A corrupt file resets with a note. It never becomes a startup error.

Delete it and you lose your pins. Nothing else changes.