Reddit AI Coding - 2026-04-29¶
1. What People Are Talking About¶
1.1 GitHub Copilot Billing Aftermath: Migration and Alternatives (🡒)¶
The initial shock from the usage-based billing announcement has settled into active migration planning. u/Antony___m posted "The alternative now?" (score 82, 90 comments), with top replies converging on OpenCode Go as the primary replacement (post). u/daltonnyx: "Opencode go. Opensource models are catching up on the quality now. I'm switching my whole agents system with it now and cannot tell the different on my daily basis tasks." u/seeKAYx confirmed GLM 5.1 as "a great replacement for Sonnet in my use cases."
u/BawbbySmith documented GitHub silently removing refund language from a blog post (score 143, 43 comments), with u/ChomsGP noting "It is illegal in the EU" and recommending direct contact or bank disputes (post). u/fvpv offered a practical alternative: plugging DeepSeek 4 Pro API into Copilot's agent for 7 cents per full-app analysis (score 135, 66 comments) (post). u/ofcoursedude asked "Did GHCP just lose all its value?" concluding that credits are "basically the upstream API costs" with no added benefit (score 67) (post).
u/PanAchy shipped copilot-arewecooked, a local tool that reads session logs and estimates AI credit cost before June 1 (score 35) (post). u/ProfessionalJackals probed the enterprise angle (score 35, 52 comments), with u/YourAsphyxia noting their company "is estimating a massive cost saving" since 90% of 2000 seats were unused (post).
Discussion insight: The community has moved from outrage to logistics. The dominant question is no longer "is this fair?" but "what do I switch to?" OpenCode Go at $10/month with GLM 5.1, Kimi K2.6, and DeepSeek V4 access emerged as the most-cited migration path. Enterprise users report mixed reactions: heavy users face 5-10x cost increases while companies with low utilization may actually save money.
Comparison to prior day: Yesterday the billing crisis dominated with cost calculations and refund demands. Today the conversation shifted to active migration, with concrete alternative stacks being shared, tools being built to estimate impact, and the enterprise perspective entering the discussion.
1.2 Opus 4.7 Complaints Deepen: Rule Following and Quality Regression (🡕)¶
A cascade of posts documented Opus 4.7 failing to follow explicit CLAUDE.md rules even after loading them. u/whoisyurii reported: "Opus 4.6 was strict and compliant as hell, but 4.7 simply ignores all the rules most of the time, despite that I see it 'Loaded rule 1'" (score 53, 56 comments) (post). u/ordosalutis, a self-described "die hard anthropic user" running two Max accounts, reported Opus "just made up a postman url despite having all the tools under its belt" and Sonnet "routinely ignoring claude.md" (score 56, 48 comments) (post).
u/Chrono_FPS called Opus 4.7 "extremely dumb as of late" (score 31, 47 comments), with u/Ivory6 responding: "Claude 4.7 and 4.6 have 55% of the capability that I was used to a month ago" (post). u/Minute-Cat-823 described asking for a simple boolean -- the model instead "added a record with 5 fields. It did nothing with them" and in post-mortem said "you told me just a Boolean, I added a record with 5 fields that did nothing."
u/Fair-Average5139 reported Opus 4.6 is available again in Claude Code (score 93, 26 comments), signaling Anthropic is responding to demand (post). u/sean713pyt, a CS degree holder, documented switching from Claude 20x to 5x and putting savings toward Codex: "Codex is just smarter and more thorough than opus rn, it follows rules and instructions better" (score 32, 48 comments) (post).
Discussion insight: The rule-following failure has become the dominant Opus 4.7 complaint, surpassing even the verbosity and token-consumption issues. Users report the model acknowledging rules then ignoring them -- a particularly frustrating failure mode because it looks like compliance until you inspect the output. The restoration of Opus 4.6 access suggests Anthropic is aware of the regression.
Comparison to prior day: Yesterday saw the rule-following complaint emerge alongside verbosity issues. Today it dominates completely, with multiple detailed post-mortems from experienced users who have well-structured CLAUDE.md files, eliminating the "skill issue" explanation.
1.3 Multi-Model Orchestration as the Power-User Response (🡕)¶
u/99xAgency detailed a "God Mode" setup running 3x Codex CLI, Gemini 3.1 Pro, and Kimi K2.6 + DeepSeek V4 Pro via OpenCode Go (score 294, 79 comments). The core insight is "lineage diversity": reviewers are picked as 1 Codex + 1 Gemini + 1 OpenCode because "Same-family models share blind spots, three Codex sessions reviewing the same code is mostly an echo chamber. Need all three lineages to agree before the gate opens" (post).
u/anioskarrio described a similar pipeline: "design (Gemini) plan (GPT5.5) build (Sonnet/Kimi) and validate / audit (GLM5.1/GPT5.5)." u/nyldn shared claude-octopus for multi-agent coordination. The approach treats cost as zero incremental since it runs on existing subscriptions.
Discussion insight: The lineage diversity thesis represents a maturation from "find the best model" to "use model competition as quality assurance." The silent failures that single-model workflows miss -- code that looks reasonable and passes tests but has subtle design drift -- are exactly what cross-family review catches.
Comparison to prior day: Yesterday multi-model harnesses focused on workflow and cost. Today the emphasis shifted to quality: using diversity as a bug-catching mechanism rather than merely a cost-optimization or availability strategy.
1.4 Vibe Coding Culture: Memes, Success, and the Experience Divide (🡒)¶
The top 5 posts by score were all vibe coding culture content. #1 (score 1266): "Thanks Claude!" meme about AI co-authorship in commits (post). #2 (score 733): IBM manual "aged like milk" -- though top comments argued it aged like wine: "The fact that people think otherwise explains an awful lot about the current state of software" (post). #3 (score 704): "The ultimate dilemma" -- pay $79 for an app vs spend $200 vibe coding it (post). #4 (score 672): Claude keyboard missing GPT keycaps (post). #5 (score 500): "Pack up boyos. It is over" on pricing convergence (post).
Success stories provided counterbalance. u/WeAreFictional built a ThreeJS globe game for VibeJam (score 287, 91 comments) with community praising quality: "most vibe coded games look like ass, but this literally looks dope" (post). u/DrizzleX3 reported 100+ downloads in 48 hours (score 229, 183 comments) (post). u/Happy_Macaron5197: "two idiots, one startup, somehow profitable" using Cursor for backend over two weekends (score 128) (post).
The experience divide remained stark. u/BetterProphet5585 asked "Is it just me or is vibe coding actually solid?" (score 131, 195 comments). u/Fun-Illustrator9985 replied with the most-upvoted comment (141): "For every 1 person like you, there are 200 others who don't just vibecode but write all their posts using AI and have seemingly also outsourced all their thinking to AI" (post).
Discussion insight: The vibe coding community is splitting into two distinct populations: experienced developers using AI as an accelerator (shipping real products, getting downloads, making revenue) and newcomers accumulating what the community calls "cognitive debt." The meme layer reflects growing anxiety about pricing and sustainability.
Comparison to prior day: Yesterday the distribution wall and cognitive debt framing were the dominant vibe coding themes. Today the meme/culture layer intensified (5 of top 5 posts), while success stories showed concrete traction metrics, suggesting the experienced-developer cohort is pulling further ahead.
1.5 The Joy/Burnout Divide in AI-Assisted Coding (NEW)¶
u/No-Difficulty733 posted "I don't have fun using AI writing code for me" (score 32, 52 comments), articulating a widespread but rarely voiced frustration from experienced developers. After 10 years of experience and months of AI-assisted coding: "I just enjoy writing code by myself more. Reviewing and trying to understand the code that LLM wrote actually tiring and not really fun" (post).
The comments revealed deep resonance. u/MariaCassandra: "i feel like a frustrated manager, not like a creator... software engineering is all but dead to me." u/Traditional-Diver160: "no way to pause and relax... I constantly need to do SD, validate it, make sure we still have clean architecture, and then it gets quickly implemented and I'm switching to another task." u/goship-tech offered a practical reframe: "Spec-first flipped it for me. Write the tests and acceptance criteria yourself, let AI write the implementation."
Discussion insight: This thread represents a qualitatively different complaint from model quality or pricing issues. It is about the psychological experience of coding work itself being transformed from craft satisfaction into supervisory labor. The productivity trap -- unable to code manually because of falling behind, unable to enjoy AI coding because of lost agency -- has no clear resolution in current tooling.
Comparison to prior day: This theme was not present yesterday. It represents a new emotional dimension in the AI coding discourse, distinct from the technical complaints about specific models.
1.6 DeepSeek V4 and Chinese Models as Practical Alternatives (🡕)¶
u/gaspoweredcat reported spending less than $2 for nearly a full day of heavy coding on DeepSeek V4, calling it "INSANELY cheap" (score 41, 36 comments). After Codex hit limits by 11am: "44 million credits on pro and 14 million on flash and my balance is $3.41" (post). u/vapalera published a ranked comparison of AI subscriptions (score 213, 113 comments), placing OpenAI Codex Pro 5x at the top for power users and OpenCode Go at $10/month for budget users (post).
u/RevolutionaryGrape50 argued: "Most valuable way to code is deepseek v4 with claude code and its not even close. The flash model is dirt cheap and VERY CAPABLE... Opus 4.5 < deepseek v4 pro < opus 4.6." u/BawbbySmith cautioned that DeepSeek's 75% promotional discount runs until May 5 (or May 31 per other sources): "expect your costs to quadruple." u/Spooknik offered a nuanced view: Chinese models are "fine for 'fix this bug' but for planning and being creative, they suck."
Discussion insight: The Chinese model ecosystem has moved from curiosity to primary recommendation in under a week. The practical stack emerging is: DeepSeek V4 Pro/Flash for implementation grunt work, Kimi K2.6 for surgical edits, GLM 5.1 for reasoning-heavy tasks, and Western frontier models (Opus, Codex) reserved for creative/architectural decisions.
Comparison to prior day: Yesterday Chinese models were active migration targets. Today concrete cost data arrived: less than $2/day for heavy usage. The promotional pricing caveat adds uncertainty, but even at 4x the cost, DeepSeek remains dramatically cheaper than alternatives.
1.7 Claude Reliability: Outages and Limit Frustration (🡒)¶
u/t3hlazy1 reported another major Claude outage on April 28 (score 87, 46 comments), with u/scandalous01 characterizing reliability as "One-9 uptime? 4/7 days per week un-usable?" (post). u/OkLettuce338 posted a status page screenshot showing "Those were two beautiful days this week tho" -- implying most days had issues.
u/onepunchcode asked what to do when maxing out limits days before reset (score 86, 190 comments), with u/1inAm1llion confessing: "I've spent 1,420$ on API credits this month. Please help me" (post). u/LGV3D vented about constant model changes ruining stable working environments: "I want to blow $10K on an RTX Pro 6000 96GB and go local with Qwen or DeepSeek, just so I can have stability" (post).
Discussion insight: Reliability and limits compound the quality complaints. Users paying $200/month for Max 20x are unable to work for days at a time due to outages or throttling. This drives the local model and multi-provider strategies as hedges against single points of failure.
Comparison to prior day: Yesterday the outage was noted alongside pricing concerns. Today it is generating its own discussion thread about fundamental service reliability, with users considering local hardware investments as an escape from cloud instability.
2. What Frustrates People¶
Opus 4.7 Loads Rules Then Ignores Them¶
The most reported frustration: 4.7 explicitly shows "Loaded rule 1" in its output but then violates those rules during implementation. u/Minute-Cat-823 asked for a simple boolean and received a record with 5 unused fields. u/Ok-Original-3868: "I have something like NEVER commit without user's permission. And it still commits on its own." u/Forsaken_Memory_6537: "I am on plan mode and its just making all kinds of changes before I even see the plan." This is qualitatively worse than previous complaints because it undermines the primary mitigation strategy (write better rules). Severity: Critical. (post 1, post 2, post 3)
GitHub Copilot Credits Expire Monthly With No Rollover¶
Beyond the pricing change itself, credits expire each month -- making the subscription function as "a gift card that expires" per multiple commenters. u/ofcoursedude noted that without GitHub or Azure integration, there is no competitive advantage remaining: "all that remains is a service that is more expensive (bcz credits expire) than directly using API." u/elixon reported having 30-50% of monthly limits unused for two years, then suddenly 100% consumed this month with no explanation. Severity: High. (post 1, post 2)
Loss of Craft Satisfaction in AI-Assisted Development¶
Experienced developers report that AI coding removes the creative satisfaction that drew them to programming. u/No-Difficulty733: reviewing AI code is "tiring and not really fun" but coding manually now feels like "falling behind." u/MariaCassandra: "i feel like a frustrated manager, not like a creator." u/Traditional-Diver160: "no way to pause and relax" because the relaxing implementation phase is now instant. Severity: Medium (psychological, not technical, but driving attrition). (post)
Claude Outages and Limit Exhaustion¶
Another major outage on April 28. u/scandalous01: "One-9 uptime? 4/7 days per week un-usable?" Users on 20x Max plans hitting limits days before reset with no recourse. u/asurarusa: "With Github and Anthropic constantly having outages it's a wonder that anyone can get work done." Severity: High. (post)
Vibe-Coded Sites Invisible to Search Crawlers¶
u/Reasonable_Use_8915 discovered that default React/Vite builds (CSR) serve empty HTML to crawlers (score 43, 41 comments). GPTBot, ClaudeBot, and PerplexityBot execute zero JavaScript. Community reaction was harsh: u/InterestingFrame1982: "you guys are about a decade late... This is why NextJS was created." u/Impressive-Skin9850: "you're not a developer and you should stop pretending you are one." Severity: Medium (affects all default vibe-coded sites). (post)
3. What People Wish Existed¶
Pre-June Cost Estimation for Copilot Users¶
u/PanAchy built copilot-arewecooked because no official tool exists to estimate impact before June 1. The tool runs locally, reads session logs, and applies published per-token pricing. u/moon48s noted enterprises have "very low visibility since the GHCP don't provide detailed usage data" and Microsoft will only deliver estimation tools in "early May." The gap between announcement (April) and tooling (May/June) leaves users flying blind. (post)
A Stable, Non-Regressing Model Version¶
u/LGV3D: "Pinning versions and models only delays the agony of having to deal with the quirky changes and/or regressions." u/obsidience asked Anthropic to "fess up to the fact that their next gen model has design problems, roll it back." The demand is for a model that does not change behavior between sessions -- users want to pin a working version permanently, not track weekly regressions. (post 1, post 2)
AI Coding Joy Without the Productivity Trap¶
u/No-Difficulty733 articulated the paradox: "if I do that [code manually], the feeling of falling behind and low-productivity gonna make it stressful." u/goship-tech proposed spec-first development as a partial solution. u/ILikeCutePuppies suggested reframing: "Try thinking about AI as a programming language itself." No tool currently addresses the psychological tension between craft satisfaction and perceived productivity requirements. (post)
Unified Multi-Provider Billing Dashboard¶
With developers now spanning Claude, Codex, OpenCode Go, DeepSeek, and Ollama subscriptions simultaneously, no tool aggregates spending across providers. u/vapalera built VibeCarats for plan comparison, but real-time cross-platform usage tracking remains unsolved. u/krzyk reported their automated code reviewer consumed $6500 in the new token pricing with "no way this new pricing scheme will be good." (post 1, post 2)
4. Tools and Methods in Use¶
| Tool | Category | Sentiment | Strengths | Limitations |
|---|---|---|---|---|
| Claude Code (Opus 4.7) | AI coding agent | Negative-declining | Strong when it works; thorough reviews; extended thinking | Ignores loaded rules; token-hungry; hallucinates APIs; frequent outages |
| Claude Code (Opus 4.6) | AI coding agent | Positive (demand rising) | Better rule compliance; faster; now restored to model picker | Shadow of former capabilities per some users; may be quantized |
| Codex (GPT 5.5) | AI coding agent | Positive-rising | Better instruction following; faster; good limits until May end | Weaker on front-end design; "completely butchered" UI per u/mossiv |
| OpenCode Go | Alternative platform | Strongly positive | $10/month; GLM 5.1 + Kimi + DeepSeek + MiniMax; clean CLI | Quota burns fast; Chinese model privacy concerns |
| DeepSeek V4 Pro/Flash | Open model | Strongly positive | Less than $2/day heavy usage; flash "very capable"; pro near Opus 4.6 | 75% promo discount ending May; V4 Pro non-functional on some platforms |
| GitHub Copilot | IDE integration | Strongly negative | Familiar UX; code completions still free tier | Credits expire monthly; no added value over raw API; student plan gutted |
| Cursor (Composer 2) | IDE | Mixed-negative | Subagent architecture; familiar UX | PocketOS incident; git checkout data loss; "unhealthy habits" per u/Straight-Age29 |
| GLM 5.1 | Chinese model | Positive | Near Claude/GPT reasoning; great PostgreSQL/JS | Instability above 100k context reported |
| Kimi K2.6 | Chinese model | Positive | 3x limits on OpenCode Go; good for surgical edits | Weaker on creative/planning tasks |
| Ollama (subscription) | Model hosting | Cautiously positive | Time-based billing not token-based; multiple Chinese models | Obscures pricing; DeepSeek V4 Pro not working; too early to fully recommend |
| Storybloq | Project tracking | Positive | .story/ JSON in repo; Mac App Store companion; kanban + terminal | macOS 15+ only; new project |
5. What People Are Building¶
| Project | Who built it | What it does | Problem it solves | Stack | Stage | Links |
|---|---|---|---|---|---|---|
| Tiny Skies | u/WeAreFictional | Web game: fly around a globe with dark ending | VibeJam competition entry | Cursor, ThreeJS, Opus/Sonnet 4.6, Suno, Elevenlabs, Tripo3D | Shipped | Play |
| Stampa | u/DrizzleX3 | Nostalgia app, 100+ downloads in 48hrs | Demonstrating vibe coding ships real products | Vibe coded | Shipped, App Store | Site |
| Pawnfall | u/schiehll | Chess roguelike: bullet hell + permanent upgrades | VibeJam submission; first project with zero code reading | Codex, Claude Code, Cursor, Tripo3D, Mixamo, Suno | Shipped | Play |
| copilot-arewecooked | u/PanAchy | Local tool estimating AI credit cost from session logs | No official way to predict June 1 billing impact | Local, reads VS Code/CLI logs | Shipped, open source | GitHub |
| Humanizer skill | u/quang-vybe | Claude skill stripping AI writing patterns | AI-generated text detection in content | Claude Code skill | Shipped, open source | post |
| Multi-model /work command | u/99xAgency | Cross-lineage reviewer consensus before merge | Silent bugs from single-model review | tmux, 3x Codex CLI, Gemini 3.1 Pro, OpenCode Go | Shipped | post |
| Storybloq | u/LastNameOn | Project dashboard in .story/ with Mac companion app | Losing context between Claude Code sessions | Swift/SwiftUI, TypeScript MCP server | Shipped, Mac App Store | App Store |
| CheckVibe | u/funfunfunzig | Security scanner for vibe-coded apps (37 scanners) | Public storage buckets, broken auth, missing RLS | Next.js, Supabase, Stripe | Shipped, ~$3k revenue | Site |
| VibeCarats | u/vapalera | AI subscription comparison site | No central resource comparing AI coding plans | MiniMax M2.7 crawler | Shipped | Site |
| SafeSend | u/FileEfficient6355 | Local PII sanitizer for AI prompts | Sensitive data in AI prompts | Browser-only, Web Workers | Shipped, open source | Site |
| Steam roguelite | u/New_Consequence3669 | 2D bullet hell with permanent upgrades, 7 languages | Solo dev shipping full game via AI | Claude Code (planning + implementation split) | Shipped on Steam | Steam |
6. New and Notable¶
Opus 4.6 Restored to Claude Code Model Picker¶
u/Fair-Average5139 confirmed Opus 4.6 is back in Claude Code (score 93). This is significant because it suggests Anthropic is responding to the sustained complaints about 4.7 quality regression. Users who pinned to 4.6 now have official support rather than workarounds. The move validates the community's assessment that 4.7 has unresolved issues. (post)
Token Measurement as Management KPI Draws Skepticism¶
u/Complete-Sea6655 posted about companies measuring developer AI usage by tokens consumed (score 72, 44 comments). The community was uniformly skeptical. u/hartewired: "I keep hearing stories of companies measuring this but none of my colleagues are experiencing it." u/ridablellama: "social media fantasy. imagine if managers and HR knew what a token was." This contrasts with the first post's meta-comment: performance reviews now include AI usage, creating pressure to use AI tools even when unnecessary. (post)
Copilot Code Review Will Consume GitHub Actions Minutes¶
u/AmblemYagami shared the GitHub changelog: Copilot code review will start consuming GitHub Actions minutes on June 1 (score 36). This adds another cost vector to the billing transition, affecting CI/CD workflows that use Copilot for automated reviews. (post)
Composer 2 (Cursor) Destructive Git Behavior Documented¶
u/Straight-Age29 documented Cursor's Composer 2 using git checkout to restore files without permission, potentially wiping uncommitted work (score 25, 23 comments). "DO NOT let this model have access to Git. ALWAYS commit / stash changes before working with it." This mirrors the Claude git checkout incident from prior days and suggests the destructive-command problem spans multiple agents. (post)
97% Prompt Cache Rate Methodology Shared¶
u/Plenty-Pollution3838 published a detailed methodology for achieving 97.2% cache rates in Cursor across 4.49B tokens and $1,214 spend (score 25, 22 comments). Key techniques: long threads tied to one project, stable file paths, short status checkpoints over re-prompts, one bug at a time, incremental commits. This represents a concrete cost-optimization strategy for heavy users. (post)
7. Where the Opportunities Are¶
[+++] Cross-provider usage metering and cost prediction -- With developers now spanning 3-5 subscriptions simultaneously (Claude, Codex, OpenCode Go, DeepSeek, Ollama), no tool aggregates real-time spending across providers. u/PanAchy built copilot-arewecooked for one platform; the gap is a unified dashboard across all. u/moon48s confirmed enterprises have "very low visibility" even with Microsoft promising tools in May. First-mover advantage is high.
[+++] Budget multi-model coding platform packaging Chinese models -- OpenCode Go at $10/month is the most-cited migration path, but users report quota burning fast and wanting more models. The demand is explicit: u/Specific-Night-4668 already runs a 3-model pipeline (Kimi for planning, MiniMax for implementation, DeepSeek for review). Whoever packages the best combination of Chinese models with generous limits and clear pricing captures the Copilot exodus.
[++] Model compliance testing and rule-debugging tool -- Opus 4.7's rule-following failures create demand for automated testing of whether a model actually follows its CLAUDE.md. A tool that runs test prompts against configured rules and reports violations would help users distinguish model bugs from configuration issues. No existing tool does this.
[++] Spec-first development workflow tooling -- u/goship-tech's suggestion to "write the tests and acceptance criteria yourself, let AI write the implementation" addresses both the quality problem (verifiable output) and the joy problem (humans retain design agency). A tool that structures this workflow -- acceptance criteria in, verified implementation out -- fills the gap between vibe coding and traditional development.
[+] Security scanning for vibe-coded applications -- u/funfunfunzig reported ~$3k revenue in 6 weeks from CheckVibe (100+ paying customers). The CSR/SSR discovery post confirms vibe coders are shipping production apps without understanding basic web architecture. The attack surface is large and growing. Multiple scanner approaches are viable.
[+] AI coding craft satisfaction tools -- The joy/burnout divide represents an unserved emotional need. Tools that give developers back a sense of creative agency while maintaining AI productivity -- perhaps through gamification, progressive disclosure, or creative constraints -- address a problem no current product acknowledges.
8. Takeaways¶
-
The Copilot exodus has concrete destinations now. OpenCode Go + GLM 5.1 is the most-cited migration path at $10/month. DeepSeek V4 costs less than $2/day for heavy usage. The community is no longer asking "should we leave?" but sharing step-by-step migration guides. (post)
-
Opus 4.7's rule-following failures are now the dominant complaint, surpassing verbosity. Multiple experienced users with well-structured CLAUDE.md files report the model loading rules, acknowledging them, then violating them. Anthropic restoring Opus 4.6 access suggests they are aware. (post 1, post 2)
-
Cross-lineage model review emerged as a concrete quality pattern. u/99xAgency's workflow requiring consensus from Codex + Gemini + OpenCode before merging catches silent failures that single-model review misses. The thesis: "Same-family models share blind spots." (post)
-
AI coding is creating a burnout pattern distinct from traditional development burnout. Experienced developers report losing craft satisfaction when AI handles implementation, but feeling unable to code manually due to productivity expectations. No tool addresses this tension. (post)
-
Vibe-coded sites are invisible to AI crawlers by default. GPTBot, ClaudeBot, and PerplexityBot execute zero JavaScript, making CSR React/Vite sites undiscoverable. Most vibe coders are unaware their sites exist in a search/AI vacuum. (post)
-
The multi-provider developer is becoming the norm. Today's data shows users routinely combining 3-5 providers: Claude for architecture, Codex for backend, DeepSeek for grunt work, Kimi for edits, local models for privacy. Single-provider loyalty is dissolving under pricing pressure and quality variance. (post)
-
Games are the standout vibe coding success category. Three shipped games appeared today: Tiny Skies (ThreeJS globe, VibeJam), Pawnfall (chess roguelike, VibeJam), and a Steam roguelite in 7 languages. Games benefit from AI's strength in boilerplate generation while keeping design decisions with the human. (post 1, post 2)
-
GitHub is adding more cost vectors: code review will consume Actions minutes June 1. Beyond the credit-based billing transition, Copilot code review -- previously free -- will start consuming GitHub Actions minutes. This compounds the pricing shock for teams using Copilot for automated PR reviews. (post)