Understand the LowLighter system.

The three product boundaries

LowLighter divides the user experience across the desktop application, the operating system, and the online account service. Each boundary owns the work that users see in its controls.

Desktop application

Owns the workspaces, settings, shortcuts, screen-selection surface, answer surface, Agent, Meetings, Phantom controls, and local preferences.

Operating system

Owns the permission decisions for screen capture, input, microphone, system audio, and Accessibility access.

Online service

Owns account authentication, plan access, usage state, online AI processing, support, billing, and update information.

How a screen request moves through the product

1. 1

   Choose a mode

   The desktop reads the mode and engine settings available to the current account.

2. 2

   Capture context

   The operating system provides the screen area selected by the user, or the desktop reuses the saved Automatic Screen Capture region.

3. 3

   Process the request

   LowLighter uses the selected online engine or the local Fast path when Offline Mode is active.

4. 4

   Show the response

   The desktop renders the result in the configured answer surface and keeps it separate from the application where the request began.

How specialized features fit the same model

Agent adds automated browser, document, file, code, and desktop tasks with the permission level you choose. Meetings adds live audio, transcription, screen context, references, and history. Phantom adds a protected presentation and related hotkey and system controls. Offline AI adds an optional local processing path after its components are installed.

Account state remains the source for plan and usage access across each feature. The desktop shows that state in the relevant workspace and settings card.