Codenotch: The Notch That Makes AI Usage Visible

A macOS utility that pulls live state from Claude, Cursor, Ollama, and other tools, then turns hidden quotas and session activity into a persistent, glanceable edge display.

8 min read • View on GitHub • More from vinzdg

A MacBook viewed from a wide angle, with a slim notch-shaped instrument pinned to the screen edge. Tiny status rings inside the notch suggest separate AI tools, while an IDE fills the rest of the display. The image explains that Codenotch stays visible without becoming another dashboard.
Codenotch turns AI usage into something you can read peripherally, not something you have to open.
Key Takeaways

Why AI Workflows Need Ambient Visibility

AI coding tools are useful partly because they disappear into the flow of work. That is also the problem. They can be busy, rate-limited, waiting, or finished, and the only way to know is often to stop coding and check another surface.

Codenotch answers that by treating usage like ambient information. It does not ask for attention. It sits at the edge of the screen and turns the state of your assistants into something you can read without leaving the editor.

I built Codenotch as a small macOS utility for one very specific problem: keeping an eye on how much of your AI coding limits you're burning through. It sits quietly on the edge of your screen as a little notch and shows the usage of your coding assistants at a glance.

vinzdg, Author/Maintainer · Codenotch is going open source

A Notch, Not a Dashboard

The metaphor is the product. A dashboard asks you to visit it. A notch stays present while doing its best not to become a destination.

That is why Codenotch feels different from the usual menu bar utility. The UI is small, edge-pinned, and designed for peripheral awareness. It behaves like instrumentation, not like a window you manage.

A close cutaway of a relay chamber where a stream moves through a transparent valve and continues onward. One branch is marked as the local model path, and a central chamber gathers signals that imply speed and activity. The image explains how Codenotch observes local AI traffic without turning the workflow into a separate app.
The clever part is not just what Codenotch shows. It is how it sees it in transit.

How Codenotch Borrows State Instead of Asking for Logins

The most interesting choice in the repo is not visual. It is architectural. Codenotch does not assume it owns the user relationship. It reads state that already exists on the machine, then normalizes that into one view of activity.

That means different providers show up through different surfaces. Some are local files. Some are SQLite databases. Some are keychain entries or local ports. The app is built as a provider system, so each source can be adapted without changing the UI contract.

Codenotch works because it discovers state where the tools already store it, then turns that into one consistent display.

The architecture suggests a simple idea with a big payoff. If the tool already knows where each provider hides its own state, the user never has to rebuild identity or repeat setup just to get visibility.

No vendor publishes a clean usage-percentage API for most of these tools, so each adapter reads whatever internal endpoint or local database the owning app itself reads from, and those can change without notice.

The Relay Trick for Local Models

Codenotch gets especially clever with local model traffic. Instead of treating local inference as a black box, it can sit in the path and observe the stream as it moves. That makes activity, throughput, and progress visible while the request is still alive.

This matters because local tools often expose the least satisfying kind of opacity. They are running somewhere on your machine, but they do not always give you a clean, live sense of whether they are thinking, stalled, or done. The relay closes that gap.

The Window That Refuses to Behave Like a Window

The AppKit side of the repo is where the notch becomes believable. The panel is nonactivating, which means it can float over other apps without stealing focus. It also supports click-through behavior, so only the meaningful chrome catches input.

That small detail changes the feel of the whole product. The app is present, but not needy. It can be repositioned with option-dragging, and it uses hover grace logic to avoid twitchy disappear-and-reappear behavior when the pointer skims past it.

Where It Fits in the Competitive Landscape

Codenotch sits in a crowded corner of the market, but the trade-off is clear. It optimizes for ambient visibility and zero-login convenience, while other tools optimize for broader provider coverage, official auth, or deeper analytics.

ToolPrimary UIData source approachStrengthTrade-off
CodenotchScreen-edge notchBorrowed local state and relay streamsAlways-visible, low-friction awarenessDependent on internal surfaces that can change
OpenUsageMenu bar appPlugin architecture with many providersBroad support and extensibilityLess ambient, more click-based
CodeQuotaMenu bar appOfficial OAuth flowsStable authenticated accessNarrower provider set and more setup
Claude GodDashboard-style appClaude-focused analyticsDeep trends and forecastsSpecialized, less cross-provider
Claude NotchNotch-style UIClaude and Codex-focused trackingHardware-notch metaphor fits the Mac wellNarrower scope than Codenotch

That comparison is the point. Codenotch is not trying to win by becoming the deepest analytics suite. It is trying to win by being the thing you notice first, because it lives where your eyes already go.

It also answers the question the official commands do not: whether a run is still working, shown as a thin arc that spins while a provider is busy.

vinzdg, Author/Maintainer · About Codenotch - vibecoding.app

Why This Repo Feels Bigger Than One Mac App

The Windows port matters because it signals a pattern, not just a product. The provider and relay shape can travel. So can the idea that AI workflows should be surfaced in the environment where they happen, rather than in a separate monitoring layer.

That is the deeper promise here. Codenotch is an observability layer for AI coding workflows, disguised as a notch. If the next wave of developer tools is going to be truly ambient, this is the kind of shape it will need.