Use case · agent workflows
Three Claude Code windows side-by-side and you can't tell them apart from the dock. Open a fourth and you lose the thread. Terminal Tags fixes that by sticking a colored, persistent label on every window and giving you a saved launcher per session so spawning the next one takes a click.
One tag per session. Red is the refactor branch, blue is the bugfix, green is the docs PR.
Running one Claude Code session is fine. Running two is fine. The trouble starts at three: the OS task switcher shows you a row of nearly identical black terminals, all titled some flavor of “node” or “Terminal,” and you have to read the prompt to remember which repo you're even in. Cmd+Tab past the wrong one and you start confidently typing into the wrong session.
Tabs help inside one terminal app but they don't survive Mission Control, virtual desktops, or accidentally Cmd+Tab'ing away. And the agent itself doesn't volunteer which world it's living in — it just answers your question, in whatever repo it happened to be started in.
What you actually want is a permanent, glanceable identity on every Claude Code window so “which session is this” becomes a half-second question, plus a way to spawn the next one without re-typing the same setup every time.
Colored OS-level labels per window
Pin a colored tag to any terminal window. The label rides on top of the window itself, so it survives Cmd+Tab / Alt+Tab, Mission Control, workspaces, and any third-party window manager. Five Claude Code windows become red / blue / green / yellow / purple at a glance. Free forever.
Global hotkey to tag
Set a system-wide shortcut and tag the currently focused window without ever reaching for the menu bar. Spin up a new Claude Code session, hit the hotkey, type a one-word label, done. Free forever.
Saved agent profiles in your tray (Pro)
Save a launcher per Claude Code variant — one for each repo, branch, model, or persona. Profile knows the working directory, the env, and the tag color to attach on spawn. Click it from the menu bar / system tray and a labeled session opens, ready to work. Multiple Claude Code instances don't need to start with the same boilerplate every time.
Agents can stage their own profiles
Terminal Tags ships a CLI so a running agent can write its own profile file. Let Claude Code set up the launcher for the next Claude Code session. You review the staged profile locally before it shows up in your tray. Free forever for the staging pipeline; Pro turns staged profiles into one-click launchers.
Works across both desktops, one license
Native menu bar app on macOS, native system tray on Windows. Your Pro license covers both desktops — useful if your daily driver and your work laptop are different OSes.
Install Terminal Tags.
Free download for Mac (Developer ID signed + notarized) and Windows (Trusted Signing). Grant the one-time accessibility / screen-recording prompt so the app can draw labels on top of other windows.Tag your first Claude Code window.
Open Claude Code in your normal terminal. Hit the global hotkey, click the window, pick a color, type a name. Repeat for the second session. You can run as many tagged windows as you want on the free tier.Save a profile per session.
From the menu bar / system tray, create a saved profile per Claude Code variant. Set the working directory to the repo, set any env vars, pick the tag color in advance. With Pro, click the profile and a tagged session spawns — no more re-typing the same setup every time.Glance to switch.
Look for the red label to find the refactor session. The blue one is the bugfix. No more accidentally pasting into the wrong Claude Code window.Free for unlimited window tagging. Pro adds saved profiles and one-click agent launching for the times you spin up sessions all day.
Get Terminal TagsMac · Windows · one license, both desktops
Keep reading