... this file?" instead of needing an id it no longer has. MCP moved to a URL nothing to install, works in any client with OAuth, so no year-long token travels through your shell history. Paste a GitHub repo URL and pick what to import. Comments now pin to characters in the CRDT, so editing inside a quoted phrase stops orphaning the thread. Here are three of my favorite improvements: Dark theme It toggles from three places: the next ... ... Each cycles Light Dark Match system, and Match system follows the OS live. Plus - I love how the logo looks in dark mode. The skill listener Nobody knows which skills their team actually uses. You can guess from the repo

... read the AGENTS.md of the 100 most-starred repos that have one (27% of the top 1,000 do). The consensus, in order of how much they write about it mostly: architecture and repo

... octoscope 0.27.0 the integrity scan stops describing a repo and starts noticing things about it. Before this release the supply-chain scan could only talk in the present tense: here is what auto-executes right now, here is a commit tip that looks forged. Useful if you happen to scan while the implant is sitting there. Useless for the two questions you actually have when a worm is circulating did something change, and what could whoever got in reach ... ... every scan records a fingerprint of what auto-executes in the repo

... doesn't accumulate GitHub only ever lets a called workflow reduce what it was 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

... gfazioli.github.io/octoscope/guide/ The octoscope guide Writing it was its own bug hunt. Plenty of what octoscope does was documented nowhere: the order it searches for your token and the scopes each kind needs, the work filters on the Repos tab, the full config key list with valid values, what the rate-limit chip is actually telling you. The home page got shorter in the same pass it had been re-explaining the tabs and drill-ins in duplicate ... ... drifted a version behind as a result. Then the release itself, which is about a smaller kind of honesty. Before it: a repo

... Continue button Hey vibe coders- I wanted to share how vibe code my roadmap when the project gets bigger and bigger and how I structured a loop behind it. Last month a week-long feature landed in my repo and I was barely in the room for it. I wrote the paragraph that started it. Then I tapped a button a few times over three days once at dinner, once from my phone, once from bed and the whole thing ... ... agent that exercised the story like a user. The only question left is  "does this user story work"   which was always the one that's mine. The unglamorous specs that make it survive a real repo

... been following along and would like to support us we would appreciate a star of GitHub: https://github.com/ota-run/ota A repo can look fine until it is run in a different environment. Native setup, Docker, CI, and remote execution often carry different assumptions, and most teams only discover the mismatch when something breaks. Ota makes those execution paths explicit so a repo

... thing I have noticed is that as my context gets richer, my repo is getting a bit wider, so I am worried context gets missed. I set up a nice folder system from the beginning and things structurally seem to be going well, but are there any helpful things you've personally done to keep the flow of context streamlined and guide the LLM to parse the repo

... what the actual job entails. Developers have noticed. Only 12% of developers use LinkedIn as their main source of technical information, according to a Stack Overflow survey. Most are on the platform purely because they feel they have no alternative, not because they find it genuinely useful. The Fake Everything Problem LinkedIn has a trust problem that is getting dramatically worse, not better. In the second half of 2024, LinkedIn identified and removed 80.6 million fake accounts at the point ... ... Working Against Developers Specifically Here is a problem that gets almost no attention but affects every developer on the platform. LinkedIn's algorithm penalizes external links. That means every time a developer does what comes naturally, sharing a GitHub repo

... been running Ota against real-world repos to see how it handles messy setup, drifted docs, hidden dependencies, and inconsistent run paths. If you want to see what Ota would surface in your repo

... built Ota after years of watching the same thing happen: you clone a repo, follow the README, and hit a wall because the project s actual setup changed, while docs and run paths drifted out of sync. I wanted a reliable way to make the ready-to-run and safe state explicit, not tribal, using an execution contract in `ota.yaml` that humans, CI, and AI agents can use. So if you want to ask about how Ota works under ... ... hood, how execution contracts are structured, onboarding pain, or where we re taking governed repo

... Quick backstory on the "why": octoscope's repo drill-in shows a 12-month star-history sparkline, and that reads GitHub's stargazers endpoint which GitHub has been tightening (a scoped token is now required) and which throws the odd 5xx. The catch: one failed star-history call used to abort the whole detail view. Not great. Now it's best-effort. If star history can't load, octoscope just drops the sparkline and still shows the description, license, latest ... ... public number, not the restricted list. This build also picks up a Go standard-library security fix (crypto/tls, GO-2026-5856), so it's worth grabbing even if you never open a drill-in. Tip: press Enter on any Repos

... octoscope v0.23.0 Polish & reliability octoscope is a terminal dashboard for your GitHub profile, repos, PRs, issues, activity, all in one TUI. This release is a polish & reliability round: Auth errors now name the fix. An expired or revoked token says so and points at the regenerate URL if it came from $GITHUB_TOKEN, or gh auth refresh if it came from the gh CLI. Under-scoped tokens name the exact scopes GitHub asked for. Watched entries never vanish ... ... silently. A watch_repos

... been following along and want to support us, we d really appreciate a GitHub star: https://github.com/ota-run/ota A lot of setup pain does not come from one repo. It comes from the space between repos

... viewers, so why do developers insist on including it in their resumes. I believe its because developers take pride in their craft and to be introduced by thier work. Yet somehow developers' best work is hidden inside private repos: the side project that might have commercial potential, that company work that can't be open source, clients and consultancy work that's covered under NDA. If you are hiring developers based on thier github profile, you are optimising ...

... code works. It's what not to do. Don't delete that database. Don't run that script in production. Don't edit generated files. Don't skip the setup checks. Don't assume the repo is ready just because it cloned successfully. Today's agents are getting better at understanding code. The harder problem is helping them understand how a repository is supposed to be operated. That's what we're building with Ota: a machine-readable execution contract ... ... that tells humans, CI, and AI agents the same story about how a repo

... couple releases ( 1.6.1 + 1.6.2 ) are mostly about project hibernation - archiving dead side projects off your SSD instead of keeping 30 GB on disk because "setting it back up later is annoying." The problem I was solving I keep old repos around for bad reasons. Source is small; dependencies and Docker runtime aren't . A docker-compose folder might be 200 MB of YAML and 8 GB of Postgres + custom images. Zipping the repo

... close to home. I've had this exact conversation multiple times. AI Memory is a topic that people get instantly. There are many people who have open-sourced basic AI memory layers and published their own GitHub repos. But when someone discovers all these options, they get excited, then realize the "setup" involves cloning a GitHub repo

... number of cool AI tools on GitHub is essentially infinite. The time to try them isn't. Every interesting repo charges what I'd call a curiosity tax : 30-90 minutes of cloning, installing, fixing dependencies, and hitting a CUDA error before you can even find out whether the tool is worth your attention. The cost isn't in skill. It's in hours spent on setup. And hours are exactly what a lot of us don't have ... ... most of the interesting tools in AI quietly go untried. Today we closed that gap. GitHub repo

... assume. Everyone who completed a course built a to-do app. It signals I completed a tutorial, not I can solve real problems. 84% of employers want to see working applications, not just code repositories. The distinction matters. A repo is a codebase. A working application is proof that you can take something from code to deployed reality, handle real-world edge cases, think about users, and finish things. The shift is simple in theory and harder in practice: stop ... ... building, link to your work. It takes two hours to set up and pays dividends every time someone lands on your profile. Pinned repositories. You get six. Use them for your best work, not your most recent. Each pinned repo

... been following along and want to support us, we d really appreciate a GitHub star: https://github.com/ota-run/ota A repo reaching a working state once is useful. But the real value comes when that working state can be repeated by the next person, on the next machine, or in the next automation run. That is where many repos

... make this thread useful for everyone. Drop the GitHub repos you found and actually use. Tools, models, scripts, weird side-projects. Anything you'd recommend to someone curious but short on time. One link + one sentence on why it's worth knowing about. That's it. Goal: turn this thread into the most-valuable bookmarked list of GitHub repos

... octoscope's Repos tab has had pinned repos

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

... agents are becoming part of everyday development, but most repos still don t have a clear way to tell an agent what is safe to run, what needs to be checked first, or which commands are actually trusted. That gap is what we re thinking about with Ota: making repo