Repository navigation
feat(agent): numbers on the windows while the modifier is held, and a mark of its own - #26
Merged
Merged
Conversation
… mark of its own - Holding the numbered shortcuts' modifier draws each window's ring number on it, so the digit to press is read rather than counted. On by default; `windowNumbers` and a menu item turn it off, `windowNumbersDelayMs` sets how long the hold has to be. - A number goes in the middle of the largest part of its window that nothing covers, rather than the plain centre, which lands on whatever buried the window and then names the wrong one. - Pointer focus is suppressed while the numbers are up: the next keystroke is going to pick a window, and following the pointer first would move focus somewhere else. - Replaces the SF Symbol icon with a mark drawn in code: what has your attention and the four ways focus can leave it. One description in `HeedCore`, shared by the menu bar item and the iconset, so the two cannot drift apart. - Renames the `FFMCore` module to `HeedCore`, after the repository's old name.
rbstp
enabled auto-merge (squash)
September 7, 2026 03:22
rbstp
disabled auto-merge
September 7, 2026 03:23
rbstp
added a commit
that referenced
this pull request
Sep 11, 2026
…creenshots (#38) The extension icon still carried the cursor mark the app dropped in #26; it is now rendered by the IconTool from the same Glyph.swift the app icon and menu bar item use, so the three cannot drift again. Renamed to icon.png because Raycast caches an extension's icon by path and kept showing the old one. The screenshots are retaken with the new icon: the root search, the Focus Window list, and Focus Window with its action panel open. The last replaces a "focus window" search that showed other extensions' commands alongside ours, which the store guidelines discourage. @raycast/api moves from 2.2.0 to 2.3.0, the current release.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Three things, all visible from the menu bar.
Window numbers
Hold the modifier the numbered shortcuts are registered under — ⌃⌘ by default — and each window
in ring order gets its number drawn on it, so the digit to press is read off the screen rather
than counted along it. Let go and they are gone. On by default; Show Window Numbers in the
right-click menu turns them off, and
windowNumbersDelayMssets how long the hold has to bebefore they appear (100 ms, short enough to feel immediate, long enough that a shortcut typed at
speed does not flash them).
A number goes in the middle of the largest part of its window that nothing covers, not the plain
centre. The centre is wrong often enough to matter: a maximised browser with a terminal parked
over it keeps its edges showing, so it stays in the ring, but its centre is under the terminal —
the badge would sit on the terminal and name the browser. It also keeps a dialog's number off its
parent's.
Pointer focus is suppressed while the numbers are up. The next keystroke is going to pick a
window; following the pointer first would move focus somewhere else and renumber the rest.
The numbers redraw after a focus shortcut and after a Space or display change, and are taken away
if the ring cannot be built. One ring build is in flight at a time with at most one more
remembered, so holding a shortcut down cannot queue a build per repeat on the queue the shortcuts
themselves need. A watchdog covers the case where the key release is never delivered — secure
event input takes the keyboard away from every monitor, so letting go inside a password field
sends nothing.
A mark of its own
The old icon was
cursorarrow.motionlines, which said "mouse" when Heed had grown into windowswitching, directional focus and now these numbers. The new one is drawn in code: what has your
attention, and the four ways focus can leave it. Filled core while Heed is on, empty while it is
off, so the switch position shows by shape as well as by the dimming, which also stands for
"no Accessibility permission".
The geometry lives once in
HeedCore.glyphPathand is shared by the menu bar item and theiconset renderer, so the two cannot drift.
Tools/make-icon.swiftbecomes aheed-iconSwiftPMtarget, since the Swift interpreter takes only one file and the alternative was two copies of the
same path. Proportions are ninths, so an 18 pt menu bar image lands its straight edges on whole
pixels at 1x.
Rename
FFMCorewas the repository's old name. It isHeedCorenow, along with its test target.make check-packagepasses and 254 tests pass. Verified live: the numbers appear ~150 ms afterthe modifier goes down, on the right windows, and clear on release.
Not in here, on purpose: Shortcut Modifier in the menu always refuses, because
claimre-registers combinations Heed itself already holds and because two shortcuts can rewrite onto the
same combination. That is a bug in the hotkey-claiming path, unrelated to any of the above, and
follows in its own PR.