LeeSnap User Guide: Capture, Translation, Clipboard, and Mouse Automation

LeeSnap is not just a lightweight screenshot utility. In its current structure, it is a menu bar workflow tool that combines screenshot capture, text translation, AI-assisted processing, clipboard history, reminder handling, privacy controls, and external mouse actions. The product structure is also clear in the settings architecture: System, Capture, Translation and AI, Status Bar and Reminders, Clipboard, Privacy, and Mouse Enhancement.

That matters because the right way to adopt LeeSnap is not to install it and press one shortcut. The real payoff comes from configuring permissions, shortcuts, AI providers, clipboard retention, and mouse actions once, then letting the app sit in the menu bar as part of your daily workflow.

1. Understand how LeeSnap is organized

LeeSnap runs primarily as a menu bar application rather than a traditional dock-first app. In the current implementation, the three main daily entry points are:

Feature	Default shortcut	Purpose
Capture	⌘ + Shift + A	Starts the screenshot and annotation flow
Selection translate	⌥ + Shift + T	Triggers text translation
Clipboard history	⌥ + Shift + V	Opens the clipboard enhancement panel

The menu bar also exposes direct actions for capture, selection translate, clipboard history, quick reminder settings, preferences, about, and quit. If you prefer learning the product through visible UI before memorizing shortcuts, start there.

2. First launch and setup

The most reliable onboarding path looks like this:

1. Move LeeSnap.app into /Applications.
2. Use macOS’ first-run security flow to open it.
3. Go straight to Preferences and open the System tab.

In the current implementation, the System tab manages two permissions that directly affect whether the app works:

• Screen recording permission: required for screenshots.
• Accessibility permission: required for auto-paste and cross-app injection.

The same page also exposes:

• Launch at login
• Screenshot magnifier toggle
• Current permission state and shortcuts into macOS system settings

If you want LeeSnap to become a real daily tool instead of a half-configured utility, this is the first page to finish.

3. How to use the capture workflow

The Capture tab represents LeeSnap’s core workflow. It controls not only the screenshot trigger, but also default annotation behavior, wheel sensitivity, and the relationship between capture output and the clipboard system.

Starting a capture

You can start capture in three ways:

• Press ⌘ + Shift + A
• Click the Capture item in the menu bar
• Bind an external mouse action to Capture in the Mouse Enhancement section

Internally, these routes converge through the same coordinator, which means the actual capture flow stays consistent no matter how you trigger it.

Selecting and annotating

Based on the current code structure, LeeSnap supports more than a simple rectangle overlay. The available annotation toolkit includes at least:

• Arrow
• Rectangle
• Ellipse
• Line
• Brush
• Mosaic
• Text

The Capture settings let you define defaults in advance:

• Default tool
• Default color
• Default line width
• Whether arrows should default to double-ended
• Wheel sensitivity for annotation adjustments

That is a strong usability detail. If you repeatedly mark up screenshots in the same style, you can make LeeSnap open in that exact state instead of reconfiguring it every time.

Saving and reviewing captures

In the current settings layout, automatic screenshot storage has been merged into the Clipboard tab rather than managed as a separate capture-only destination. In practice, that means:

• Capture output and clipboard history can share one storage strategy.
• Cleanup rules can be applied in one place.
• Screenshots fit naturally into later reuse, browsing, pasting, and categorization.

This makes more sense for heavy daily use than treating screenshots as disposable one-off files.

4. How translation and AI are meant to work

The Translation and AI section is not just a prompt box. It groups selection translation, AI provider settings, and weather-related status bar data into one operational area, which signals that the app is designed for repeated text workflows rather than isolated chat calls.

Selection translate

The default shortcut is ⌥ + Shift + T. If you work in browsers, documents, or multilingual chat windows all day, this is the shortcut worth turning into muscle memory.

The settings currently let you define:

• The translation shortcut
• A default target language

If you do not want to decide direction every time, keeping the default as auto-detect is a sensible choice.

AI provider setup

LeeSnap currently supports provider-specific configuration for:

• DeepSeek
• OpenAI
• Claude
• Zhipu GLM
• Doubao
• Custom endpoints

Each provider can store its own:

• API key
• Base URL
• Model name

The current implementation also validates several basic failure cases:

• Very short API keys are rejected
• Base URLs must use HTTPS
• Model names can only contain letters, numbers, dots, underscores, and hyphens

So if saving fails, the first thing to inspect is the configuration value itself, not the UI.

What the AI flow does today

From the current AIService logic, LeeSnap does not simply upload an image and ask the remote model to do everything. It prioritizes local OCR first and then sends text to the configured model. That has two practical consequences:

• Token usage is lower
• Extract, translate, and chat modes can reuse OCR results

From a user perspective, the modes map cleanly:

• Extract for OCR-style text capture
• Translate for quick language conversion
• Chat for follow-up questions about the recognized content

If most of your work starts from screenshots that contain text, this structure is both efficient and easier to reason about.

Weather and date configuration

The same settings page also includes weather configuration, which connects back into the status bar system. You can define:

• Region
• QWeather API key
• API host

This is not random feature creep. It feeds directly into status bar display and reminder usage.

5. Clipboard enhancement is the second major module

The clipboard system is not a side feature in LeeSnap. Judging by the code structure, it is close to a standalone product: its own coordinator, panel window, history store, privacy policy, link preview logic, pinboards, previews, and cleanup rules.

Practical capabilities you can use now

The Clipboard tab currently exposes configuration for:

• The clipboard history shortcut
• Whether monitoring is enabled
• Whether paste targets the active app or only the clipboard
• Plain-text paste preference
• History size limits
• Separate retention periods by content type
• Auto-cleanup
• Consecutive deduplication
• Pinboard and display behaviors
• Unified storage directory

The default shortcut is ⌥ + Shift + V. The panel itself is designed as a bottom card strip and supports workflows such as:

• Searching history
• Switching board filters
• Previewing text, image, and other cards
• Creating and managing pinboards
• Editing saved content

This makes it especially useful for operators, support staff, writers, and anyone constantly moving reusable fragments between apps.

Why storage and cleanup matter

LeeSnap currently separates retention rules for text, images, video, and files. That gives you a practical way to keep the system useful without letting it grow into clutter:

• Keep text longer
• Expire images faster
• Use stricter windows for large files and videos

If you rely on LeeSnap heavily, this is one of the most important settings groups to tune early.

6. Do not skip the privacy tab

The Privacy tab determines whether the clipboard system remains safe in real work environments. The current controls include:

• Whether the clipboard panel can appear during screen sharing
• Screen sharing detection mode
• Manual “currently sharing” override
• Link preview generation
• Sensitive-content filtering mode
• Ignoring transient clipboard content
• Ignored applications

These switches are practical rather than theoretical. They help you:

• Avoid exposing clipboard content during meetings
• Reduce the chance of storing passwords, tokens, and similar secrets
• Exclude specific apps from clipboard history entirely

If your work touches production systems, credentials, support back offices, or frequent video calls, this page deserves real attention.

7. Status bar and reminders can become a lightweight command center

LeeSnap’s menu bar presence is not just a launcher. In its current form, the status bar can also carry:

• Time display templates
• Time zone selection
• Weather data
• Independent reminders and alarms

The Status Bar and Reminders tab lets you manage:

• Display template
• Time zone
• New alarms
• Active, paused, firing, and completed reminder states

There is also a Quick Reminder Settings action in the menu bar, which is useful when you want to create or review reminders without digging through the full settings layout.

8. Mouse enhancement is for heavier users

The Mouse Enhancement tab is the most advanced part of LeeSnap. It does not merely record one mouse click. It handles devices, permissions, action listening, profile selection, and app-specific overrides.

What you need first

The current UI makes one prerequisite explicit: full mouse enhancement depends on two permissions being available together:

• Listen permission
• Inject permission

If one of them is missing, the feature will not behave as a fully reliable trigger layer.

What it can do

Based on the current implementation, you can:

• Enable or disable mouse enhancement
• Inspect connected external USB or Bluetooth mice
• Start action listening to see the most recently observed action
• Build profile-based bindings
• Add app-specific overrides
• Map an action to one of these targets:
  • A custom shortcut
  • Trigger capture
  • Trigger translation
  • Open clipboard history
  • Disable the default action

If you are already used to using middle-click or side buttons as workflow triggers, this feature can remove a surprising amount of keyboard overhead.

9. A sensible setup order for new users

If you want the shortest path to a stable daily setup, use this order:

1. Confirm screen recording and accessibility permissions in System.
2. Set your default annotation tool, color, and width in Capture.
3. Add AI credentials and model configuration in Translation and AI.
4. Tune history limits, paste target, and retention windows in Clipboard.
5. Configure screen sharing and sensitive-content behavior in Privacy.
6. Set up time display and reminders in Status Bar and Reminders.
7. Configure Mouse Enhancement only if you actively use external mouse bindings.

This sequence gets the fundamentals working first and keeps advanced features from becoming noise.

10. Common troubleshooting paths

Screenshots do not start

Check screen recording permission in the System tab first.

Copy works, but auto-paste does not

Check accessibility permission. In the current logic, missing accessibility access causes the workflow to fall back from auto-paste to clipboard-only behavior.

AI settings fail to save

Check three things first:

• The API key is not obviously too short
• The Base URL uses HTTPS
• The model name contains only allowed characters

You do not want the clipboard panel to appear during meetings

Configure the screen sharing behavior and manual override in Privacy.

Mouse bindings were recorded but do not trigger anything

Check listen permission, inject permission, whether the device is recognized as an external mouse, and whether the binding target was accidentally set to disable the default action.

11. Final take

Looking at the current code structure, LeeSnap is no longer “a screenshot app with an AI button.” It is better understood as a menu bar workstation for capture, translation, AI-assisted text workflows, clipboard history, privacy-sensitive handling, reminders, and mouse-triggered actions.

If you only take occasional screenshots, LeeSnap can still work for you. But if your day involves constant copying, recurring screenshots, text translation, and fast context switching between apps, the real value shows up only after you configure the full stack once and let it stay in place.