Power User Guide: Themes, Layouts, and Advanced Wilee Configuration

July 23, 2026

Wilee works out of the box. Install it, hold the right mouse button, flick toward an action, release. Most people never change a single setting, and that's fine — the defaults are chosen to work well for the majority of use cases.

But if you're the kind of person who remaps keybindings in every application, customizes your IDE theme on day one, and has strong opinions about tab width, this guide is for you. Wilee's settings page exposes everything: menu layout, theme colors, gesture sensitivity, trigger buttons, action bindings per context, opacity, animation style, display mode, and more. Here's how to use all of it.

Choosing a Layout

The layout determines how many actions your menu holds and how they're arranged spatially. Wilee ships with six layouts:

To change your layout: open Wilee's settings, go to the Gesture section, and click the layout you want under "Look." The preview on the left updates immediately so you can see how your current action bindings map onto the new layout.

A practical tip: if you switch from a higher-capacity layout (like Radial 8) to a lower-capacity one (like Radial 4), some actions won't fit. Wilee keeps the first N actions from your current binding order and drops the rest. You may want to re-order your bindings after switching to make sure your most-used actions occupy the available slots.

Theme Customization

Wilee includes seven built-in themes, an auto-match mode, and a fully custom color editor.

The built-in themes:

Auto-match mode is a toggle at the top of the Theme section. When enabled, Wilee detects whether the page you're on has a light or dark background and automatically selects the Minimal or Minimal Dark theme to blend in. This is the set-and-forget option — the menu adapts without any manual switching.

Custom theme lets you pick exact colors for six properties: wedge background, wedge hover, stroke, text, text hover, and center. Click "Custom" in the theme row, and a color picker grid appears. Each property gets its own color input. Changes reflect in the preview immediately, so you can dial in exactly the look you want.

Opacity and Shape

Two more visual controls that work across all themes:

Opacity controls the overall transparency of the menu, from 30% (barely visible) to 100% (fully opaque). The slider is in the Gesture section under "Look." Lower opacity lets page content show through the menu, which some users prefer — it feels less intrusive. The Ghost and Transparent themes already have low-opacity wedges, so reducing global opacity on top of those can make the menu nearly invisible. Wilee warns you if the combination might be hard to see.

Shape has two options: Classic (flat pie slices with sharp edges) and Plate (chamfered corners that round the wedge edges slightly). The difference is subtle but affects the overall feel of the menu. Classic is crisper; Plate is softer. Both are available on all layouts.

Gesture Sensitivity Tuning

Two numeric settings control how the menu responds to your mouse movement:

Hold threshold (100-1000ms, default varies by trigger). This is how long you need to hold the trigger button before the menu appears. A shorter threshold makes the menu feel more responsive; a longer threshold prevents accidental activations. If you find the menu appearing when you don't want it — for example, during a slow right-click to access Chrome's native context menu — increase this value. If the menu feels sluggish, decrease it.

Flick min distance (5-200px, default varies). This is how far your cursor must travel from the menu center to register a wedge selection. A lower value means small wrist movements are enough to trigger actions — fast, but more prone to accidental selections. A higher value requires a more deliberate flick — slower, but you'll never accidentally close a tab because your cursor drifted two pixels.

For speed optimization, experienced users typically set hold threshold to 100-150ms and flick min distance to 15-25px. For accuracy (or if you have tremor), hold threshold of 300-400ms and flick min distance of 40-60px work well.

Per-Context Action Bindings

This is where Wilee's configuration depth really shows. Each of the four contexts — Text, Link, Image, Page — has its own independent set of action bindings. The actions in your text-context menu are completely separate from your link-context menu.

To edit bindings: in the Gesture section, use the context tabs (Text, Link, Image, Page) above the preview to switch contexts. Click any wedge in the preview. The editor panel below the preview shows the current action for that wedge and a catalog of all available actions for that context. Click an action in the catalog to assign it to the wedge.

Available actions vary by context. The text context offers Copy, Cut, Paste, Search, Define, and LLM actions. The link context offers Open in New Tab, Open in Background, Copy URL, and Copy Link Text. The image context offers Save Image, Copy Image, and Open in New Tab. The page context offers navigation (Back, Forward), tab management (Close Tab, New Tab, Reopen Tab), scrolling (Top, Bottom), and more.

You can also assign custom macros (multi-step action sequences you define in the Macros section) and prompt templates (LLM prompts with placeholder text) to any wedge. This means a single flick can trigger a complex workflow — for example, a macro that copies selected text, opens a specific URL, and pastes into a form field.

Each layout stores its own bindings per context. If you switch from Radial 8 to Radial 4, your Radial 4 bindings are independent — changes you make in one layout don't affect the other. This lets you maintain different setups for different use cases without conflicts.

Wedge Colors

Beyond theme colors, individual wedges can be color-coded. When you select a wedge in the editor, a row of color presets appears. Clicking a color tints that wedge with a highlight, making it visually distinct from its neighbors.

This is useful for at-a-glance orientation. You might color your "destructive" actions (Close Tab, Delete) red, your LLM actions blue, and your clipboard actions green. The colors persist across contexts and layouts — they're tied to the action ID, not the position.

Trigger Configuration

The trigger is the button that opens the radial menu. Wilee supports four trigger options:

Separately, the trigger mode determines how you pick a wedge after the menu opens:

Keyboard Shortcut Trigger

For users who prefer (or need) a keyboard trigger, Wilee registers a Chrome shortcut: Ctrl+Shift+Space (Cmd+Shift+Space on Mac). Pressing this opens the radial menu at the currently focused element. Once open, you can navigate wedges with arrow keys, select by number key (1-9), or confirm with Enter.

This shortcut can be remapped or disabled at chrome://extensions/shortcuts. It's particularly useful for keyboard-centric users who want radial menu actions without switching to the mouse, and for accessibility scenarios where a keyboard trigger is more reliable than a mouse hold.

Menu Size

Four size presets scale the entire menu up or down:

Display Mode

Three options control what each wedge shows:

Animation (Motion)

Three animation styles for how the menu appears:

If your operating system's reduced-motion preference is enabled, Wilee overrides this setting and uses Instant regardless of your choice. You can also toggle reduced motion manually in Wilee's Accessibility section.

Speed Optimization Tips

Once you're comfortable with the basics, here are specific adjustments that make Wilee faster:

Reduce your wedge count. If you only use four actions in a given context, switch to Radial 4 instead of keeping eight wedges with four empty slots. Fewer options means faster visual scanning and wider targets. Hick's Law applies here: halving the options measurably reduces decision time.

Prioritize by frequency. Put your most-used action in the direction you flick fastest. For most right-handed users, that's up-right or right. For left-handed users, up-left or left. Your dominant hand has a natural flick bias — lean into it.

Use Instant motion. Aperture and Trail look good, but they add animation time before the menu is fully interactive. Instant removes that delay entirely. For power users optimizing for throughput, the visual trade-off is worth it.

Drop to Label on hover or Icon only. Once you've internalized your layout, you don't need to read labels on every activation. Icon only is the fastest because your brain processes the wedge position, not the text — but Label on hover is a good middle ground while you're building muscle memory.

Lower the hold threshold. The default is set conservatively to avoid accidental activations. If you've used Wilee for a few weeks and never accidentally trigger the menu, drop the hold threshold to 100-120ms. The menu will appear almost instantly when you hold the trigger.

Set per-context bindings deliberately. Don't accept the defaults indefinitely. After a week of use, review each context and ask: which actions am I actually using? Move unused actions out and promote the ones you reach for most to the easiest directions.

Use macros for multi-step workflows. If you find yourself repeating the same sequence — copy text, open new tab, paste into a specific field — build a macro for it. One flick replaces the whole sequence. The Macros section in settings lets you chain multiple actions into a single wedge.

Import and Export

If you've spent time configuring Wilee to your preferences, the Import/Export section in settings lets you save your entire configuration as a JSON file. This is useful for backup, for transferring settings to a new machine, or for sharing your setup with someone else. The export includes all bindings, themes, macros, prompt templates, and preferences.

Power users who maintain different configurations for different tasks (work vs. personal, writing vs. coding) can export multiple profiles and import whichever one fits the current session.

Configure everything. Try Wilee free.

Add to Chrome