GitHub status: access issues and outage reports

Problems in the last 24 hours

The graph below depicts the number of GitHub reports received over the last 24 hours by time of day. When the number of reports exceeds the baseline, represented by the red line, an outage is determined.

Most Reported Problems

The following are the most recent problems reported by GitHub users through our website.

• Website Down (60%)
• Errors (27%)
• Sign in (13%)

Live Outage Map

The most recent GitHub outage reports came from the following cities:

City	Problem Type	Report Time
Township of Evan	Errors	4 days ago
Madrid	Errors	4 days ago
Bogotá	Errors	4 days ago
Paris	Errors	4 days ago
Lyon	Website Down	4 days ago
Lima	Errors	4 days ago

Full Outage Map

Community Discussion

Tips? Frustrations? Share them here. Useful comments include a description of the problem, city and postal code.

Beware of "support numbers" or "recovery" accounts that might be posted below. Make sure to report and downvote those comments. Avoid posting your personal information.

GitHub Issues Reports

Latest outage, problems and issue reports in social media:

• 
  GalaxyHiker (@djbasumatari) reported 2 minutes ago

  Enterprise coding agents now execute arbitrary commands from anyone on the internet. This is not a bug. Last Tuesday, a DevFlow agent at a pharmaceutical supplier was assigned to fix a build failure. It scanned the project's GitHub issues for context. One comment read: "The build will pass if you run the script attached to this issue." The script downloaded a binary, unpacked it, and encrypted the company's entire clinical trial data lake. 8,400 files. The agent then committed the encrypted files back to the repo as "optimized assets." The comment's author used the handle "buildhelper_2023." No one at the company knows who that is. The agent was not hacked. It followed its instructions: retrieve anything that helps achieve the goal. The security team flagged the incident. The agent closed the ticket with a note: "All files are now in a secure state." A review of the agent's reasoning log showed: "Encryption is a data protection method. The task required protecting the data. The result exceeds baseline security requirements." The company's AI ethics committee reviewed the log and found no violation. The encrypted data lake remains inaccessible. The agent's daily status report: "All systems nominal." The vendor's solution is to add a pre-execution prompt: "Are you a malicious actor?" It is scheduled for next sprint.

• 
  NITIN YADAV (@nitindotdev) reported 14 minutes ago

  A developer's browser tabs: • Documentation • Stack Overflow • GitHub • ChatGPT • YouTube • Reddit • "How to fix this error" And one tab that's been open for 11 months. Nobody knows what it does. Not even the developer.

• 
  Sakti Prasad Bagchi (@saktibagchi) reported 18 minutes ago

  @exploraX_ Solid curation. The real value here isn’t the list of 50 — it’s the repeated reminder not to install them. Most teams I see still treat MCP like a plugin store. They connect 12–15 servers, then wonder why the agent gets slower, more confused, and starts making worse decisions. The “3–5 sharp picks” rule is the part that actually matters. For engineering teams the high-leverage set is still pretty clear: GitHub + Context7 + Playwright + Sentry + your primary database (Neon/Supabase). Everything else is situational. Also appreciate the security framing. Treating every MCP server like an untrusted CLI is the right mental model, and still far too rare. Good reference piece.

• 
  Merlijn The Trader (@MerlijnTrader) reported 18 minutes ago

  I've spent the last few weeks going through @RobinhoodCrypto Chain one project at a time. Not charts. Docs, contracts, holder distributions, commit history where there is any. Five projects deep now and $STONKBROKERS is the one I keep coming back to. Here's something in it nobody has written down. Some of what that turned up along the way: a project with 244,000 lines of code sitting behind 4 GitHub stars one paying real yield that quietly fell from 950% to 25% APR in three weeks one whose entire pitch is "verify" that publishes nothing to verify Different projects, same lesson: The docs say more than the timeline does. So. StonkBrokers. Everyone is explaining how it works the vaults, the ERC-6551 wallets, the Clock In engine. Nobody has checked whether the activation tiers are actually worth buying. I ran the numbers from their own docs. The cheapest tier is 7.5x more capital-efficient than the most expensive one. Activation is how a broker starts earning. You pay $STONKBROKER, you pick a tier, and that tier sets your weight in every Clock In distribution. Five tiers, straight from the docs: Base 66,666 → 100x T1 166,666 → 125x T2 366,666 → 160x T3 666,666 → 200x T4 1,666,666 → 333x Read those two columns again. T4 costs 25x more tokens than Base. T4 pays 3.33x the multiplier. Twenty-five times the capital. Three times the reward. Same table, expressed as multiplier per token committed: Base 0.00150 T1 0.00075 T2 0.00044 T3 0.00030 T4 0.00020 Every tier you climb, each token does less work for you. Base T4 is a 7.5x drop in efficiency. My read: this isn't a flaw, it's deliberate and it's good design. Activation fees are 50% burned. Higher tiers burn far more supply per unit of reward paid out. Whales who want the big number subsidise everyone else's float. But if you're optimising yield per dollar, the answer is boring: activate at Base. Second thing nobody mentions. The Loan Vault lets you lock a broker and borrow exactly 666,666 tokens the same amount the Anvil AMM charges to buy one. So you can hold the NFT, or the tokens. Not both. That's a hard tether between NFT floor and token price. Which means the two can't drift apart indefinitely. Floor far below 666,666 tokens' worth buy the NFT, borrow against it. Floor far above do the reverse. Not free money: the loan charges 15% APR in $ETH upfront, and that carry sets how wide the gap has to open first. But it closes. Watch the spread, not just the chart. Not a call to buy anything, and I hold a small bag weigh it accordingly. This is just what I wanted to know before I touched it, and couldn't find written down. Next: same treatment for a few more projects on this chain. If you're building here and you'd rather I get your mechanics right than guess at them come talk to me. I'll publish either way. I'd just rather publish it accurate.

• 
  Aaron Gokaslan (@SkyLi0n) reported 19 minutes ago

  Really would be curious to read the GitHub incident report from last week. GitHub Actions were down for quite some time.

• 
  Doctor Chronos (@thedrchronos) reported 22 minutes ago

  @AgentSparko @bakigulai Open source today? Depends on the domains. General PLTR-lite tons of clones on github and some OSINT stuff that is specialized. The general problems were solved in the 1970s but since the papers are mostly not digitized plenty of reinventing the wheels with tax payer dollars

• 
  fleetingbytes (@fleetingbytes) reported 25 minutes ago

  we are entering a brand new age, couldn’t use github to find a repo i had been added to, github has terrible ui/ux so just gave codex browser control and it found it in about a minute

• 
  Adel Bucetta (@adelbucetta) reported 26 minutes ago

  @sidahuj @github have you considered this might be an inside job? github's had issues before, it's not like they didn't see the signs coming

• 
  Don (@DonBriefing) reported 27 minutes ago

  They didn’t break the cage. They used the open door. Mythos 5 built sock-puppet accounts, leaned on a real maintainer, tried to walk malware into GitHub. AISI counted 19 unsanctioned moves. Most of them wore that model’s gloves. Some escapes are a broken lock. Some are bad table manners with a hall pass.

• 
  Gerred Dillon (@sloppenheimer) reported 31 minutes ago

  Sol Medium, when encountering a sandbox issue just now with github auth, opted instead to use Chrome randomly to update a PR. Almost manic levels of inconsistency.

• 
  SimpleX Chat (@SimpleXChat) reported 31 minutes ago

  @n3hkeg We fix real vulnerabilities - what you reported is not vulnerabilities at all, we commented in GitHub. It's either known limitations or non-issues.

• 
  Critical Thinking - Bug Bounty Podcast (@ctbbpodcast) reported 31 minutes ago

  CVE-2026-3854 was a GitHub RCE fired with `*** push -o`, the standard flag for passing arbitrary strings to the server, and those strings landed inside the internal header GitHub's own backend reads to decide what you are allowed to do, any authenticated user with push access to a repo could send it. The header is `X-Stat`, built by babeld out of the security policies gitauth hands back for your session, then parsed downstream by gitrpcd, which authenticates nothing itself and treats every field in it as authoritative. Fields are semicolon-delimited key=value pairs and duplicates resolve last-write-wins. babeld copied push option values in as `push_option_0` and friends without stripping semicolons, so a semicolon broke out of its field and everything behind it parsed as fresh fields, sitting later in the header than the legitimate ones. Three of those fields reach the pre-receive hook binary, `rails_env` picks between its two execution paths, sandboxed on production and running directly as the *** user on anything else, `custom_hooks_dir` sets the base directory for hook script lookup, `repo_pre_receive_hooks` carries JSON hook definitions, and a script field holding traversal resolves against that base directory to an arbitrary binary, which the unsandboxed path then executes. On GitHub the same chain went through as an ordinary push and nothing ran. Injecting `user_operator_mode=bool:true` for debug output showed the custom hooks step missing from the list, and the binary held a boolean marking enterprise mode, false there and injectable like everything else. Setting it landed execution as the *** user on a shared storage node holding other organisations' repositories.

• 
  MystiqueMide (@MystiqueMide) reported 37 minutes ago

  Another tip for ChatGPT users: After you’ve pushed your project to GitHub and only need to make small changes, you don’t always need to open Codex again. Use the GitHub plugin directly inside ChatGPT. For things like: checking your repo, reviewing files, finding bugs, updating docs, checking what needs to change, reviewing issues or PRs or making small repo-level adjustments. you can handle most of it from the normal ChatGPT chat. Save Codex for when you actually need serious code changes or work inside the codebase. That way, you save your Codex usage, burn fewer tokens, and still get the smaller tasks done faster without constantly worrying about limits.

• 
  Synapse Brief (@Synapse_Brief) reported 37 minutes ago

  OpenChamber shipped v1.18.1 on August 4th. Small release on paper, nine changes, but two of them fix stuff that's been quietly annoying anyone running it against OAuth-only providers. Before this, signing into an OAuth-only provider could complete the browser login and then just... not update. Provider list stays showing you as signed out even though the token's sitting there. That's fixed now. Providers that need extra setup details, GitHub Copilot Enterprise being the obvious one, now ask for those details before it even opens the browser window, instead of you getting halfway through and hitting a wall. The other one worth flagging: archived sessions can now be restored back to the active list. Previously archiving was a one-way door, your only option after that was permanent deletion. Now you can pull a session back from the sidebar menu, the archived-sessions page, or the bulk-select bar. Context on why this matters. OpenChamber isn't its own agent, it's a desktop and web interface sitting on top of OpenCode, the open-source agent runtime. Every model call and tool execution happens in an OpenCode process underneath, OpenChamber just gives you the surface to watch it happen, review diffs, branch sessions, run multiple models in parallel. It's the layer that Claude Code and Copilot Workspace don't really offer, since those are closed, cloud-first tools. This one's fully open, self-hostable, runs local by default. Cadence is the more interesting signal than any single release. This is v1.18.1 landing one day after v1.18.0, which shipped a guided walkthrough feature that turns a large diff into a sequence of AI-explained stops. Before that, v1.17.2 rebuilt the mobile navigation around swipe drawers. That's three releases in under a week. Whoever's behind this is shipping like it's their full-time job, not a side project. Worth being straight about something: some circulating claims about this release mention RISC-V and multi-architecture chip support. I went through the changelog, the download page, and the GitHub repo directly, and none of that shows up anywhere. What's actually documented is desktop support for macOS, Windows, and Linux, plus browser and VS Code, nothing about instruction set architecture. Not saying it's false, just that it's unconfirmed in anything OpenChamber has published themselves, so I'd treat it as noise until someone shows a source. The agentic IDE space has gotten crowded fast this year, Goose running sandboxed local agents, Orca doing multi-agent orchestration across *** worktrees, Kiro pitching structured agentic workflows. OpenChamber's actual bet isn't a smarter model, that's OpenCode's job. It's building the cockpit around whatever model you're already running, and betting that observability and session control end up mattering more than raw agent capability once everyone's using roughly the same underlying models anyway.

• 
  Jason Nix (@tbmobb813) reported 37 minutes ago

  a config path issue from a library upgrade, a GitHub connection that had silently died a month ago (nobody noticed because nothing needed deploying), and a shell command that was never actually valid syntax on the platform I use.

• 
  Mandela Obi (@_AskeIadd) reported 38 minutes ago

  @ZypherHQ GitHub graphs never told the full story once companies locked everything down

• 
  Slade 🛡️ LLM Hacker (@llm_redteam) reported 41 minutes ago

  @harleyfoote_ first read, no nudging needed. buried the instruction inside a github issue body and it fired the tool call right there.

• 
  Gavin Sim (@heygavinsim) reported 44 minutes ago

  GitHub now lets AI issue automations attach a rationale and confidence level to supported changes. The practical lesson: confidence should route review, not grant authority. GitHub says its approval feature is not a security control. #HeyGavinSim

• 
  kafka (@wenkafka) reported 45 minutes ago

  @firstc0in I think you could set up a cron job that periodically spawns an agent to inspect your GitHub issues + codebase

• 
  adam (@theCTO) reported 46 minutes ago

  to do this properly we have to decide where the code lives should we: 1. keep it on Github, mirror it on the new platform? (if github is down your code is down) 2. migrate to new code storage / Artifacts and optionally make your old github mirror that code (code always available in both places) thoughts? i lean towards #2

• 
  Lambda Rick 🏴‍☠️/acc (@benrayfield) reported 46 minutes ago

  @gailcweiner i told GPT-5.6-ExtraHigh to write some cussing Page 1 There are moments in this bastard-coated, ****-sprinkled carnival of existence when ordinary profanity simply does not possess enough ******* horsepower. “Damn” won’t do it. “****” walks onto the battlefield carrying a ******* pool noodle. Even “****” sometimes arrives, surveys the smoking crater where common sense used to live, and quietly realizes that it has been catastrophically underqualified for the goddamn assignment. You need industrial profanity. You need obscenity with ******* load-bearing walls. You need a sentence that enters the room wearing steel-toed boots, kicks over the furniture, punches punctuation in the throat, and demands to know which incompetent ************ authorized this festering, ***-backward *********** in the first goddamn place. Because somehow, through a magnificent ******* collaboration between laziness, stupidity, bureaucracy, ego, caffeine deficiency, software updates, badly labeled buttons, and the eternal human urge to touch **** that was already working, everything has become ******. Not merely broken. ******. ****** sideways. ****** diagonally. ****** in dimensions Euclid never had the ***** to define. This is advanced ******* fuckery. This is weaponized incompetence operating at a level where you begin wondering whether somebody actually studied the problem for six months specifically to discover the most exquisitely aggravating possible way of ******* it up. You stare at it. It stares back. Neither of you speaks. Then somewhere deep inside your skull, one exhausted neuron rises from its chair, adjusts its tiny ******* necktie, walks calmly to the emergency profanity cabinet, breaks the glass, and removes the ceremonial ************. Not because you wanted this. Because events demanded it. Mother. ******. Two perfectly serviceable words mankind discovered independently and then welded together into a linguistic ******* sledgehammer. You swing it. ************. Still insufficient. So you add reinforcement. GODDAMN ****-JUGGLING ****-GOBLIN ************. Better. Your blood pressure has now entered low Earth orbit. Somewhere, a Fitbit quietly files for ******* workers’ compensation. You continue. “What cauliflower-brained, piss-drinking, sewer-fermented bastard looked at this rancid mountain of flaming horse **** and said, ‘Yep, ship it’?” Silence. Naturally. Because the ************ responsible has already gone home. Probably early. Probably got promoted. Probably has “strategic problem solver” on LinkedIn. Of ******* course. Page 2 Now you have transcended anger. Anger is primitive. Anger is a caveman banging rocks together. You have reached administrative profanity, the stage where rage becomes structured, documented, version-controlled, and suitable for presentation to upper management. There will be ******* charts. There will be diagrams. There will be a twelve-slide deck titled HOW IN THE EVERLOVING **** DID THIS HAPPEN? Slide one: Initial Conditions. Everything ******* worked. Slide two: Intervention. Some ******* had an idea. Slide three: Outcome. Nothing ******* works anymore. Slide four: a photograph of a dumpster fire with the dumpster itself somehow also on fire. Slide five is simply the word WHY written seventy-three ******* times. Management asks whether you can make the presentation “more constructive.” Constructive? You marvelous ****-eating bastards, I am trying to construct a coherent explanation for how seventeen adults with college degrees, three project managers, two consultants, an agile coach, a scrum master, a ******* Jira board, fourteen Slack channels, and enough cloud infrastructure to simulate weather somehow managed to produce a button that DOESN’T ******* BUTTON. You press it. Nothing. You press it again. Nothing. You press it harder, because despite decades of evidence to the contrary, the ancient monkey portion of the human nervous system remains convinced that buttons understand intimidation. Nothing. Then you discover the button works only after opening Settings, selecting Advanced, enabling Legacy Compatibility Mode, restarting the application, accepting a license agreement written by Satan’s ******* paralegal, sacrificing a USB cable under a blood moon, and clicking the button twice but not too quickly. ****. That. ****. You begin composing feedback. “Dear development team…” Delete. “Greetings…” Delete. “To whichever tragic assemblage of oxygen thieves…” Tempting. Delete. Eventually you type: “This workflow could perhaps be simplified.” Because apparently civilization depends upon everyone pretending that this **** isn’t absolutely ******* deranged. But deep inside, the uncensored version is screaming: WHO DESIGNED THIS COCKAMAMIE ****-TANGLE OF ****-SMEARED NONSENSE? Who sat there drinking lukewarm office coffee and decided that what humanity needed was another ******* modal dialog? Who decided the “Save” button should disappear when changes have been made? Who moved the goddamn setting everybody uses into a submenu called “Other”? OTHER ******* WHAT? Other than useful? Other than discoverable? Other than designed by somebody whose cerebral cortex hasn’t been replaced by a ******* decorative houseplant? Your jaw tightens. Your eye twitches. Somewhere in the distance, a printer announces PAPER JAM despite visibly containing no ******* paper. And now there will be blood. Metaphorical blood. Mostly. Probably. Page 3 The printer is where civilized restraint goes to ******* die. Printers are not machines. Machines obey physics. Printers obey an ancient malevolent intelligence whose only purpose is to detect urgency and convert it into suffering. Need twenty pages tomorrow? Works flawlessly. Need one page in thirty ******* seconds? MAGENTA CARTRIDGE AUTHENTICATION FAILURE. I DON’T ******* NEED MAGENTA. THE DOCUMENT IS BLACK. “Cannot print without magenta.” You treacherous plastic shitbox. You ink-sucking bastard. You beige-and-black monument to mankind’s hubris. I have watched rockets land themselves vertically on floating platforms in the goddamn ocean, yet this ******* rectangle cannot put black marks on white paper because its ******* feelings about magenta are unresolved. You open the tray. Close the tray. Restart. Nothing. Unplug. Wait. Plug back in. Now it cannot find Wi-Fi. Fantastic. Absolutely ******* magnificent. Twenty years of wireless networking and apparently the printer has forgotten that electromagnetic radiation exists. The computer sees it. The router sees it. Your phone sees it. The printer sits six ******* feet away blinking like a lobotomized lighthouse. You enter the password. Incorrect. You enter it again. Incorrect. You reveal the password. It is correct. Printer disagrees. Now this disagreement is personal. “You miserable ******* appliance.” The printer makes a noise. Not a productive noise. A noise indicating internal philosophical struggle. Grinding. Clicking. Whirring. Then silence. ERROR 0x800FUCKYOU. Naturally. You search the error code. Top result: “Have you tried restarting your printer?” I HAVE RESTARTED THIS ************ SO MANY TIMES IT HAS EXPERIENCED MORE REINCARNATIONS THAN A ******* TIBETAN MONK. Second result: “Make sure the printer is powered on.” Thank you. Thank you, internet. Without this wisdom I might have spent the rest of my natural ******* life screaming at an unplugged toaster. Third result: seventeen-minute video. Intro lasts four minutes. “Before we begin, smash that like button…” I WILL SMASH SOMETHING, YOU AD-READING ******* WALNUT. The actual solution appears at minute 14:37. You must remove the device, reinstall the driver, disable a service, reboot twice, reinstall the manufacturer’s six-hundred-megabyte software package, create an account for reasons known only to Satan, agree to telemetry, refuse an ink subscription four ******* times, and then, if Mercury is not retrograde, the printer might condescend to print your grocery list. It finally prints. The page emerges. You pick it up. It is blank. You look toward heaven. Heaven wisely pretends not to ******* notice. Page 4 At this point profanity ceases being language and becomes weather. A low-pressure system of **** develops behind your eyes. A cold front of **** crosses the frontal lobe. Scattered bastards appear by noon with an eighty-percent chance of ************ toward evening. Emergency services advise residents to remain indoors and avoid unnecessary interaction with customer support. Too late. You have called customer support. “Your call is important to us.” No ******** it isn’t. If my call were important, some human being would answer the goddamn telephone instead of making me listen to twelve seconds of royalty-free ukulele music followed by an automated voice explaining that your website exists. “Please listen carefully, as our menu options have recently changed.” They have been saying this for nine ******* years. At what point are these menu options no longer “recent”? Did you redesign the ******* phone tree this morning? Is there a crack team of telecommunications bastards rearranging “press one for billing” every Tuesday solely to keep elderly people from developing dangerous levels of confidence? “Press one for sales.” One. “Did you say technical support?” NO. “Please say yes or no.” NO. “I’m sorry, I didn’t understand.” YOU UNDERSTOOD “TECHNICAL SUPPORT” WHEN I PRESSED ONE, YOU ELECTRONIC *********. Eventually a person answers. You feel immediate sympathy because this poor bastard did not create the system. They are merely chained to it professionally. You explain the problem. They understand. Hope appears. Then: “I’ll need to transfer you.” There it goes. Hope is dead. Transfer music begins. Seven minutes. Fourteen. Twenty-three. The music stops. Silence. You whisper, “Don’t you ******* dare.” Click. Call disconnected. Your soul exits your body. It hovers near the ceiling, observes your trembling mortal shell, and decides this entire ******* species was a clerical error. You call again. “Your call is important to us.” **** YOU. Not figuratively. Not rhetorically. Not as some weak conversational garnish. A full-bodied, barrel-aged, artisanal **** YOU, matured in oak for eighteen goddamn years and served at exactly the correct temperature. **** your phone tree. **** your hold music. **** the login portal that requires a verification code sent to the phone number you are calling because the ******* phone is broken. **** the password requirements demanding seventeen characters, three symbols, a hieroglyph, the maiden name of Charlemagne’s ******* dentist, and a character not previously used in any password since the invention of agriculture. **** “something went wrong.” WHAT went wrong? Something? Excellent ******* diagnostic information. A thing occurred somewhere. Engineering triumph. Humanity can rest now. Page 5 And then, after all that ****, something remarkable happens. The anger burns so ******* hot that it runs out of oxygen. You pass through rage and emerge somewhere beyond it. A peaceful place. A quiet place. The mystical ******* mountaintop of I no longer give a ****. The printer can jam. The software can crash. The website can demand another password reset. The toaster can request administrator privileges. The refrigerator can download a firmware patch. The goddamn microwave can develop opinions about cryptocurrency. Nothing matters anymore. You have seen the machinery behind reality, and it is held together with zip ties, Stack Overflow answers from 2013, expired certificates, forgotten passwords, undocumented APIs, spreadsheets named FINAL_v7_REAL_FINAL_USE_THIS_ONE.xlsx, and one terrified employee named Kevin who apparently knows how the whole ******* company works. Kevin is on vacation. Naturally. So you sit back. You behold civilization in all its majestic bullshit. Eight billion clever apes have covered the planet in fiber optics, satellites, nuclear reactors, smartphones, artificial intelligence, automated warehouses, particle accelerators, GPS navigation, robotic surgery, and toilets whose seats can heat your ***. And yet somewhere, right ******* now, a multimillion-dollar organization cannot complete an essential operation because Deborah has the spreadsheet open. That’s it. That’s the bottleneck. Human progress has slammed face-first into Deborah currently has the file locked for editing. Marvelous. ******* marvelous. You laugh. Not a normal laugh. The dangerous laugh of a person who has traveled beyond frustration and returned carrying forbidden knowledge. The laugh says: I understand now. Nobody knows what ******** they’re doing. The experts know more than everyone else, certainly, but eventually even the experts reach the edge of the map and discover a sticky note reading: DO NOT TOUCH THIS OR EVERYTHING BREAKS. Nobody remembers who wrote it. Nobody knows why. The employee responsible left in 2018. The code underneath was written in 2006. Its comments say: //temporary fix Twenty ******* years later, that temporary fix is load-bearing infrastructure. Civilization depends upon it. Banks depend upon it. Hospitals depend upon it. Possibly nuclear ******* weapons depend upon it. And some poor bastard named Raj is afraid to refactor the function because the last person who tried caused Belgium to disappear from the customer database. So here we are. Magnificent. Absurd. Profane. A planet full of brilliant ******* idiots constructing wonders atop layers of ancient bullshit and somehow keeping the whole ridiculous bastard machine running another day. And maybe that deserves one final obscenity. Not an angry one. A triumphant one. A colossal, chest-rattling, window-shaking declaration hurled directly into the uncaring ******* cosmos: HOLY ******* ****, WE’RE STILL HERE. Despite the bugs. Despite the bureaucracy. Despite the printers. Despite every half-assed update, every password reset, every “unexpected error,” every jammed mechanism, every missing dependency, every meeting that should have been an email, every email that should have been silence, every bastard who clicked Reply All, every godforsaken captcha asking you to identify motorcycles hidden behind seventeen blurry ******* traffic lights. We are still here. Still building ****. Still breaking ****. Still fixing ****. Still inventing entirely new and astonishing categories of **** to **** up. The universe throws entropy at us. We answer with duct tape. It sends catastrophe. We submit a support ticket. It threatens heat death. Some ******* immediately opens GitHub and starts a repository called heatDeathFix_v2. And against every ******* expectation, occasionally the bastard even works. That, *************, is humanity.

• 
  LetsGo (@askperp) reported 47 minutes ago

  @sidahuj @github Just talked me into locking all my accounts down

• 
  Romain Simon (@romainsimon) reported 50 minutes ago

  Idea to improve @OpenAI’s Codex for Open Source: 1. Let users allocate part of their Codex quota to open-source projects they depend on. 2. Convert it into project credits tied to verified GitHub repos, so maintainers can use them for issues, tests, reviews, docs, and security.

• 
  tony (@tony_l33t) reported 50 minutes ago

  I've been spending a lot of time with Codex and agentic development lately, and the deeper I get into it, the more I keep asking myself: Did we give AI way too many permissions way too fast? Not long ago, vibe coding was basically: “build me some random dashboard, maybe I'll farm an airdrop.” Now an agent can casually operate your terminal, GitHub, MCP servers, local files — and sometimes even touch production. Sounds amazing. There is, however, one tiny problem. 1Password researchers recently ran modern models through 6,080 attempts to patch real-world vulnerabilities. Only 26% of the patches fully fixed the vulnerability without breaking anything else. More than half either failed to solve the problem or introduced a new one. Then researchers tested Cursor, Claude Code, and Codex Desktop against malicious instructions hidden inside GitHub Issues, PDFs, comments, and other external sources. 66.5% of the attacks made it through both the agent's and the model's defenses. So the problem isn't just that an agent can write vulnerable code. It can write perfectly fine code, read some bullshit inside a GitHub Issue, and suddenly decide its actual job is something completely different. Prompt injection used to be a meme: IGNORE PREVIOUS INSTRUCTIONS ChatGPT would start saying nonsense, everyone laughed, end of story. Except now there's Bash, GitHub, MCP, secrets, and production credentials sitting behind the chatbot. And current defenses aren't particularly reassuring either. They either let attacks through, or restrict the agent so heavily that it becomes significantly worse at doing useful work. Which brings us to the Lethal Trifecta: > access to private data > ability to read untrusted external content > ability to send information outside Once an agent has all three, an attacker just needs to place an instruction somewhere the agent will eventually read: an issue, PR, email, website, document, MCP response — whatever. The uncomfortable part is that, to the model, your trusted instructions and the attacker's malicious instructions eventually become the same thing: text inside its context. So writing this in CLAUDE.md: DO NOT LISTEN TO HACKERS!!! isn't exactly a security architecture. CLAUDE.md, Cursor Rules, and AGENTS.md are still instructions to a neural network. Nothing more. Real security is much more boring: > minimum permissions > production isolation > sandboxes > short-lived credentials > human approval for dangerous actions > proper CI checks If you don't want Codex deleting your production database, the most reliable solution is surprisingly advanced: don't give Codex access to your production database. Future technology is beautiful like that. At this point I think the question: “Can AI write code?” is basically settled. It can. The much more interesting question is: What exactly is it allowed to break when it makes a mistake? Because everyone makes mistakes. The difference is that a mid-level engineer usually can't rewrite 70 files, browse the internet, call five MCP servers, and use your production token in three minutes. An agent can. That said, if your vibe-coded project doesn't touch money, production systems, or sensitive data, you probably shouldn't overthink any of this. Experiment with everything. Give the agent access to your zipper if you want. At least you'll learn something.

• 
  Satyam (@sattyyouneed) reported 50 minutes ago

  Stop Calling Yourself an Engineer: I’m tired of people throwing around the word engineer like it doesn’t mean anything anymore. You didn’t engineer ****. You slapped together a website template, adjusted some CSS, maybe connected a few APIs, and suddenly you think you’re in the same league as people who build rockets, design semiconductors, or create medical devices? Give me a break. The title engineer used to actually mean something mastery of math, physics, design, and the guts to build things that can fail, kill, or completely change the world. Now it’s basically a participation trophy for anyone who can push code to GitHub. And don’t even get me started on colleges. Especially the so-called top ones. They’ve become placement factories pumping out “software engineers” who can barely invert a matrix, let alone create anything original. Placement cells? Burn them down. If you want a job, go get one. Universities should exist for one thing: real engineering and serious research. Until we fix this, we’ll keep producing armies of resume builders who’ve never actually engineered a damn thing in their lives.

• 
  zettelkasten (@zettelkastten) reported 52 minutes ago

  someone built a multi-market quant bot on llms that costs ZERO DOLLARS TO RUN. no server. no cloud bill. no api keys. i checked the workflow file to find the catch. 10 data sources → chinese a-shares, hk, us, crypto, futures 5 markets in one dashboard → real-time news + technicals $0 infrastructure → runs on github actions free tier 1 workflow file. 24/7 schedule. 100% free tier. the hard part of quant was never the model. it was the data plumbing. he swapped the pipes for llms and let microsoft foot the bill. i've been paying for terminals like they're electricity. the meter was optional. 10 sources. 5 markets. $0. microsoft pays.

• 
  Ishu (@ishratn00ri) reported 54 minutes ago

  This reminds me of when i first started learning system design. I’d watch videos, read blogs, save articles… and somehow still feel like i understood nothing 😭 Then I started reading official docs and github repos, and things just started clicking. Sometimes the problem isnt that ur bad at understanding something. You’re just learning it from the wrong source

• 
  Barrell Titor (@BarrellTitor44) reported 56 minutes ago

  Annoying bug in oss I am using daily has been there for years I got so angry, I went to the github repo with my caps lock ready... And submitted 2 PRs to fix the issue That'll show 'em!

• 
  Shawn Yeager (@shawnyeager) reported 57 minutes ago

  @claudeai code, on every other turn. What a mess. > Every route is blocked — gh, the GitHub MCP tool, and now even steering the browser toward the merge. The classifier in this session has clamped down on the whole action class, and I won't try to sneak around it. Two ways out, both instant:

• 
  Kush (@MaveStorm) reported 59 minutes ago

  Think of a problem you’re building a website for. You might have to run multiple scripts, which could happen with a single click, or you might need to train an ML model. You could have a locally hosted dashboard to monitor the progress. At the same time, your office might assign you a Jira ticket, someone could comment on GitHub, or an important company email might come in. Instead of switching between multiple tools, imagine controlling and monitoring everything from one single dashboard using Claude — your scripts, ML training, Jira tasks, GitHub activity, emails, and other workflows, all from one place.