# Navigating DevKeepr

DevKeepr knows your projects, their stacks, and their scripts. Everything comes together in one place, and you can reach it from anywhere: the app, the menu bar, or your terminal.

## The Overview

When you open DevKeepr, the Overview is the first thing you see. Your projects are sorted by recent activity or size, with indicators for CI status and deployments. Alongside the project list you get a summary of disk space reclaimed through hibernation, Claude session stats (with Pro), and your global packages across all managers.

![The DevKeepr Overview panel](/screenshots/homepage-light.webp)

## Everything Starts With Stack Detection

The actions available for a project come from [Stack Detection](/docs/general/features/stack-detection). When DevKeepr detects that a project uses Laravel and Node, it automatically surfaces Artisan commands, Composer scripts, npm scripts, Make targets, GitHub workflow dispatches, and anything else the matched detectors contribute.

You don't configure any of this. Detection happens automatically, and the available actions reflect whatever was found.

## The Quick Action Menu

The quick action menu is a searchable list of everything DevKeepr knows about the current project: general actions like opening your editor or terminal, stack-specific scripts, log tailing, hibernation controls, and more.

When no project is selected the menu switches to global context with navigation, package manager updates, and a list of all your projects to jump to.

## Reach It From Anywhere

The same actions are available through every surface DevKeepr offers. Each one adapts to its environment, but the core is always the same.

### In The App

Press `Cmd+K` to open the command palette. It's searchable, context-aware, and shows the current project's actions first.

![Command palette showing project actions and stack scripts](/screenshots/docs/command-palette.webp)

### Menu Bar

Right-click the tray icon to open the context menu. Bookmarked projects appear as submenus with their full set of actions. Navigation items have `Option` key hotkeys for quick access.

<p style="text-align: center;">
  <img src="/screenshots/docs/menubar.webp" alt="Menu bar with bookmarked project submenu and Composer scripts expanded" style="max-width: 600px; width: 100%; margin: 1.5rem auto 0; border-radius: 12px;">
</p>

### Project Detail

The project detail screen surfaces all actions directly. Stack actions, log files, processes, and general actions are all accessible without opening the command palette.

![Project detail screen showing stack actions and log files](/screenshots/docs/project-detail.webp)

### CLI

Your terminal gets the same access through the `dk` command. See the [CLI Tool](/docs/general/features/cli-tool) page for more.

![The dk CLI action menu in the terminal](/screenshots/docs/dk-cli.webp)

## What Ties It Together

Actions fall into a few categories. The exact list depends on the project's detected stacks.

- **General actions** are available for every project: open in editor, terminal, Finder, open the Git remote, hibernate, wake, rescan.
- **Stack actions** come from detected stacks. npm scripts, Composer scripts, Artisan commands, Make targets, Docker compose, GitHub workflow dispatch, and more.
- **Logs** are detected per stack. Select one to tail it in real time.
- **Processes** that you run appear in the [Process Tray](/docs/general/features/process-tray) at the bottom of the screen, alongside CI workflow runs and deployments.

The idea is simple: DevKeepr figures out what's relevant, and makes it available everywhere you work.