Glint
Claude Code activity, right where you want it.
Start new thread

Glint - Claude Code activity, right where you want it.

by•
Glint is a lightweight macOS menu-bar app that surfaces what your Claude Code sessions are doing - live status, the current tool, token spend, the plan, subagents, usage meters, and context window - in a glanceable island near your notch, a floating pill, or beside the Dock. Reads ~/.claude locally; your session data never leaves your Mac. Support for other providers like Codex, Kiro and etc are on the roadmap to be release ASAP!

Add a comment

Replies

Best
Maker
📌
I run multiple Claude Code sessions throughout the day, and I got tired of constantly alt-tabbing into terminal windows to answer two questions: Is it done? And is it waiting on me? So I built Glint a lightweight macOS menu bar app that surfaces Claude Code activity in a Dynamic Island-style overlay near the notch. If you're not a notch fan, there's also a draggable floating pill that works over full-screen apps, plus a Dock-side bar that uses otherwise wasted screen space. What Glint shows: - Live status: thinking, idle, or waiting for input. This was the main reason I built it—no more sessions sitting blocked for 20 minutes because I forgot about them. - Per-turn tokens, cost, and elapsed time, matching Claude Code's own status line. - Current plans and active sub-agents. - Context window usage. - Multiple sessions at once: the one needing attention takes priority, while the rest remain visible in an expanded view. - Session and weekly usage limits, complete with reset countdowns. - Optional subtle sounds when a task finishes or requires input. Privacy: Glint reads the session logs Claude Code already writes to ~/.claude, entirely on-device. No telemetry, no data leaves your Mac. The only network request is license validation. Performance: Near-zero CPU usage at idle, even with hundreds of MB of session history. Glint only tails actively written transcripts and refreshes at most once per second.

Sessions sitting blocked for 20 minutes because I forgot is exactly my problem too, except I'm on Windows so I can't try this. The "waiting for input" priority view is the feature I'd actually want most — that's the moment that costs the most time. Hope this comes to other platforms eventually.

Maker

 Thanks José, that "waiting for input" priority view is the heart of Glint, and Windows is firmly on the roadmap (the lifetime license even includes the Windows and Linux versions free when they land), so hang tight.

The thing I never solved is the alt-tab tax... I kick off a Claude Code run, switch windows, then keep flipping back to see if it's done or just stuck waiting on me. Does it flag when Claude's blocked on a question vs still working? That gap is what actually eats my evenings.

Maker

 That gap is the whole reason I built Glint. It tells the states apart: Thinking (still working, with the live tool) vs Awaiting - needs you (blocked on your answer), right in the notch/pill/dock. And there's an optional sound output (which can be configured in app settings) which will trigger when a run finishes or needs input, so you can stay in another window and get pinged only when you're the bottleneck. Would love your feedback if you give it a go.

Maker

Glint roadmap already includes building support for other providers like Codex, Kiro and etc.

Most of my claude code sessions run in the background while i'm doing something else. watching a video, handling emails, whatever. glint is the thing that actually tells you when it needs your attention without you having to go check. the subagent view is a nice bonus too - parallel sessions get chaotic fast. been using it every day since i stumbled on it

Maker

 Glad it's been useful! That background workflow was exactly the problem I built Glint to solve. Thanks!

Claude Code in the menu bar is exactly the tiny status layer I want. Half my agent anxiety is just wondering if it is cooking or asleep.

Maker

 Thanks! That's great to hear. Glint gives you that glance so you always know if it's thinking, idle, or waiting on you, without breaking flow.

Claude Code activity surfaced where i'm already working is the kind of utility that becomes invisible in the best way once it's there. curious what the most common surfaces have been so far. is it editor adjacent (sidebar, status bar) or more in the team layer (slack, pr review). and is the activity feed read only or actionable from inside it?

Maker

 Right now Glint can live on the notch, a draggable floating pill, and a dock-side bar showing status, plan, tokens, and sub-agents - but by the end of this week we're shipping the actionable bit like jumping straight to a session's terminal from the expanded view and support for other providers as well.