octoscope v0.17.0 — trust it running all day 🟢
No new tabs this time. v0.17.0 is the boring-on-purpose release: I went back through everything you actually touch in a long session and made the app meaningfully steadier underneath. It does the same things v0.16.0 did — it just behaves the same in hour eight as in minute one.
The self-multiplying API traffic, gone
This is the one that actually mattered. octoscope's auto-refresh used to be able to spawn an extra timer chain every time you hit `r` or changed the interval. Nothing visible — but over a long session those chains stacked, and the app quietly accelerated its own polling. The longer you left it open, the faster it hit GitHub, and the more of your rate-limit budget it burned for no reason.
Now there is exactly one timer, period — no matter how many times you refresh or retune the interval. Stale ticks get dropped via a generation counter, and a nonsense refresh_interval (zero, negative, sub-second) is floored to something sane and never written back to your config. Refresh traffic is flat and predictable for as long as the app stays open.
Errors that read like sentences
GitHub's GraphQL gateway throws the occasional 502, and HTTP/2 streams sometimes die mid-flight. octoscope now retries them a few times with a short backoff before they ever reach your screen — so most transient hiccups you simply never see. And when something genuinely is wrong, you get a clean human sentence instead of a wall of raw 502 Bad Gateway HTML.
Smaller things that add up
• Sponsor and release-notes links are now real OSC 8 hyperlinks — clickable in iTerm2, WezTerm, Kitty, recent VS Code; plain text elsewhere.
• Paste into the filter works now, including multi-rune batches. Backspace is multibyte-safe, and search input is sanitized against ANSI/C0 escapes.
• The PR diff viewer honours the monochromatic theme contract (monochrome / phosphor / amber), and a deleted "-- comment" line no longer gets mis-styled as a diff header.
• Bumped golang.org/x/net and golang.org/x/sys to close known advisories.
Upgrade:
brew upgrade gfazioli/tap/octoscopehttps://github.com/gfazioli/octoscope/releases/tag/v0.17.0
As always: read-only, free, MIT, on Linux / macOS / Windows.
Curious — how long do you leave terminal dashboards open? Always-on second monitor, or open-check-close?
Replies
Great job! Answering your question - open-check-close, there's really no need for me to monitor the Github dashboard that closely :)
octoscope
@sk_uxpin Ha! That’s fair — and honestly, open-check-close is exactly the workflow this release is built for. The rate-limit fix means even quick check-ins won’t silently burn through your API budget in the background.
By the way, since you’re a quick-check kind of user — if you’re on a Mac, you might like FinderGit (https://findergit.app). It’s a native macOS file browser that shows branch, status, and diffs across all your repos in one window. Same idea of seeing everything at a glance, but from the file system side instead of the terminal.