Starboard trades a hotkey for a permanent panel, and an Accessibility grant for it
A terminal that's always beside your Dock — not a Quake-style hotkey overlay, a permanent fixture
At a glance
- What is it?
- A macOS terminal that lives beside the Dock with no hotkey and no focus stealing, delivered as an ad-hoc signed app that cannot enter the official Homebrew cask tap, needs four approval clicks on first launch, and silently loses its Accessibility grant on every in-place update.
- Who is it for?
- Adopt Starboard if you want a shell that is always there beside the Dock and never steals focus, and if you are willing to grant Accessibility access and re-grant it after updates. Do not adopt it expecting a drop-in Homebrew cask, since the official tap now requires notarized builds and this one is ad-hoc signed, and do not use it with a left or right Dock, which falls back to a fixed corner.
- Can I use it commercially?
- Yes. MIT is a permissive licence: you can use, modify and sell software built on it, as long as you keep its copyright and licence notices.
- Is it still maintained?
- Yes. The repository last received commits 53 days ago.
- What is it written in?
- Mainly Swift, according to GitHub's language statistics.
Answers come from the project's GitHub data, last synced on November 13, 2026, and from our analysis. They are not legal advice.
Star history
- palamim/starboard377 ★ · +4
| Repository | 2026-09-17 | 2026-11-13 |
|---|---|---|
| palamim/starboard | 373 | 377 |
4 Stars in the last 57 days, measured from the daily GitHub snapshot. Compare with other projects
Editorial analysis
No hotkey, no focus, and no dismiss
Starboard's premise is a refusal. A terminal is summoned with a hotkey, takes focus, and is dismissed again when you are done. Starboard has no hotkey at all, never takes focus, and has no summon or dismiss cycle.
Instead it sits permanently beside the macOS Dock, on screen, on every desktop, all the time, tracking the Dock's height and position live. It is visible on every Space, including over full-screen applications.
The shell underneath is a real persistent one, `zsh -l`, so `cd`, history and state carry over between commands rather than resetting like a one-shot command runner. That combination is the actual use case the README describes: run a command in whatever project you are in, then go straight back to the editor without switching applications or losing your place.
The comparison list is explicit about what it is not built to replace. Guake, Yakuake, tilda, iTerm2's hotkey window and Ghostty's quick terminal are all named as summon-and-dismiss tools. The trade is screen space: a panel that is always present is space you have given up permanently, which is a different bargain from one you accept for the ten minutes a hotkey overlay is open.
Ad-hoc signed, so the official cask tap is closed to it
Installation is one of two routes, and the reason there are two is worth reading first.
The Homebrew route needs the full repository URL rather than the short form, because the tap lives in this repository and the short form only works for repositories named `homebrew-*`:
brew tap palamim/starboard https://github.com/palamim/starboard
brew install --cask palamim/starboard/starboardThe stated reason Starboard cannot go in the official `homebrew/cask` tap is that tap now requires notarized builds. Starboard is ad-hoc signed and not notarized, which also means Homebrew does not save you the approval steps: a cask-installed copy hits Gatekeeper like any other download.
The manual route is the same three commands the tap saves you:
unzip Starboard.zip
mv Starboard.app /Applications/
open /Applications/Starboard.appWhat Homebrew does buy is the download, the move, and updates, since `brew upgrade` picks up each new release.
First launch takes four approvals, and the fourth one matters
Because the build is ad-hoc signed and not notarized, the first launch is a sequence rather than a single click.
Opening it is blocked outright with a Starboard Not Opened dialog, which you dismiss with Done. In System Settings, under Privacy & Security, you choose Open Anyway next to the Starboard entry, confirm Open Anyway again, and enter your password. Then Starboard launches and an Accessibility prompt appears, where you click Open System Settings and enable Starboard.
That last step is the one with a purpose attached. Accessibility access is what lets the panel read the Dock's live on-screen position, and it is the only sensitive-looking permission the app asks for.
Refusing is survivable rather than fatal. Starboard still works without Accessibility, pinned to a fixed corner instead of hugging the Dock, which is a reasonable degraded mode for anyone who would rather not grant it.
To have it start at login, the documented route is System Settings, General, Login Items & Extensions, then adding Starboard.app. No script is needed for either of the two install paths.
Every in-place update silently needs a fresh Accessibility grant
This is the operational detail that decides whether Starboard is pleasant or a chore, and the README is unusually candid about it.
Updating in place means overwriting the same `/Applications/Starboard.app`, which is what `brew upgrade` does too. That needs a fresh Accessibility grant, because each release is signed differently.
The trap is what happens next. System Settings can keep showing Starboard as already granted while it silently is not, and re-checking that same box does not fix it. So the symptom is that after an update the panel stops tracking the Dock, with no error and no prompt.
The remedy is to remove the Starboard entry from System Settings, Privacy & Security, Accessibility, by selecting it and choosing the minus button, or to run `tccutil reset Accessibility com.starboard.app`, then relaunch to get a fresh prompt. The README points at CLAUDE.md for why this happens and for what to do if you also have a source build installed through the install script.
If you update Starboard often, that command is worth keeping somewhere outside this article.
Source builds use a script because the code signature changes
Building from source is two commands:
swift build
.build/debug/StarboardRunning it at login takes a different path from either install method above. `scripts/install.sh` packages and code-signs a `.app` and registers it as a LaunchAgent, which the README explains is what keeps Accessibility permission across rebuilds, where adding to Login Items does not.
Once installed that way, it is managed with launchctl:
launchctl unload ~/Library/LaunchAgents/com.starboard.app.plist # stop
launchctl load ~/Library/LaunchAgents/com.starboard.app.plist # start
scripts/uninstall.sh # remove entirelyLogs go to `~/Library/Logs/Starboard.log`.
The reason for the script is the same root cause as the update problem in the previous section: the Accessibility grant is bound to a code signature, and a raw `swift build` produces a binary that does not match what was granted. Packaging and signing through the script keeps the identity stable across rebuilds, which is why the project routes login items through launchctl instead.
The tree explains the rest: Package.swift and Package.resolved for SwiftPM, a Sources/ directory, a VERSION file, a Casks/ directory that matches the Homebrew tap layout, and scripts/.
It follows an auto-hiding Dock, but not a vertical one
The positioning behaviour is where most of the small engineering lives, and the requirements section is specific about what works.
macOS 13 is the floor. Across displays, Starboard follows the Dock, and moving it to another monitor re-glues it there within a second.
With an auto-hiding Dock, the panel conceals and reveals along with it, with one exception: it stays put while you are actively using it, whether you are typing into it or have expanded it. That exception is the difference between a panel that helps and one that vanishes mid-keystroke.
The unsupported case is a left or right Dock. There the panel falls back to a fixed corner on the Dock's own screen, and the README points at CLAUDE.md for the detection details.
The other display feature is Cmd+E, which expands the panel to full screen height when Dock height is not enough, and Cmd+E again to snap it back. Cmd+T opens a theme picker driven by the arrow keys, Enter to apply and Esc to cancel, over twenty built-in themes split evenly between ten dark and ten light, including Gruvbox, Solarized, Monokai, One Dark and Light, Tokyo Night and Catppuccin. The default look is its own dark style with a muted nautical ANSI palette, which is a small piece of personality in a category where everything else is grey.
1,400 lines, no network requests, and one permission
The trust argument is made by size and by what is absent.
Starboard makes no network requests and collects no data. The README's point is that this is not a promise but a property of the source: there is nothing in the code that could, because the project is just over 1,400 lines across 17 Swift files, and it invites you to read them rather than take it on faith.
Against that, the one permission that looks sensitive is Accessibility, and its use is stated as exactly one thing: reading the Dock's on-screen position so the panel can sit next to it.
Two rendering bugs are listed as known issues rather than hidden. Pasted text briefly renders in the wrong colour until the next keypress. And some prompt glyphs previously rendered as question marks during live redraws, which the README says has not recurred recently. Both are pointed at CLAUDE.md for the full write-up, and that file also holds the architecture and design decisions behind the accessibility and multi-display behaviour.
Maintenance is current: MIT licensed, last push on 2026-09-23, with v0.21.0 tagged the same day and v0.19.0 and v0.20.0 both shipped on 2026-09-10.
Editorial conclusion
Adopt Starboard if you want a shell that is always there beside the Dock and never steals focus, and if you are willing to grant Accessibility access and re-grant it after updates. Do not adopt it expecting a drop-in Homebrew cask, since the official tap now requires notarized builds and this one is ad-hoc signed, and do not use it with a left or right Dock, which falls back to a fixed corner. Keep the tccutil reset command from the README handy before your first update.
Frequently asked questions
How do I install Starboard on macOS?
With Homebrew, using the full tap URL because the tap lives in this repository: `brew tap palamim/starboard https://github.com/palamim/starboard` then `brew install --cask palamim/starboard/starboard`. Or manually: unzip Starboard.zip, move Starboard.app into /Applications, and open it. It cannot go in the official homebrew/cask tap, which requires notarized builds.
Why does Starboard need Accessibility permission?
To read the Dock's live on-screen position so the panel can sit beside it. Without the grant Starboard still works, pinned to a fixed corner instead of tracking the Dock, and the README describes that as the degraded mode.
Starboard stopped tracking the Dock after an update, what do I do?
Each release is signed differently, so an in-place update needs a fresh Accessibility grant, and System Settings can keep showing Starboard as granted while it is not. Remove the Starboard entry from Accessibility, or run `tccutil reset Accessibility com.starboard.app`, then relaunch it.
Does Starboard work with multiple displays or a vertical Dock?
It follows the Dock across displays and re-glues within a second, and with an auto-hiding Dock it hides and reveals with it except while you are typing or expanded. A left or right Dock is unsupported and falls back to a fixed corner on the Dock's own screen.
Does Starboard make network requests or collect data?
No. The README states it makes no network requests and collects no data, and puts the reason in the source size, about 1,400 lines across 17 Swift files, which it invites you to read.
Official sources
Add this badge to your README
If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.
[](https://hysenlabs.com/projects/palamim-starboard)Star history chart for your README
[](https://hysenlabs.com/projects/palamim-starboard)Was this useful?