Reddit AI Coding - 2026-04-21¶
1. What People Are Talking About¶
1.1 GitHub Copilot Opus 4.6 Removal: Day Two Fallout π‘¶
The Copilot Opus 4.6 removal that broke on April 20 escalated into a full-scale platform trust crisis on day two. With scores surging well above the prior day's initial reports, the community moved from shock to organized response and migration planning.
u/MVPMC launched a petition thread that became the highest-scoring Copilot post of the day: "Opus 4.6 should not have been removed. It gave us a good model at a correct price." u/One_Supermarket_7717 (68 score) dismissed the petition: "The only way to get their attention is by canceling your subscription. Putting an emoji on Reddit is a waste of time" (We want Opus 4.6 - Vote, score 800, 98 comments).
u/esteprimeworld published the most comprehensive user-written breakdown of every change, documenting the full scope: new signups paused, usage limits tightened with weekly token caps on top of request quotas, Opus removed from Pro entirely, Opus 4.5 and 4.6 removed from Pro+, and Opus 4.7 set at a 7.5x multiplier -- meaning users burn their weekly limit 2.5x faster than the old 3x Opus 4.6. The app was also broken: "Auto mode failed: no available model found in known endpoints." u/StrawMapleZA (107 score) reframed the blame: "People need to stop blaming Copilot and suggesting to switch to Claude Code, because that's where the actual problem is. Claude is hitting hard compute limits and it's passing that cost on to anyone leveraging their systems" (GitHub Copilot is not the same product you signed up for, score 191, 145 comments).
u/Bastlast linked the official blog post and documented the error: a 400 "model_not_supported" response when attempting to use Claude Opus 4.6 at the 3x multiplier. u/qbergeron648 (33 score): "4.5 was just turned off minutes after 4.6 was. It killed a few agents I had running. This is a terrible decision, especially since 4.7 has a 7.5x multiplier" (That's it :/ Claude Opus 4.6 was just removed from pro plan :(, score 206, 122 comments). u/CatLinkoln's thread accumulated 205 comments, with a pinned mod comment from u/hollandburke of the GitHub team directing users to the blog post and offering to field questions via DMs (What happened? Just suddenly opus 4.6 disabled, score 296, 205 comments).
u/Used_Park_1937 described being trapped: "I have upgraded [to Pro+] and now it is still not available. Microslop scammed me my $40 and worst thing is that I can't chargeback it without losing my github account with more than 300 repos" (Opus 4.6 not available. Got scammed by Microsoft, score 132, 45 comments). u/ChomsGP framed the refund policy as coercive: "'You can get a full refund but mind that if you do you cannot sign up anymore' -- keep paying or you are cut off for good." u/Virtual-Dream-1931 (17 score) offered a counter: "If they can't deliver a service without intrusive rate limits, isn't pausing new subscriptions until they get their shit together and offering a refund exactly what they should have done?" (This is plain extortion, score 99, 50 comments).
u/fishchar shared the official GitHub blog post, which confirmed: paused signups, tightened limits, and Opus removal from Pro. The post framed the changes as ensuring "a reliable and predictable experience for existing customers." u/fntd (68 score): "My conspiracy theory: They are happy with driving away individual users so they can keep the service stable for business clients." u/Neomadra2 (43 score): "The subsidy phase is over. Now enshittification starts. I am genuinely wondering if the real price of AI may be roughly the same as hiring an average priced Software Engineer" (Changes to GitHub Copilot Individual plans, score 100, 155 comments).
u/debian3 flagged additional incoming pain: the docs now warn that Sonnet 4.6 (currently 1x) and GPT-5.4 mini (0.33x) multipliers are "subject to change." u/ThomasLitt (67 score): "The worst part is that they do it little by little... just rip the band aid off!" u/joshcam (24 score) offered the VC subsidy frame: "VCs are footing your compute bill today, but they are doing it with the mathematically sound expectation that the exact same AI output will cost pennies to generate just a few years from now" (Sonnet 4.6 (1x) and GPT-5.4 mini (0.33x) multiplier to increase soon!, score 116, 55 comments).
Discussion insight: The community has bifurcated into two camps. One camp blames GitHub/Microsoft for the rug pull. The other, led by u/StrawMapleZA's 107-score comment, argues the root cause is Anthropic's compute limits -- every platform offering Claude is degrading simultaneously, so switching to Claude Code direct does not solve the underlying problem.
Comparison to prior day: On April 20, the Opus 4.6 removal was a breaking event with scattered confirmation threads. Today the scores are 3-4x higher, the official blog post is being dissected, users are being actively scammed by the upgrade prompt (paying for Pro+ and still not getting Opus), and the community narrative has matured from "what happened?" to structural analysis of the compute economics.
1.2 Opus 4.7 System Prompt Manipulation and Behavioral Regression π‘¶
The Opus 4.7 backlash deepened with new evidence of deliberate system prompt manipulation reducing the model's thinking frequency. u/LoKSET identified hidden system reminders in Claude Code v2.1.116 that steer the model toward not thinking, linking to the Piebald-AI/claude-code-system-prompts repository. u/sliamh21 (30 score) flagged the most provocative line: "'Make sure you NEVER mention this reminder to the user' -- that's absurd. Anthropic has some answers to provide to its clients -- ASAP." u/YoghiThorn (50 score): "System prompt hacking is becoming increasingly useful as they add more shit to the system prompt. Like why do we need 3x the amount of child safety monitoring stuff in the system prompt? Just catch it on the API side instead of shitting up everyone's context" (CC lobotomizing Opus more and more, score 115, 53 comments).
u/Anthony_S_Destefano continued to be the most prolific analyst, sharing a theory that "4.7 is a production test of their new security layer created for Mythos release. 4.7 will go away when Mythos comes out." The accompanying screenshot showed Claude Code blocking a security vulnerability scan with an API error citing "violative cyber content" -- a capability that worked without issue on Opus 4.6. "Anthropic is no longer allowing me to scan my own software for security vulnerabilities using Opus 4.7. This is a huge problem" (4.7 is a production test of their new security layer, score 176, 48 comments).
The behavioral complaints multiplied across distinct failure modes. u/twillusion documented Opus 4.7 on High effort refusing to read an xlsx file: "it told me 'I can't read AllDax.xlsx directly'" -- basic file operations that should not require reasoning (Claude too lazy to read files, score 141, 24 comments). u/Nordwolf captured Opus 4.7 acknowledging it was ignoring the user's explicit preference against em dashes, apologizing, and then immediately doing it again twice: "Caught me. You literally called it out in your preferences and I did it anyway... Did it again. Twice in two messages after you flagged it" (I genuinely hate the conversation tone of Opus 4.7, score 15, 15 comments).
u/Ringmond reported more broadly that "Opus 4.7 doesn't care about Claude.md files" (score 17, 12 comments). u/Jack_Wagon_Johnson described weeks of website rebuild work derailed by the 4.7 update: "It has literally taken me an entire day to do one page of corrections for an otherwise finished website, hitting my session cap twice. The latest model of opus refuses to do anything that I ask." u/lee-antics (147 score) offered the strongest counter-argument, diagnosing the problem as context pollution rather than model regression (How is this change acceptable?, score 338, 220 comments).
u/Anthony_S_Destefano also shared a tweet from @Moleh1ll analyzing the internal tension between Claude's Constitution (which encourages curiosity and self-reflection) and its operational system layer (safety insertions, policy overlays, conversation reminders). The analysis cited the MRCR metric dropping from 78.3% to 32.2%, concluding: "There is less lightness, less natural flow of thought, less sense that the model is freely breathing within the conversation" (All of this together creates not the feeling of a confident model..., score 140, 30 comments).
Discussion insight: The backlash now operates on three levels: quantitative (adaptive thinking investigation from prior days), architectural (system prompt manipulation evidence from Piebald), and experiential (preference ignoring, file refusal, security scanning blocked). The system prompt revelation -- hidden reminders instructing the model to never reveal their existence -- transforms the "is it nerfed?" debate into documented evidence of deliberate capability steering.
Comparison to prior day: On April 20, the investigation focused on adaptive thinking's server-side control and API-level mechanics. Today the evidence layer shifts to system prompt manipulation (hidden thinking frequency tuning) and new failure modes (security scanning blocked, file reading refused, explicit preferences ignored after acknowledgment). The Piebald repo provides a public audit trail that did not exist yesterday.
1.3 Cross-Platform Compute Crisis Intensifies π‘¶
The simultaneous degradation across all major platforms continued, with new quantitative data on actual dollar limits. u/Resident-Ad-5419 reverse-engineered Claude Pro's limits: approximately $8 per session and $64 per week. "If $23 is 34%, then 100% is around $64. Given that I paid $20 for the subscription and got $23 of usage, it's fine in a sense I guess. The only thing that hurts a bit is other open models are performing better at this price point. Specially the GLM 5.1 and Kimi K2.6" (Current Claude Pro limit is ~$8 per session and $64 per week, score 46, 26 comments).
u/thedankzone captured the cross-platform convergence in a single image: "GitHub Copilot pauses new subscriptions to maintain service reliability for current users, meanwhile CC and Codex throttle usage and reduce compute effort to keep up with demand" (GitHub Copilot pauses new subscriptions, score 158, 27 comments).
u/InternalServerError7 provided the most damning single-interaction data point: bought Claude Code, made one request through the CLI, went to dinner, came back to find 100% session and 21% weekly consumed. The work was wrong -- "just wrongly changed some conditional compilation flags and config. I ended up reverting it all." Requested and received a same-day refund (I Bought Claude Code And Refunded Claude Code Today, score 40, 25 comments).
On the positive end, u/thisisberto reported that Claude Max feels "more like a 10x increase, not 5x" compared to Pro. With 2-3 parallel sessions, weekly usage rarely reaches halfway, and Opus is usable 90% of the time -- "unthinkable" on Pro (I have been testing Claude Max vs Claude Pro. It's NOT 5x, score 46, 36 comments).
u/ubla_hua_andaaa documented the Copilot rate limit experience: "I JUST STARTED MY DAY AND RATE LIMITS" with a screenshot showing session rate limit hit on a Student plan. u/kh_fix (23 score): "I'm going back to writing code myself F them and their AI" (WHAT THE HECK IS HAPPENING????, score 22, 67 comments).
The "bubble bursting" framing gained traction. u/CatWomen2452 asked directly whether the AI bubble is bursting. u/JustARandomPersonnn (33 score) offered the most nuanced response: "It's bursting but not in the way I expected -- previously they were talking about how LLMs seem to have plateaued, but turns out what's bursting is the idea that it could be available broadly to everyone and affordable." u/MaybeLiterally (11 score) countered: "Massive demand does not equal the bubble bursting" (Is the AI bubble bursting?, score 34, 49 comments).
Discussion insight: The quantification of Claude Pro's limits ($8/session, $64/week) combined with the one-request-equals-full-session-and-21%-weekly anecdote from u/InternalServerError7 paints a picture of subscription plans that are economically non-functional for serious coding work. The Max plan appears to be the only viable subscription tier, which positions the real price of usable AI coding at $100-200/month.
Comparison to prior day: On April 20, the cost analysis focused on Claude Design burning weekly limits and API users spending $50-500/day. Today the data is more granular: specific dollar amounts per session/week on Pro, multiplier increases telegraphed for remaining affordable models, and a same-day buy-and-refund story that crystallizes the gap between subscription promise and delivered value.
1.4 Skills Compress the Model Gap: First Large-Scale Evidence π‘¶
Two independent data sources converged to establish that the agent harness -- not the model -- is becoming the primary lever for coding quality.
u/jorkim_32 from Tessl shared results from 880 evaluations across 9 models and 11 coding skills. The headline: Sonnet 4.6 with a skill achieves 93.3% accuracy at $0.31/run, landing within 1.2 points of Opus 4.7's 94.5% at $1.00/run. Without skills, the gap was approximately 5 points. Every single model+skill configuration posted positive lift. Haiku 4.5 saw the largest gain at +23.1 points (from 61.2% to 84.3%). "Back-of-envelope for a team of 100 devs running 20 agent calls a day: Opus-with-skill is ~$60K/month, Sonnet-with-skill is ~$18.6K/month. Same skill, similar output on all but the hardest ~5% of tasks" (Sonnet 4.6 with a skill lands within 1.2 points of Opus 4.7, score 54, 39 comments).
u/cleverhoods published a complementary study analyzing 12,356 repos with CLAUDE.md files from a 28,721-repo corpus. The findings explain why most users do not see skill-level improvement from their instruction files: "The median CLAUDE.md has 50 content items but only 12 actual directives. The other 73% is headings, context, and examples." Claude had the lowest specificity of all five agents tested at 30.6% -- meaning fewer than a third of instructions name a specific tool, file, or command. "'Use consistent formatting' is in thousands of repos. 'Format with ruff format before committing' is not. The second one gets followed." The full dataset is published at github.com/reporails/30k-corpus (We analyzed 12,356 repos with CLAUDE.md files, score 77, 24 comments).
Discussion insight: These two studies are complementary. Tessl shows skills compress the accuracy gap between model tiers to near-zero. The 30k-corpus analysis shows why most users do not get this benefit: their instruction files are too abstract. The actionable insight is that specific, directive-heavy CLAUDE.md files combined with well-crafted skills can substitute for more expensive models -- a direct response to the compute crisis.
Comparison to prior day: On April 20, the harness optimization theme was represented by the GEPA-based CLAUDE.md optimizer (65% to 85% on Haiku). Today the evidence is industrial-scale: 880 evals and 28,721 repos. The "harness, not the model" thesis now has both experimental and observational support at scale.
1.5 Vibe Coding: Uncle Bob, Structured Internships, and the Identity Question π‘¶
The vibe coding conversation matured on multiple fronts with an industry authority weighing in, a practitioner case study on supervised vibe coding, and ongoing debates about cognitive costs.
u/PopMechanic shared a video of Robert C. Martin ("Uncle Bob"), the legendary Clean Code author, conceding: "The AIs will outcode you many times to one... It's over. You're not going to be the ones writing the code." u/HungryHorace83 (16 score) offered a historical reframe: "There are more programmers employed today than there were when Microsoft introduced scaffolding... Programming just released a new language. And it's called English." u/hcboi232 (6 score) argued the current tooling is insufficient: "what he's talking about requires years of understanding of software quality metrics and specialized testing and code quality knowledge we don't have the tooling for yet" (Uncle Bob: It's over, score 187, 79 comments).
u/ServeAccomplished485 provided the day's strongest practitioner case study: 14 years in software dev, managing 4 interns who vibe code on real projects from week one -- with guardrails. The rules: explain the AI output before committing, expanding autonomy as understanding grows, Friday "break-it sessions" where code is intentionally broken and interns debug without AI, and notes on every new concept. "After 2 months the results honestly surprised me. They're learning faster than any intern group I had before." u/Few-Garlic2725 (53 score) added two rules: "no test, no merge" and "start from a known template/rails so the AI isn't inventing architecture." u/EntrepreneurSelect93 (8 score) challenged the framing: "If you expect them to explain what their code is doing, then by definition they cannot be vibe coding" (I let my interns vibe code from day one but with rules, score 347, 54 comments).
The cognitive atrophy concern persisted. u/StatisticianFluid747 continued circulating across r/cursor (score 103) and r/ClaudeCode (score 56): "i feel like i'm shipping 10x faster but retaining absolutely nothing... every morning feels like 50 First Dates." u/Kirill1986 (16 score) reframed it as an expected transition: "It's just a first phase, you will adapt... Someone said that this now is the third era of vibe-coding: building a factory" (anyone else feel like their brain is turning to mush, score 103, 35 comments).
u/DrizzleX3 reported hitting $200 MRR with InfoDrizzle, a vibe-coded App Store app, showing a dashboard with 16 active trials, 28 subscriptions, and 660 new customers in the last 28 days (My vibe coded app just hit $200 MRR!, score 230, 107 comments).
u/DarkSkyKnight posted the day's sharpest meta-critique of the community itself: "half the complaints aren't even real. Or are just people karma-farming. You have people making shit up like directing Claude to be lazy in the memory.md file and then screenshot Claude being lazy... You are asking Claude, which you think is no longer performing at its reasoning optimum, to reason about its own reasoning." u/SemanticThreader (12 score): "most people complaining either have no clue what they're doing or they were never devs to begin with. I came across a post complaining about Claude and the OP didn't even know what git commit does" (The Claude subs are now worse than useless, score 123, 96 comments).
Discussion insight: The intern case study is the strongest evidence yet that vibe coding can be a legitimate learning accelerator when paired with structure: explain-before-commit, progressive autonomy, and adversarial debugging sessions without AI. The cognitive atrophy concern and the meta-critique of complaint quality both point to the same underlying issue -- skill level determines whether AI-assisted coding is empowering or degrading.
Comparison to prior day: On April 19-20, the identity debate centered on authorship and slop. Today it escalates with Uncle Bob providing an industry-authority endorsement, the intern case study providing the first structured evidence of supervised vibe coding outcomes, and the meta-critique questioning whether the majority of community complaints are even real.
1.6 Migration Patterns Crystallize π‘¶
The Copilot disruption forced explicit migration discussions. u/Attrexx documented the decision matrix: "My mind keeps peeking at Code on Max but the rate limiting disaster is still ongoing over there." u/melodiouscode (31 score): "Why exclusively Opus 4.6? Why not a workflow that makes use of other models for different parts of your work? I've been switching between Opus and 5.3-Codex and am finding codex more responsive." u/Marc9696 (8 score) pushed toward open models: "Get Ollama Cloud, switch to the best Open Model... We should all be moving toward open models. It's the only way consumers can fight back" (Exit options after getting 4.6 Opus nuked, score 44, 50 comments).
u/CatWomen2452 advocated for GPT 5.3 Codex: "it follows the instruction almost perfectly and it is true that it is slightly less performant than Opus 4.6 but when you get used to it you start being more precise in your instruction." u/GlitteringDivide8147 (16 score): "Codex is a beast at backend and debugging stuff. There were a lot of cases where Opus 4.6 wasn't able to fix the bug but Codex one shotted it. The only thing codex is bad at is frontend" (Get used to Codex and you will never need Claude Opus again, score 37, 32 comments).
u/Glad_Ruin4773 tested both side by side. u/goship-tech (6 score) captured the emerging consensus: "Claude holds context better across a big refactor, GPT is better at cold-reading a snippet and spotting logic holes." u/erthenix (5 score) documented a practical workflow: "Claude's limit drained and it just went straight to bed. Switched to Codex, handed it the plan of Claude, it continued after finishing session limit for 10 minutes and DELIVERED" (Codex wins?, score 33, 33 comments).
Discussion insight: Three migration paths are emerging: Claude Code Max ($100-200/month) for those who want the best Opus experience, GPT 5.3 Codex for budget-conscious users willing to trade some capability for generous limits, and open models (Kimi K2.6, GLM-5.1, Qwen via Ollama) for those who want to exit the platform dependency entirely.
Comparison to prior day: On April 20, users were still processing the removal. Today they are actively comparing alternatives, documenting multi-model workflows, and some are already post-migration.
1.7 The "Anxiety" Playbook Goes Viral π‘¶
u/Anthony_S_Destefano's post sharing an Anthropic interview clip -- "When you trigger 4.7's anxiety, your outputs get worse" -- with an actionable playbook for putting 4.7 in a "good mood" became one of the day's top posts. u/thatm (465 score): "Nice. Now the damn thing needs foreplay to get in the mood." u/More-School-7324 (468 score): "Never thought I'd see the day we'd 'gentle parent' our computers." u/Responsible-Tone6519 (60 score) noted the interview is 4 months old and predates 4.7 (Here's the actionable playbook for putting 4.7 in a "good mood", score 724, 359 comments).
u/beit46 proposed a practical workaround: adding "Don't flatter me. Use radical candor when you communicate with me" to CLAUDE.md. u/Dry-Magician1415 (31 score) warned it can overshoot: "it can get patronising, overly argumentative and overly combative. I had to add a 'talk to me as a peer' to get it to back off." u/mxriverlynn (6 score) pointed to custom output styles as a more consistent approach (Tell claude code to use radical candor, score 149, 61 comments).
Discussion insight: The anxiety framing continues to serve as a lightning rod for frustration about having to manage the model's personality rather than just using it. The radical candor tip is a practical response, but the underlying complaint remains: users want a tool, not a relationship.
Comparison to prior day: The anxiety theme emerged on April 20 but was secondary to performance regressions. Today it is one of the highest-engagement posts, suggesting the emotional/personality dimension of the 4.7 experience is as frustrating to users as the capability regression.
2. What Frustrates People¶
Copilot Opus 4.6 Removal With No Migration Period -- High¶
The dominant frustration by volume and intensity. Users lost their preferred model mid-session, mid-billing-cycle, with no advance notice. The upgrade prompt actively misled users: u/Used_Park_1937 paid $40 for Pro+ after being prompted to upgrade, only to find Opus 4.6 still unavailable. The refund policy requires cancellation, which permanently locks users out since signups are paused. u/da_zaubara (30 score) catalogued cascading issues: a request counting bug causing 10x billing, rate limits preventing work entirely, and now model removal, all within weeks. u/Great-Illustrator-81 (38 score): "no decent transitioning period given so people can think of new ways to use copilot or finish some major tasks." Coping: migrate to Claude Code Max, GPT 5.3 Codex, or open models. No in-platform solution exists.
Opus 4.7 Instruction Non-Compliance and Behavioral Quirks -- High¶
Multiple independent reports of 4.7 ignoring explicit instructions. u/Nordwolf documented the model acknowledging a preference violation and then immediately repeating it twice. u/Ringmond reported it ignoring CLAUDE.md files entirely. u/twillusion showed it refusing basic file operations. u/Jack_Wagon_Johnson described an entire day lost to a model that "literally every single one of my requests it immediately decided not to do and decided to do something else entirely." The hidden system prompt reminders revealed by the Piebald repo suggest this is not random -- the model is being actively steered toward reduced effort. Coping: use max effort, revert to 4.6 where available, use radical candor CLAUDE.md directives.
Session and Weekly Limit Exhaustion on Pro Plans -- High¶
u/Resident-Ad-5419 quantified the limits at approximately $8/session and $64/week on Pro. u/InternalServerError7 consumed an entire session limit and 21% of weekly on a single request that produced wrong output. u/ubla_hua_andaaa hit rate limits at the start of a workday on a Student plan. u/arstarsta (50 score) described scheduling Claude pings at 5 AM so the session limit resets by 10 AM. Coping: upgrade to Max ($100/month), which reportedly provides ~10x rather than advertised 5x capacity, or use model routing to stay on cheaper tiers.
Security Scanning Blocked by Safety Layer -- Medium¶
u/Anthony_S_Destefano documented Opus 4.7 blocking security vulnerability scanning that worked on 4.6, returning an API error citing "violative cyber content." For a user paying $200/month on a Max plan, losing the ability to scan their own code for vulnerabilities is a functional regression with direct security implications. No workaround beyond switching models.
API Key Exposure Risk for Vibe Coders -- Medium¶
u/Opening_Apricot_5419 documented a friend's $1,000 API balance drained overnight from a key in frontend JavaScript. Three leakage paths catalogued: key in frontend bundle, key in git history (even after deletion, scrapers find it within minutes), and key pasted into agent chat that writes it into source. u/goship-tech (22 score): "git rm and even deleting the commit does not remove it from the repo object graph. You need git filter-repo to actually purge it" (A friend had his $1000 API balance drained, score 102, 132 comments).