How Atmos Handles Context Menus and Menu Bar Actions

Atmos is a menu-bar-first app, so a lot of its behavior starts before you ever open the main window. The menu bar icon is not just a launcher. It is also a control surface, a context menu trigger, and a shortcut into different parts of the app depending on your license state.

This guide explains how that system works.

Atmos is designed as a menu-bar-only app

On launch, Atmos hides itself from the Dock and App Switcher and runs as an accessory-style macOS app. That means the menu bar icon becomes the main entry point for interacting with the app.

This is one of the reasons Atmos feels lightweight. It is not structured around a persistent Dock presence. It is structured around a small status item that can reveal the main panel or open quick controls when needed.

Left-click and right-click do different jobs

The Atmos status item explicitly listens for both left mouse up and right mouse up events.

That split matters:

• left-click is mainly used to show or hide the main Atmos window
• right-click opens a context menu directly from the menu bar icon

This means the menu bar icon supports both a panel workflow and a quick-command workflow without forcing users into a single interaction style.

Left-click toggles the main window

When the main window is already visible, a left-click on the status item hides it. Before hiding, Atmos captures the current window frame so it can restore that exact position later.

When the window is hidden, a left-click brings it back. In that specific menu bar path, Atmos centers the window on screen rather than restoring the last manual frame.

That gives the icon a clear “bring the panel to me” behavior when summoned directly from the menu bar.

Right-click opens different menus depending on license state

Atmos does not use one universal context menu. It chooses between different menu families based on the current license state.

In practice, there are three broad menu types:

• full app menu for active and grace states
• license menu for activation and renewal states
• support-only menu for locked or restricted states

This is an important hidden behavior because it means the menu bar experience changes depending on what the user is currently allowed to do.

The full app menu exposes quick controls

When the license state allows the app to run normally, the menu bar context menu includes a set of app controls such as:

• enable or disable Atmos
• reload the app
• toggle loop
• toggle Smart Loop
• change playback speed
• jump into Library
• jump into Settings
• quit the app

This is effectively a compact command center for the most important runtime controls.

Speed uses a submenu with state-aware selection

Playback speed is handled as a submenu, not a flat list of duplicate commands. Atmos builds a speed menu with preset values and marks the currently active rate.

That is a small but useful detail because it turns the menu into both:

• a control surface
• and a status indicator

The same is true for toggles like Loop and Smart Loop, which show their current on or off state directly in the menu.

Reload App is a real recovery action

The Reload App command is more than a superficial refresh. When triggered, Atmos re-applies the active wallpaper if needed, reloads the cursor skin engine, reloads the widget overlay if widgets are enabled, and then shows the main window again.

That makes the menu action useful as a lightweight recovery tool when desktop-facing systems need to be rebuilt.

This is exactly the kind of hidden functionality that is easy to miss if you only think of the menu bar icon as a launcher.

License states swap in different menu behavior

If Atmos is not activated or a subscription has ended, the menu changes to a license-oriented version with actions like:

• paste license key
• subscribe or renew
• contact support
• quit

If the app is in a more restricted state like revoked, device limit reached, network required, or locked, the menu simplifies even further to support and quit actions.

That keeps the available commands aligned with what the app can actually do in that state.

The window itself can also show a context menu in some states

There is another hidden branch here. The main Atmos window can intercept right-click events and open a context menu directly from inside the panel, but only for certain license-related states.

That behavior is gated intentionally. In active or grace states, the app keeps normal right-click behavior inside the panel. In license-blocked states, it routes right-click into the context-menu system so the user can still reach relevant actions like support or subscription flow.

This is a good example of Atmos adapting the UI around state rather than pretending every screen should behave the same way all the time.

Some menu actions also navigate the main window

Not every context-menu action stays in the menu layer. Some actions first show the Atmos window and then route the user to a specific destination like Library or Settings.

That means the context menu is tightly integrated with the main panel rather than being a totally separate interface.

The menu can either:

• perform an immediate action
• or open the window and drop the user into the right screen

That is part of why the menu bar workflow feels cohesive.

Hidden behaviors worth knowing

There are several subtle details in this system that are easy to overlook:

• the status item explicitly distinguishes left-click from right-click
• left-click from the menu bar centers the panel when showing it
• hiding the panel stores the exact current frame first
• context-menu contents change based on license state
• some blocked license states keep support actions available through the menu
• Reload App rebuilds wallpaper, cursor, widgets, and window visibility together

These details make the menu bar icon much more than a simple show or hide button.

What this means in practice

If you use Atmos heavily from the menu bar, you are already relying on this system. The icon acts as a launcher, a quick settings surface, a recovery point, and a state-aware access path into the app.

That is one of the reasons Atmos can stay compact without feeling limited. A lot of the app's control logic is concentrated into the menu bar, and the context-menu system makes that entry point much more powerful than it first appears.