Customization

Power Strip customization opens with the + button at the end of the strip. The modal has three tabs: Commands, Settings, and Status.

Commands Tab

The Commands tab manages the active command slots. You can:

  • Drag active commands to reorder them
  • Remove commands
  • Add commands from the available catalog
  • Reset the command list to its defaults

The default list is Quick Note, Save Clipboard, Toggle Floating Navigator, Search Memory, Open Project, Tasks, Drop File, and Recents.

Folder, Agent, Automation, and Browser Agent can have multiple instances. Adding another instance creates a child slot associated with the existing toolbar position and exposes it through the stacked-command flyout.

Bindings and advanced options are configured from the individual command's context menu rather than from one generic form.

Settings Tab

The Settings tab exposes:

  • Idle opacity, 20 to 100 percent
  • Vertical or horizontal orientation
  • Full opacity during drag
  • Sound effects
  • Display mode
  • Command labels
  • Lock position
  • Glow intensity, 0 to 200 percent
  • Focus glow
  • Debug hover visualization
  • Reset profiles

Full, Compact, and Peek work as display modes. The settings interface also shows a Hidden choice, but selecting it does not take effect — it resolves back to a visible mode. Use the app's global Power Strip visibility toggle when you need to hide the strip.

Status Tab

Status shows the current project and a Power Strip action log. It is a status surface, not a command editor.

Strip Context Menu

Right-clicking the strip background provides:

  • Full, Compact, and Peek
  • Command labels
  • Vertical or horizontal orientation
  • Lock position
  • Preview on Save
  • Reset position
  • Settings

The drag-handle menu provides display mode, command-label, orientation, and position-lock controls. Hidden is not offered in either menu.

Command buttons have type-specific context menus. Depending on the command, these can configure a folder, agent, automation, hook, browser settings, removal, or an additional instance.

Global and Per-App State

Power Strip keeps both global settings and per-application profiles.

Global settings include sound effects, labels, drag opacity, glow and focus-glow behavior, global visibility, and default display mode.

App profiles include position, display mode, lock state, orientation and opacity, preview behavior, default sidecar close policy, and command slots.

When the foreground application changes, Power Strip restores position, display mode, lock state, orientation, idle opacity, drag opacity, and browser-command visibility. Preview and sidecar policy are read from the current profile when used. Command arrangements do not switch live per application.

Position and Locking

Power Strip can be dragged when unlocked. It snaps to a screen edge and saves its position. Reset Position returns it to its default placement.

Drag clamping and reset use the primary screen. This can constrain positioning on secondary monitors, even though sidecars choose their placement from the screen nearest the strip.

Lock Position prevents ordinary repositioning and is one of the values restored on foreground-app changes.

Command Labels

Command labels are a global visibility option. They render in separate lightweight windows aligned with command buttons and refresh when strip layout or visibility changes.

Glow and Activity Settings

Glow intensity controls the strength of execution feedback around Power Strip. Focus glow and debug hover are additional visual options.

Activity opacity controls the floating cards' resting opacity from 25 to 100 percent. Activity placement can follow Power Strip or use the upper-left or upper-right corner of the screen containing it. The cards become fully opaque while the pointer is over them.

Activity opacity and placement are global settings. These settings affect presentation; they do not configure Agent execution.

Preview on Save

Preview on Save can be toggled from the strip context menu. Supported local save paths can open a preview after a successful save. Browser captures request preview after the extension result is imported on the desktop.

Preview is not implemented as an independent override on every command type. Treat it as a supported-path setting rather than a guarantee for all commands.

Sidecar Close Behavior

An app profile can supply the default sidecar close policy. Individual panels can override that default from the sidecar behavior control.

Available policies are stay open, close after the primary item action, close after a successful action, and close on focus loss.

Current Limitations

  • Hidden is not a working settings-selected display mode.
  • Command arrangements do not switch live per application.
  • Primary-screen clamping limits some multi-monitor placement.
  • Browser buttons are shown by Chrome foreground detection, not connection state.