Hacker News
Show HN: A terminal glued to the macOS dock
I usually have 3-4 vscode windows open at the same time, and I like them in separate desktops (for mac users). i gotta admit, i use 8 desktops, 3-4 for vscode, 1 for arc, 1 for docker, 1 for postman etc.
So my daily routine when I turned on my mac was: (1) open ghostty; (2) cd-path+code.; (3) drag the vscode window to a desired desktop; (4) get back to the ghostty desktop; (5) repeat until all is open.
i was unbothered for 6y. Until i realized how inefficient i was being: (1) opening ghostty just to run one-off commands to open another app felt wrong, like why do I need a terminal if it's not a process I need to watch; (2) the need to go back to the ghostty desktop every time i wanted to open a new project and drag it to a new desktop and switch back... it's funny how we simply accept a habit and don't bother to fix it
i wanted a terminal that persisted across desktops AND that was always visible so i could access it anytime AND that wasn't big because i would only run one-off commands. so I created starboard.
where could I fit a terminal that was always visible and accessible? i looked at the macOS dock, i looked at the empty space to its right, and I said "that's it".
starboard is a floating terminal window that's literally glued to the dock, filling the blank space to the right, tracking its height and position live. it's visible from any desktop, a real companion to the dock, and it's a persistent shell.
to close the story on my routine, I now can happily jump straight to the desktop i want my project to be in and open it there through Starboard. i rarely open ghostyy, unless i really need it.
here's where feedback is massively important. i built this for the way i work with it, the way my dock is, which is in the bottom. my dock's position and height give me a perfect sized Starboard with 3 visible lines that I can happily work with. hearing from you guys how it appears to you would be essential for further improvement.
prabhanjana_c
|next
[-]
My workflow as of today is open a terminal at documents/claude_mac_master folder , with Claude Code cli. always running. this is my master for all frequent tasks.
frequent commands I use on that. - 1. open vscode for project with name (it searches and finds the matching folder and then opens the vscode, then onwards it remembers my top 10 projects or folders working on ), 2. move the recently downloaded images to right folder. 3. create a new experimental project with following vision, in the right folder, open it in cmux (another agentic terminal) , with vision.md so that I will continue to work on that. 4. check disk sizes, and any cleanup.
would like to run the any cli agent in this terminal with default operations.
leopalamim
|root
|parent
|next
[-]
new release: a new 0.8.2 version was released and starboard now expands ignoring the dock and centering itself on the screen. it still sits above apps though.
the default width you're experiencing is most likely because your dock is wide. if you want more room in the default starboard, i'd recommend reducing dock's height and removing apps you don't naturally open from the dock. starboard will automatically resize itself and have more room.
the new expanded version might help you now. however, for your workflow, i'd recommend using starboard for fast ambient stuff (open VS Code for project X, sort downloads, quick disk check...) and a real terminal for claude code sessions.
i use claude code on starboard though and it persists across desktops which helps.
tell me how you feel about the new change and what other use cases you're using starboard for
Maphielbso
|next
|previous
[-]
leopalamim
|root
|parent
|next
[-]
what use case are you thinking for starboard? running agents?
leopalamim
|root
|parent
|next
|previous
[-]
nottorp
|root
|parent
|previous
[-]
Not that I dislike it.
leopalamim
|root
|parent
[-]
leopalamim
|next
|previous
[-]
(1) starboard now expands to full height, you can run agents and longer processes now
(2) starboard is now also a downloadable app, macOS will warn the dev can't be verified because it's ad-hoc signed, just hit privacy & security -> open anyway, step by step in the README.md
(3) source is still there if you want to read it yourself and build