Why doesn't LinearNotify's count match Linear?

LinearNotify fetches the 50 most recent notifications and deduplicates by groupingKey — the same method Linear uses internally. Hold the key for 2 seconds to force a refresh. If it still looks wrong, sign out and back in from the Property Inspector.

Why does LinearNotify require port 28976?

Linear's OAuth requires an exact redirect URI match. The redirect URI is registered as localhost:28976, so that port can't change. If something else is using port 28976, quit it and try signing in again.

LinearNotify — Linear inbox count on your Stream Deck

The point of a notification system is to tell you something changed, not to make you go check. LinearNotify gives you one number on one key. When it ticks up, you notice. Tap to go straight to your inbox.

What it does

Unread inbox count — always current, always on your deck. Polls every 60 seconds.
Exact match with Linear's counter — fetches your 50 most recent notifications and deduplicates by groupingKey, the same method Linear uses internally. The number matches what you see in the app.
Tap to open inbox — one press goes straight to linear.app/inbox.
Double-tap to open the latest issue — skips the inbox list and lands you directly on the most recent item.
Hold 2 seconds to force refresh — when you've just merged a PR and want the count to clear now, not in 60 seconds.
"X min ago" timestamp — the key shows when it last refreshed so you always know how stale the number is.

Who it's for

Engineers

You're deep in a task. A review comment, an unblock, or a question from a teammate might have dropped. You don't need to open Linear to find out — the key either changed or it didn't.

Product managers

You're monitoring several active projects across multiple teams. LinearNotify doesn't pull you in — it just makes the information available the moment you glance at your deck.

Designers

You handed off a design and you're waiting on feedback. When the count moves, something came in. You go look; otherwise you stay focused.

Getting set up

Install LinearNotify from the Marketplace and drag the Inbox action onto a key.
Open the key's Property Inspector and click Sign in with Linear.
Authorize in your browser. The plugin starts polling within a minute.

Port 28976 must be free when you sign in. Linear's OAuth requires an exact redirect URI — the port is fixed and can't change. If sign-in fails, quit anything that might be holding that port and try again.

Good to know

My count doesn't match what Linear shows

LinearNotify fetches the 50 most recent notifications and deduplicates by groupingKey — exactly how Linear calculates its own counter. Older notifications outside that window aren't counted. Hold the key to force a refresh. If the number still looks wrong, sign out and back in from the Property Inspector.

Sign-in page doesn't load

Port 28976 is occupied. Linear requires an exact redirect URI match, so the port can't be changed. Find and quit whatever's using it, then try signing in again.

The count is stale

Hold the key for 2 seconds to trigger an immediate refresh. If it keeps showing old data, the token may have expired — sign out and back in from the Property Inspector.

View in Marketplace →