Control StableBar from Shortcuts, Spotlight and stablebar:// links

Open
#205 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
macos, swift

Research direction

Start with the command-line controls in docs/command-line.md and trace how they become RuntimeRequest actions; inspect Resources/Info.plist and the app entry points under Sources for URL event handling. The issue calls for App Intents and stablebar:// links covering the same runtime actions, plus a decision on whether URL-triggered scripts need a setting. Done means both entry paths invoke the existing actions and the trigger safety behavior is defined.

Written by the indexing model from the issue text.

Description

enhancement P3

Problem

Every runtime action goes through the command line: --popup, --profile, --refresh and --trigger (see Command-line controls). Shortcuts can only reach them through Run Shell Script with the full path to the binary, and launchers such as Raycast and Alfred need a script command for each action. Links in notes or web pages can't reach the bar at all.

macOS 26 brought Shortcuts automations (Focus, time of day, Wi-Fi) to the Mac and runs App Intents from Spotlight. A shortcut can also have a keyboard shortcut, so App Intents would give global hotkeys without StableBar needing a hotkey editor.

Proposal

  • App Intents for the existing actions: open or close a widget's popup, switch the profile or return it to automatic, refresh a widget, and send an event with data. Widget and profile parameters list the IDs and names in the current configuration. An AppShortcutsProvider makes the common ones appear in Spotlight and Shortcuts without setup.
  • A stablebar:// URL scheme for the same actions, such as stablebar://popup/meeting, stablebar://profile/focus, stablebar://refresh/weather and stablebar://trigger/deploy?STATUS=done. It needs CFBundleURLTypes in Info.plist and a handler for the open-URL Apple Event.
  • Both go through the same RuntimeRequest actions as the command line, so they behave the same and the CLI stays the reference.
  • Configuration edits (--set, --add, --batch) stay on the command line.
  • Open question: a link can come from any web page or document, so decide whether trigger over a URL, which can run widget scripts with the data it carries, should be allowed or need a setting.

Both use public APIs only: App Intents (macOS 13+) and URL types in Info.plist. Resources/Info.plist on main declares no URL types, and Sources has no App Intents.

Possible today

Partly. A Run Shell Script action, or a Raycast or Alfred script command, can call /Applications/StableBar.app/Contents/MacOS/StableBar --popup <id> and the other flags. That needs a shell for each action, shows up in Spotlight only through a user-made shortcut, and can't be a link.

Related

  • #72 added --popup; its example binds it in AeroSpace, skhd or Raycast through the binary.
  • #81 lets commands set conditions that profiles match; App Intents would let Shortcuts automations set them without a shell.
  • #70 hides and shows the bar; when it lands, it fits the same intents and URLs.
  • Demand elsewhere: Ice #501, Raycast integration (open, 28 reactions).

Triaged by Claude Code via T3 Code (Claude Opus 5.5).

Dominant language
Swift
Stars
184
Forks
12
Avg merge
3h 50m
Merged PRs (30d)
387

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from Seb-GRAF/StableBar

All issues in Seb-GRAF/StableBar

Similar issues

More Swift issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.