#Browse

▍browse-tree120×32

browse-treeA tree with a Frecent branch listing three recently used groups and projects, Your groups expanded to show the platform group and its projects, and a collapsed Starred branch, beside a panel summarising the highlighted project.

#Branches

Frecent is the top branch. On a first launch, before anything is pinned, it is already a working list of what you open the tool for.

#What you can do

Key	Action	Key	Action
j k	move	Enter	scope the dashboard here
l →	expand a node	P	pin it as a tab
h ←	collapse a node	o	open in the browser
/	search the tree	Esc	back where you came from

In Browse, h and l fold and unfold tree nodes instead of switching section tabs, because Browse has no section tabs.

#Scoping and pinning

Enter scopes the dashboard to the highlighted node and takes you back to it. The scope is temporary: the next Enter replaces it, and nothing is written to disk.

P pins it as a tab, named from the node you were standing on, and that pin survives a restart.

Scope to platform/ingest, switch from merge requests to pipelines and back, and you stay where you were. The breadcrumb in the context bar names the current scope.

#Loading

• One level per keypress. Subgroups and projects are fetched when you open their parent, so a tree with two thousand projects costs one query to draw its root. currentUser.groups returns in 0.43 s.
• Cached to disk. A cold start paints the tree from cache and refreshes behind it, the same way the tables do.
• Search falls through. Typing filters the nodes already loaded, then asks GitLab for the ones that are not.

#More than one GitLab

Each GitLab in your settings is a root in the tree, so moving between instances is navigation. A view pinned under one root remembers which instance it came from. See multiple instances.