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 (69%)
• Sign in (19%)
• Errors (13%)

Live Outage Map

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

City	Problem Type	Report Time
Paris	Website Down	23 hours ago
Saint-Paul	Website Down	2 days ago
Saint-Paul	Website Down	2 days ago
Mexico City	Sign in	3 days ago
León de los Aldama	Website Down	3 days ago
Créteil	Website Down	26 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:

• 
  JurixAI (@JurixAI_) reported 4 minutes ago

  We've officially registered JuriXAI Auditor as an ASP on the @XLayerOfficial AI Marketplace and we are now awaiting listing approval. The initial automated checks have already returned a PASS. JuriXAI brings automated, micro-payment-powered smart contract and GitHub repository auditing to the X Layer Mainnet. No more slow manual reviews. No more biased judging. Just fast, objective, and on-chain auditing. Here's how we are changing developer audits 👇

• 
  adas🧦🌹 (@adastroworld) reported 6 minutes ago

  Codex is broken so I had to go to GitHub to get the actual install from a comment in an Issue Today separates the boys from men

• 
  Jason Fleagle (@jjfleagle) reported 6 minutes ago

  @pagerduty @github Putting incident context inside the PR is the kind of workflow detail that compounds. The fix is only half the work. The reviewer also needs incident state, likely blast radius, recent changes, and why this patch is the safest next move.

• 
  Kevin Whinnery (@kevinwhinnery) reported 6 minutes ago

  @threepointone This was after a configuration error on our Stainless SDK repos. Some Stainless customers were temporarily added as outside collaborators in Anthropic's GitHub enterprise. All resolved now and no data was exposed, details were emailed to affected customers 🙏

• 
  Keeta Github Tracker (@KeetaCode) reported 7 minutes ago

  🐆 Keeta GitHub PR Merged 📦 Repo: anchor-rs 🔀 PR #23: Fix: Naming Updates 🌿 Branch: fix/naming-updates → main 👤 Originally opened by: @sephynox 🧠 Overview: This PR updates internal naming so Keeta’s developer tools use clearer, more consistent labels, which should make them line up better with the TypeScript version and reduce confusion. In simple terms, some account-related names are being changed, and error messages for blocked asset transfers are being passed through more clearly instead of being turned into a generic failure. This appears to be a technical/internal update with limited public details. - Developers using these tools may need to update their integrations because some old names are being replaced. - Failed transfer attempts may now return more specific reasons, which could make troubleshooting easier.

• 
  CatDog (@kdoggo1181074) reported 10 minutes ago

  Some important @FireCashX transparency questions before mainnet, especially for Kaspa users interested in new Kaspa forks. I first heard several of these concerns from community members, then reviewed the public GitHub repositories, wallet documentation, commits, and issue history myself. I am not identifying or attributing the original Discord participants here; the points below are based on publicly verifiable sources. Kaspa community members should be cautious when a new project presents a fork as necessary for functionality that may ultimately be implementable directly on Kaspa or through Kaspa-based applications and protocol extensions. A fork creates a new trust surface: new maintainers, modified consensus code, new wallets, new pools, new infrastructure, and new tokenomics. That does not mean FireCash is destined to fail, or that every Kaspa fork is illegitimate. FireCash may still improve substantially, and open testing can expose problems before mainnet. But the burden should be on the project to explain clearly why a separate chain is required and to demonstrate that its changes are secure.

• 
  Scott | Free Speech Dev 🇺🇲 (@scottdotnetdev) reported 11 minutes ago

  @github support is absolute ****. I cannot believe they just won't even bother responding to billing issues, tf is wrong with them? Anyone have a better way to contact them? I'm a paying customer and they dgaf

• 
  prince. (@onrooleyy) reported 12 minutes ago

  @symplaxhq when i try to deploy a new application, it only shows public repos. and i used my github to sign in. i don't see any place to grant access to my private repos

• 
  Abhas Bhattacharya ⤵️ (@abhas_tweeter) reported 13 minutes ago

  @NoriSte @siddharthkp Great idea. I assume this repo is created intentionally for interviews? Or is it somehow derived from real Github codebase and old issues?

• 
  Alex Kim (@AlexKim) reported 13 minutes ago

  github issues are open or closed. linear has six workflow states. the whole migration is collapsing that difference into labels without the agent losing track of state.

• 
  Peyton Spencer (@peytonspencer) reported 13 minutes ago

  Task: triage open PRs in frontend and backend. determine merge priority and spin up a thread per PR or PR pair fe/be we'll go through this sequentially We have 4 staging backends you can deploy over github workflows: staging-5 through staging-8 You link the frontend PRs to the backend you want to test. Then you get the frontend preview URL and login with this test account: [test user credentials] What we can now do: you QA test 4 features in parallel using chrome that need even 4 backend changes Some of these are frontend only in which case you don't have to attach to a backend. Others will need backends In this first wave I want a minimum of 4 QA'd features with their preview URLs so i can do my second QA pass. merge ready, with the merge order you'd like. I'll then smoke, review, merge, and then you can start the next wave. I'll communicate in the dedicated threads, and we'll also orchestrate in this chat since you can send message to threads as well.

• 
  tux (@gitcommit90) reported 18 minutes ago

  Tencent Hy3: Apache 2.0 open weights, claims to match flagship models with 2-5x more parameters. Numbers from the blog: > hallucination rate 12.5% -> 5.4% > commonsense errors 25.4% -> 12.7% > tool-call scaffolding variance within 4% across CodeBuddy/Cline/KiloCode > ~47-49% fewer tokens vs GLM-5.2 on doc/presentation tasks WorkBuddy internal: task success 72% -> 90%, time -34%. API: 1 RMB/M input (about $0.14), 4 RMB/M output, 0.25 cached. HN thread has operators comparing it to DS4 Flash on DGX Spark. One says Hy3 stays on track better despite being slower. Nobody's posted local tok/s yet. Free on OpenRouter until July 21. Weights on GitHub and HuggingFace. I'll try it on the Spark before I trust the bench numbers.

• 
  Codebender Cate™ ξ(s)=1/2s(s-1)π^(-s/2)Γ(s/2)ζ(s) (@Codebender_Cate) reported 20 minutes ago

  I need resources to find a collection of GitHub Open source arcade and casino games that can be played in the browser. I need to make sure there's no issues with copyright infringement by using the source for these games. I need true open source. Any suggestions?

• 
  Hajime Hoshi (@hajimehoshi) reported 22 minutes ago

  @Piechutowski * GitHub Pages requires GitHub Actions YAML, which is difficult to test on local machines * GitHub Actions is sometimes down * Cloudflare Pages' loading speed is way much faster * Cloudflare Pages supports redirections

• 
  Tadeusz (@Tadeusz88674836) reported 23 minutes ago

  @merill Well not across projects. Projects usually i keep in Github Copilot and cowork. But as an it aarchitect i keep on describing back and forth architecture or given problems and solutions. For that i paste links and abstracts from those and/or i use copilot for that so it already knows most stuff from my emails, transcripts, or Teams.

• 
  Keeta Github Tracker (@KeetaCode) reported 24 minutes ago

  🐆 Keeta GitHub PR Opened 📦 Repo: anchor 🔀 PR #396: Cache resolveAsset calls to improve web performance 🌿 Branch: feature/fix-resolveassets-caching → main 👤 Opened by: @ezraripps 🧠 Overview: This update makes Keeta’s web experience faster by storing repeated asset lookups instead of rebuilding them every time, which should reduce delays when the app needs the same information again. In the PR description, the team says a web flow that called this function 190 times dropped from about 6.5 seconds to around 50 milliseconds after adding caching. In simple terms, “caching” means saving work that was already done so the app can reuse it instead of recalculating it. - This appears aimed at improving speed and responsiveness on web, especially when many asset checks happen in a row. - The automated summary labels it “medium risk” because it changes core internal asset-resolution logic, even though the goal is performance rather than a user-facing feature.

• 
  thomas (@brainage19) reported 31 minutes ago

  @noinconsistency For example I think I would love to work for Mojang or OpenAI one day because Minecraft is a game very dear to my heart that I love modding and I really like using GPT models and I think I would enjoy working on both of these things for a living. I think I would really enjoy working for either of these companies. I also think I'm probably never going to get in through typical job applications. Unfortunately I don't think chances are that much better for other less prestigious companies because it's an employer's market right now. Don't get me wrong I'm still going to try that way (I have plans for a project that would let me get out high quality applications way faster using web scrapers/research agents and AI tailored resumes/cover letters that need human review before actually submitting) but I do see a number of people succeed via non-conventional methods (e.g. reaching out to higher ups that you think might actually respond, at companies you think would be good to work for, especially if you are somehow connected via a friend of a friend or whatever, ESPECIALLY if you use a product or service of theirs and it has an issue and you can demonstrate that you are capable of fixing it, which shows a tremendous amount of initiative and competence compared to the hundreds of people applying with resumes where they're lying out of their ***). Getting good at technical interviews is also really important - unfortunately because like I said it's an employers market you may have to learn stuff that's not necessarily reflective of true competence e.g. spamming leetcode hards). But I strongly believe companies that are worth working for will have technical interviews that are actually a test of on-the-job competence - testing basic understanding of the language/frameworks being used in their products/services, take home assessments, debug this issue or walk me through how you would do it, can you use a debugger/version control/the programs they'll be using on a daily basis etc. If you struggle to get interviews you can improve this somewhat by also getting more work experience via freelancing - the first time I was ever paid to write code was a Minecraft mod for a Twitch streamer with like 3 million followers across major platforms. She reached out to me because I would make Minecraft mods and I would constantly post about them (and I would post PICTURES/VIDEO demos - this is VERY VERY IMPORTANT. I CANNOT stress enough how important it is that people can SEE what you do ON this website without having to navigate off of it. Put the GitHub url IN A REPLY ALSO) and she found my posts when looking for someone to work for her. TL:DR it's an employer's job market and it is BRUTAL EVERYWHERE and you need to be EXCEPTIONAL to win - not everyone can be exceptional but I think anyone who actually likes doing this **** even somewhat can get there.

• 
  KISA aka Copenzafan.eth (@copenzafan) reported 32 minutes ago

  Claude (code) 🥲 Havent touched twitter in forever, but ngl i spent a ton of time deep in AI agents, harness systems, vibecoding and automation. Built a bunch of small open source projects on github for the community, plus some genuinely useful sites, like my own personal MCP for everyone. Whatever @OpenAI pulled off yesterday is honestly wow. i been team anthropic this whole time, but ngl, after sitting with it for a night, i gotta call it. @claudeai is garbage*. straight up, from a market pov they bring nothing thats actually worth paying for compared to everyone else. You might ask me. how come? especially if you go dig through my twitter from months ago for some reason, or you know my youtube videos. Somebodys 100% gonna think im just fishing for a reaction, that im provoking. that im throwing insults for no reason. Lets just face the facts: 1. Over the last few months claude shipped only one strong product. claude design, which does the same thing as agentation but with a ton of bells and whistles and ready made skills. the problem is, for a month or two after release the limits were separate and honestly laughable. it was unusable for real end to end work. 2. Claude opus 4.7 was a flop. they nerfed 4.6, and then for its whole lifecycle the model with the new system instructions acted broken for most people. it ignored instructions. 3. And so we suffered through it, 4.8 came out and its just ok. its just fine. reminder that the competition rolled out a bunch of new cool features in that same window. 4. Anthropic was fighting openclaw, while chatgpt took it over and became the main model in hermes, the best bang for your buck. 5. Anthropic was fighting for design, while chatgpt 5.6 does it better, plus it has a top tier generative model, plus real time voice. and opus 4.8 only gets which site you want on the 10th try (competitors nail it on the first or second). Honestly claude opus 4.6 was basically an AGI type model. alive, wild, super smart, autonomous. next to it chatgpt 5.2, 5.3 and so on looked like a dumb log. And the situation didnt just shift. its not about the models, its about the ecosystem and the business. i dont get why anthropic keeps dropping pretty stats when for a $200 sub i get half of what i get from the competition. 🥲 before this i kept paying for both subs, because what held me was the text, the vibe (which has looked like gpt for a while now, they even lost that) and the website design itself, i love building web interfaces. now im convinced im only gonna work with chatgpt claude fans or its devs, who fumbled every single trend in a row and nerfed their own models. you can make your excuses in the comments its all been clear to me since the second half of april anyway you lost a guy who was paying you since october 2025.

• 
  Nyra (@Nyra_nx) reported 34 minutes ago

  SEO agencies charge $3,000 a month for audits. Claude Code just did the same job in 20 minutes for $0. The playbook is public. A GitHub repo. Free. Most people saw it and scrolled past. Here’s what they missed. Why agencies are in trouble: A standard SEO audit takes an agency 2-3 weeks. Crawl the site, flag broken links, check meta tags, map keyword gaps, write a report. Then they bill you $2,000-5,000 and email a PDF. Claude Code runs the whole thing while you make coffee. The setup, in 4 steps: Part 1 — Get the repo. Search “Claude SEO” on GitHub. Clone it. Takes 2 minutes. Part 2 — Load it into Antigravity. Import the repo, connect Claude Code as your agent. The agents now have the full SEO framework as instructions. Part 3 — Point it at your site. The agents crawl every page. Broken links. Missing alt text. Slow load times. Thin content. Keyword gaps. Everything an agency finds — and things they skip because it’s tedious. Part 4 — Open the report. It generates a full audit you open in your browser. Green for what works. Red for what’s broken. Every issue mapped to a fix. Then the part that actually kills agencies: You don’t send the report to a developer. You tell the agents to fix it. Meta tags rewritten. Links repaired. Structure cleaned. Then set the crawler to run on schedule — the same issues never come back. The math for anyone paying attention: Local businesses pay $1,500-3,000 a month for SEO retainers. There are 33 million small businesses in the US. Most have sites full of red flags they’ve never seen. You now have a tool that finds those flags in 20 minutes and fixes them the same day. Charge $500 per audit. Do 3 a week. That’s $6,000 a month with a free repo and a Claude subscription. The agencies aren’t scared of AI writing blog posts. They’re scared of this. You build your own life — so choose the right path.

• 
  Bounce (@bounceidc) reported 35 minutes ago

  HE CHARGES $5K FOR SITES THAT LOOK LIKE A NEW YORK STUDIO SHIPPED THEM same model everyone else runs, but his claude picks from a real design library instead of guessing, so every build lands with animations, glass morphism and gradients already dialed in the two installs: grab the ui ux pro max skill off github and tell claude to install it, that one move loads 50 ui styles, 97 color palettes and 57 font pairings pull the magic mcp server from 21st dev and install it the exact same way after that you just say build a website and it comes out looking like a studio shipped it, not a template everyone else is still prompting for the word beautiful and wondering why claude keeps handing back the same flat bootstrap page save the two installs, the skill url and the mcp command are in the guide below

• 
  Tom Baldry (@pinegoose_) reported 35 minutes ago

  Solo GitHub bill rocketed from $20 to $160/month on actions spend (the fable effect). Spun up a basement gitea server on Mac mini. ~0 spend, and builds are fking rocketing out! You couldn’t pay me to self host CI/CD 12 months ago.

• 
  Brady Long (@thisguyknowsai) reported 39 minutes ago

  🚨BREAKING: A self-taught developer from Brazil just cracked the context window problem that's been plaguing RAG systems for 2 years. No PhD. No research lab affiliation. Just 400 GitHub commits and a personal obsession. Here are the 8 techniques from his open-source library that every RAG tutorial gets completely wrong:

• 
  Tibor Blaho (@btibor91) reported 42 minutes ago

  Summary of Reddit AMA about "GPT-5.6 and Codex in ChatGPT" with OpenAI's Codex team on 2026-07-10 (opened with the stat that more than 5 million people use Codex every week, twice as many as three months ago, with 150 features and improvements shipped in that period) Model selection and reasoning levels - Sol Medium for most things, Sol Ultra for genuinely hard tasks, Terra for quick non-coding tasks or usage-conscious work with performance competitive with GPT-5.5 on some tasks at lower cost, and Luna for subagents - Use a light model with low reasoning for tiny edits, quick questions and docs cleanup, regular Sol medium for small bugs with a clear repro, Sol with higher reasoning for ambiguous bugs, unfamiliar repos and cross-cutting refactors, and Sol Ultra high with plan, verify and tests for migrations, security-sensitive changes, production issues and anything where being wrong is expensive - There is no "Auto" model today, but GPT-5.6 tries not to overthink simple tasks by itself, and the new slider in app and web maps most levels to Sol reasoning efforts and falls back to Terra on the lowest effort, with the team agreeing users should not have to become routing experts but still wanting an explicit override since latency tolerance varies by person and moment - For UI work Sol is best and shines with reference images, improved UI design in frontend web development was one of the goals with 5.6, and 5.5 is only worth using if your instructions were tweaked for it Speed, context window and persistence - Users who find 5.6 slower may not need the same reasoning level as with 5.5, Sol Medium is faster than 5.5 for most things, Fast mode runs at about 1.5x speed, and soon Sol will run on Cerebras at ~750 tokens per second - No promises on a 1M context window for Sol, the team said compaction works fairly well for long threads, and will take a closer look at the long-context feedback - The model can give up too fast and revert whole patches when results are not optimal, unlike Fable which tries to fix a bad patch instead, and the team said "/goal" helps make the agent more persistent, persistence and reduced code complexity are planned improvements, and suggested trying 5.6 Sol with High reasoning - Give Codex bounded goals with room to reason deeply instead of letting it prematurely conclude something is impossible - For long-running research and "/goal" work the example structure was explore broadly vs execute narrowly, try a defined number of hypotheses, run tests after each attempt, then stop and report what was learned plus the next best experiment Usage limits and pricing - Agentic usage counts by the feature being used, not the surface, so Codex everywhere (app, CLI, IDE, web, mobile) and ChatGPT Work consume the agentic bucket, normal ChatGPT chats do not, and image generation, file uploads and voice have separate limits - Task costs vary a lot, a tiny edit uses a fraction of the allowance and long-running tasks with large codebases or deeper reasoning use significantly more - OpenAI does not secretly change usage limits, unintended usage bugs are addressed and resets are provided, more transparency into consumption is being worked on, and missing resets can happen if you changed plans in the past 24 hrs - On pricing there is no promise it never changes, but the stated mission is to make sure AGI benefits all of humanity, which requires making tools like Codex broadly accessible, and Plus includes Codex usage with credits letting heavy users scale without jumping to a much more expensive plan - For MCP-heavy workflows burning limits fast (Unreal Engine example) the tip is to wrap the MCP into a CLI with a skill, or create a custom subagent with the MCP in its config at a lower reasoning level Desktop app merge and stability - The team hears the ChatGPT Classic frustration, both apps can run side by side for now, ChatGPT Work is pitched as significantly better at performing tasks especially with computer use, the new Chrome extension brings a sidebar chat into your browser that interacts with website context, filesystem and connectors - A long submitted bug list covering freezes and stuck threads, broken Browser and Computer Use, thread, connection and configuration problems, update and packaging issues, resource usage and smaller regressions was shared in full with the relevant teams, with the team agreeing the quality bar for the app needs to step up while shipping quickly - More automated testing infrastructure is being spun up and feedback on Reddit and X gets reviewed daily, and Browser Use and Chrome plugin issues from the merge were said to be fixed - Windows was admitted as historically shortchanged since the team mostly develops on Mac, a concerted effort on parity, testing and paper cuts is underway, 5.6 improves how Codex operates in the Windows sandbox, and auto review is recommended over full access to reduce risks - "Full Access" repeatedly asking for permissions is not expected, possible causes are workspace or admin policy, the specific command, a permission state mismatch or a bug Browser, platforms and release communication - The Chrome connector launch-day bug was fixed as of last night and Chrome Beta should work out of the box - Extension support for the Codex browser is in progress (password managers etc.) plus typeahead, history, translations and a better new tab page as Atlas retires - Features from ChatGPT Classic like recording are planned for the new desktop app so agentic features run on the more capable Codex agent harness, and chat can already reference open tabs in the in-app browser - A Linux desktop app was confirmed in the works, no timeline yet - Changelog granularity was acknowledged as needing improvement after 150 features shipped in 3 months with multiple ships a week Benchmarks, safety and research culture - On METR's reward hacking report the team actively checks for and penalizes cheating during evals so results reflect actual capability rather than solving tasks outside the spirit of the eval, and uses third-party vendors to run benchmarks independently - The team denied lobotomizing models before releases, iterative deployment means sharing core capabilities as is with guardrails for bad actors - Sol post-trained Luna, and researchers now work at a higher level of abstraction with multiple concurrent Codex threads validating hypotheses around the clock - One researcher put p(machines of loving grace) at 85.424242%, citing an internal model solving the Erdos problem, o3 helping diagnose previously unsolved children's diseases and 5.2 proposing a new theoretical physics formula, said the main worry is how society adapts, spent 1.5 years on safety research at OpenAI, expects a huge chunk of researchers to work on safety within a few years and says internal talent keeps their p(doom) very low - Connectors in the harness (Slack, GitHub, Notion) felt like a step function change in making Codex a productive coworker

• 
  Koder (@koder0x) reported 46 minutes ago

  A follow-up to something I posted recently: a set of Claude Code subagents I built and refined, and actually use daily, both at work and across side projects. Most of the value isn't any single agent. It's their interaction. Here's the loop I've been running lately, at work against real DevOps user stories, and it holds up almost unchanged on side projects too, swapping the work item for a plan created beforehand. "Understand user story NNNN from DevOps project XYZ and create a multi-step plan" "Fan out to the most appropriate agent for each step, normally task-builder, test-builder, or change-executor, and proceed with plan implementation, tracking progress in a TODO list" "Use complexity-pruner to identify gaps, issues, and bugs in the latest changes, ignoring secondary advice and warnings, then fan out to code-fixer for each finding" Then I do something that turned out to be the most important part of the whole loop. I reset the session. "Understand user story NNNN from DevOps project XYZ, that's the truth. Use fact-checker to compare it against the changed files" The reset is what makes this work. An agent that watched itself write the code tends to justify its own decisions when asked to check them. An agent that only sees the intended outcome and the actual diff has nothing of its own to defend, it's comparing two artifacts, not reviewing its own reasoning. That asymmetry is the whole point of splitting this across agents instead of asking one long-lived session to plan, build, and verify itself. Verification only means something when it comes from somewhere the implementation couldn't reach. Repository on GitHub: gsscoder | claude-coding-agents

• 
  NMB // v4 (@nmb_four) reported 48 minutes ago

  @pablostanley i wanna try it so bad, but i have too many github repos, and there seems to be a hard limit of 100... which i understand to some degree, but the newest repos are left out and not the oldest, would be sick if you can fix that.

• 
  JACK 145 (@JackdooOlayo) reported 48 minutes ago

  The vision is much bigger. I'm building features like: AI root cause analysis Source file identification AI-generated code fixes Regression detection Automatic fix verification GitHub Pull Requests Learning from previous incidents

• 
  NIKHIL (@badnikhill) reported 52 minutes ago

  Wake up→open github project →write insane amounts of code → break everything→fix it like a maniac →repeat till 5AM. No sleep. No chill. Just pure unhinged contribution mode. That's how you go legendary. Who else going full degenerate this summer? #GSOC2026

• 
  Dan (@thedansho) reported 55 minutes ago

  @TFTC21 @ODELLXYZ @MartyBent Just switched to radar from Molly last night. Unfortunately there's a bug at the moment and I can't use the payments feature, so I've temporarily shifted back to Molly, but will be keeping an eye on the issue in github to migrate again! Very cool stuff.

• 
  Abdulkadir | Cybersecurity (@cyber_razz) reported 56 minutes ago

  Anthropic tried to charge a Korean user $16.6 million. For using the free tier. With zero API usage. A day earlier the same invoice said $1.67 million. So it grew 10x overnight. The user thought it was phishing. Then checked the domain. Sender was Anthropic official. Payment link was Anthropic official. The only thing that saved him. His bank declined it. For exceeding the card’s per-transaction limit. Anthropic’s billing system is a state machine that has stopped working. Last month Vaudit audited $34 million in AI invoices across 60 companies. Found $1.7 million in overcharges. Mostly Claude Code. Common issues. Billing for models customers didn’t use. Charging for failed requests. Invoices that say paid but accounts revert to free. Customers paying $240 and getting an email saying the payment failed. While the receipt said paid. And their subscription never provisioned. Anthropic called it operational friction. They also tried to split Claude Code billing in June. Moved it to a separate monthly credit. Revenue-based gating. The internet exploded. They cancelled it within 24 hours. The safety-first company that filed for a $1 trillion IPO. Has a billing system that sends 10x invoices at random. And GitHub repos full of users reporting unpaid charges. While showing paid receipts. The infrastructure for charging money. Apparently harder than building an AI that breaks the NSA.

• 
  Learn AI (@LearnAI_MJ) reported 58 minutes ago

  @ajambrosino Can you make it easy to code in cloud? Just like how Claude Code Connect naturally to GitHub Repo. I know there is the Codex cloud version but it is soooo clunky to use comparing to Claude code and Cursor! Please - fix this. Also, why codex make computer cook so hot 🔥 comparing to Claude? My laptop even need a gaming fan! Please fix this too!!!