... there's no inbox key at all; if you asked and you're at inbox zero, it's []. And if the fetch fails, the run fails. It never quietly prints something that looks like inbox zero. brew upgrade gfazioli/tap/octoscope How do you keep up with GitHub notifications today: the web bell, email filters, gh? And where would you pipe this first? Site: https://gfazioli.github.io/octos... Newsletter: https://octoscope.substack.com Mastodon: https://hachyderm.io/@undolog ...

... spinner's own ticks and stops when the spinner does, so it adds no delay at all and the octopus on the website is the very same drawing, held to the Go source by a test. Upgrade: brew upgrade gfazioli/tap/octoscope Does a little life on a loading screen make the wait feel shorter to you, or would you rather have just the spinner? And what does your terminal show you while it waits? Vide: https://youtu.be/y3639rBcizA Site: https://gfazioli.github.io ...

... cask rather than a formula, so it serves Linux Homebrew too. And a confession 0.34.0's macOS cask installed a binary that macOS killed at launch, because a cask's download is quarantined where a formula's is not. brew upgrade --cask gfazioli/tap/octoscope fixes it. Every check in my pipeline was green; not one of them executed the thing it installed. That one's on me and there's now a gate for it. brew

... feed through jq and you have a personal work log you can diff from one day to the next; and if you script against it, branch on whether recent_activity is present , not on whether it is long. Upgrade: brew upgrade gfazioli/tap/octoscope How do you keep an eye on your own activity the GitHub dashboard, notifications, something you built yourself? And if you already script against octoscope, what is the next thing you would want in --json? Site: https://gfazioli.github.io ...

... gfazioli/gh-octoscope and it answers to gh octoscope. A container on ghcr.io , multi-arch and about 7 MB, for --json and --plain. The bare executables sit next to the archives on every release, so a curl needs no unpacking. And brew, as always. The container is deliberately not the dashboard. A TUI inside a container has nothing attached to read it, so it refuses and tells you why; --json fetches once, prints and exits, which is the shape a CI step ... ... strength of cross-compilation alone CI had never built it natively, run its tests, or started it once. It does all three now, and three packages that branch on the OS went from zero tests to covered. brew

... files churn constantly; the install-script subset moved twice, and the same version was republished zero times. That zero is what lets the sharp case carry real weight instead of teaching you to skip the axis brew upgrade gfazioli/tap/octoscope What does your team actually do with a lockfile diff today read it, skim it, or trust the bot that opened the PR? Site: https://gfazioli.github.io/octos... Newsletter: https://octoscope.substack.com Mastodon: https://hachyderm.io/@undolog Comment from Giovambattista Fazioli(@gfazioli): @sumonmatrix ... ... security tool trustworthy. Makes total sense that the write is unconditional otherwise you'd have to build a whole separate 'is this repo clean' system just to decide when to record. The trade-off you described (false positives vs

... does: if you flip it while a refresh is already running, the change is remembered and one more fetch follows when that one lands so you never see a result that read the old setting on its way out. brew upgrade gfazioli/tap/octoscope Honest question for the people who run big accounts: would you rather a column like this stay opt-in with a cost you can see, or just be on and eat the 4 6 seconds every refresh ...

... compared anything. And if you'd rather octoscope talked to exactly one host, check_service_status = false opts the status check out entirely; it's the only feature that contacts anything other than GitHub's API. Upgrade with brew upgrade gfazioli/tap/octoscope I'm genuinely curious about one thing: has a tool ever told you it was fine when it hadn't actually checked? That's the failure this whole release is chasing, and I suspect everyone has a story. What ...

... request folds into a single row with a N count, so a heavily-reviewed PR stops burying the week. But an approval never folds. Collapsing the one review that mattered into a " 12" was the whole failure to avoid. brew upgrade gfazioli/tap/octoscope Curious what the last thing you left the terminal for was I keep finding one more. octoscope 0.29.0 the Overview tab with the eight-entry tab row octoscope 0.29.0 the Inbox tab, unread notifications with their reason, repository ...

... handed, so a workflow asking for contents: write whose caller passes nothing holds nothing. Getting that backwards would have flagged a pile of perfectly safe repos, and a security tool that cries wolf is one you learn to ignore. brew upgrade gfazioli/tap/octoscope Cross-repo chains are still out of scope a call into another repository is reported as an unfollowed chain rather than quietly ignored, but it isn't traced. How do you audit workflow permissions today ...

... fine" and "I had nothing to look at" is worse than one that admits it. The same reasoning made the checks needing admin scope fail open but still name themselves: "deploy keys (the token lacks the scope this needs)". brew upgrade gfazioli/tap/octoscope So: how would you find out today that something which auto-executes changed in one of your repos? I keep asking people this and the honest answer is usually "I wouldn't". Curious whether that matches your experience ... ... first group is the one that needed the fingerprint, and it's the group i'd bet on long term: it survives renames and re-obfuscation for free Comment from Giovambattista Fazioli(@gfazioli): @bill_frad  thanks "informative vs

... blank pane, wondering whether the fetch had broken. Now it tells you the filter is what's hiding them, and which key clears it. Zero results is a state, not an error it just had to say which one. brew upgrade gfazioli/tap/octoscope Eleven backlog items in this one, all of them things people actually hit. So: how do you check CI across all your repos today a browser tab, or has something in your terminal earned that ...

... Checks API, its link points at its own dashboard and a GitHub-looking row shouldn't be a one-click trip somewhere else. URLs carrying bytes that could break out of the terminal escape sequence are refused outright. brew upgrade gfazioli/tap/octoscope How do you check CI today browser tab, gh CLI, or something else? I'm curious whether the terminal is where you'd want this at all, and what you'd reach for next. https://gfazioli.github.io/octos... https://octoscope.substack.com ...

... recommendations. For me, these are: Ad Professor Tom s Marketing Ideas PH Newsletter Feel free to share your own list as well. Comment from Nika(@busmark_w_nika): @productrambler  I totally forgot about Lenny's Newsletter and Marketing Brew... I subscribed to them too but do not have so much time to read them all :D Comment from Nika(@busmark_w_nika): @foued_sendi  Wow, it seems to be a thick book :D Comment from Foued Sendi(@foued ... ... nika): @foued_sendi  aaaa, okay, sorry, I misunderstood that :D Comment from Lavakumar E(@productrambler): Here is my list that gets dropped in my inbox. I focus on the Product/Sales/GTM side of things. Lenny's Newsletter Marketing Brew

... detail view's own actions (o to open on GitHub, v to cycle a repo's star history) live in the title bar up top so nothing got hidden, the footer just stopped lying. Grab it, or upgrade: brew upgrade gfazioli/tap/octoscope What's the smallest UI detail that's ever made you trust or distrust a tool? I collect these octoscope: https://gfazioli.github.io/octos... Newsletter: https://octoscope.substack.com ...

... grabbing even if you never open a drill-in. Tip: press Enter on any Repos / PRs / Issues row to open the drill-in and inside a repo, v toggles the star sparkline between density and a cumulative curve. Upgrade: brew upgrade gfazioli/tap/octoscope More: https://gfazioli.github.io/octos... https://octoscope.substack.com How do you keep an eye on your GitHub activity without leaving the terminal? Curious what you'd want octoscope to surface next. Comment from Hossein Yazdi(@hosseinyazdi): Nice update. I like ...

... launch. Three new config keys default_sort, default_work_filter, default_star_history seed the list sort, the Repos work filter, and the star-history sparkline so octoscope opens the way you like it. Free & open source. Upgrade: brew upgrade gfazioli/tap/octoscope Site: https://gfazioli.github.io/octos... Newsletter: https://octoscope.substack.com ...

... theme and config without rewriting them. Unset it and your real theme (amber, phosphor, whatever you picked) comes right back. Better for monochrome terminals, screen-reader-friendly setups, CI logs, and anyone who just wants zero visual noise. Upgrade: brew upgrade gfazioli/tap/octoscope Still 100% read-only octoscope never touches your GitHub state. Website: https://gfazioli.github.io/octos... Newsletter: https://octoscope.substack.com ...

... issues across different repos that you keep scrolling back to find, they now stay exactly where you put them. As always it stays read-only public GitHub, your existing gh login or a $GITHUB_TOKEN, no mutations. brew upgrade gfazioli/tap/octoscope Comment from Giovambattista Fazioli(@gfazioli): @hosseinyazdi  thanks Hossein, really appreciate it octoscope is something i use every day, so most releases are just me scratching my own itch. pinned issues was one of those why didn ...

... refresh octoscope checks the public Releases API and, if there's something newer, drops a quiet one-line notice under the banner. The upgrade command is context-aware: it detects how you installed octoscope and suggests the right one brew upgrade, go install, gh extension upgrade, or a download link. It never self-updates. The package manager owns the binary, and auto-overwriting it would fight brew/gh/go and break octoscope's read-only model. The check is cheap one free ... ... Both the repo and CI queries now paginate through the whole set (up to 500), so the numbers and the list are finally complete. With 100 or fewer repos nothing changes it's still a single page. Upgrade brew

... Shai-Hulud / Miasma worm has been quietly pushing itself into people's GitHub repos including real, well-known OSS projects where it auto-runs the moment you open the repo in an AI editor (Claude / Cursor / Gemini / VS Code) or install it, then harvests your tokens. It lives in the GitHub source, not the npm registry, so a lockfile audit never sees it. octoscope already points at the repos you own, so this release teaches it to look. @icflorescu What ... ... hands you a copy-paste remediation script (press y) clone-without-checkout, reset-not-revert, and the right pages to revoke the OAuth grant, not just the token. You run it; octoscope just shows you the door. Upgrade brew

... doing; the panel tells you why. Work filters On the Repos tab, w cycles quick presets: PRs open, CI broken, stale 90d. They compose with the / search and span pinned, owned and watched sections alike. One esc clears everything. brew upgrade gfazioli/tap/octoscope https://github.com/gfazioli/octo... As always: read-only, free, MIT, on Linux / macOS / Windows. Source: https://github.com/gfazioli/octo... Curious what preset would you add to the work filters? "needs my review"? "no release in 6 months"? Comment from Giovambattista ...

... 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 ... ... 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

... galdayan): our setup ended up being a Slack webhook per agent session, posted to a channel only that agent writes to. sounds basic but the key part was making the notification say WHY it's waiting (needs approval vs finished vs

... running, bundled into the binary so it works offline, with a link to the full release notes. Keyboard-shortcut overlay (press ?) a full keymap grouped by area, finally inside the app instead of just the footer. Upgrade: brew upgrade gfazioli/tap/octoscope Thanks to everyone running it and if octoscope saves you time, a sponsorship genuinely helps keep it maintained. Comment from Aarav Pittman(@aarav_pittman): Great launch! I ve been using Octoscope for a while, and these small improvements really make ...