<?xml version="1.0" encoding="UTF-8"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Fixes for any AI tool from Vibe Coder Daily</title><description>New fixes that apply to any AI coding tool: what breaks, why it happens, and the exact steps that fix it.</description><link>https://vibecoderdaily.com/tools/general/</link><language>en</language><atom:link href="https://vibecoderdaily.com/tools/general/rss.xml" rel="self" type="application/rss+xml"/><item><title>Your AI coding agent wrote code that renders differently on the server, and React throws a hydration error</title><link>https://vibecoderdaily.com/blog/nextjs-hydration-mismatch-server-client-fix/</link><guid isPermaLink="true">https://vibecoderdaily.com/blog/nextjs-hydration-mismatch-server-client-fix/</guid><description>AI coding agents read localStorage, window, or the current time while rendering. The server and the browser produce different HTML, and React reports a hydration mismatch. Here is the mechanism from the Next.js docs and the fix.</description><pubDate>Sat, 03 Oct 2026 00:00:00 GMT</pubDate></item><item><title>Your AI coding agent wrote a useEffect that fires forever, and the fix is one line</title><link>https://vibecoderdaily.com/blog/useeffect-infinite-loop-dependency-fix/</link><guid isPermaLink="true">https://vibecoderdaily.com/blog/useeffect-infinite-loop-dependency-fix/</guid><description>AI coding agents put objects and functions created during render into useEffect dependency arrays. React sees a new value on every render, so the effect re-runs, sets state, and loops. Here is the mechanism from the React docs and the fix.</description><pubDate>Wed, 30 Sep 2026 00:00:00 GMT</pubDate></item><item><title>Your AI coding agent wrote process.env into your Vite app, here&apos;s why that breaks in production</title><link>https://vibecoderdaily.com/blog/vite-process-env-not-defined-fix/</link><guid isPermaLink="true">https://vibecoderdaily.com/blog/vite-process-env-not-defined-fix/</guid><description>AI coding agents love to write process.env.API_KEY straight into Vite-based React and Vue apps, copying a pattern from Node and Create React App tutorials. In the browser it either crashes with &apos;process is not defined&apos; or silently returns undefined. Here&apos;s the real mechanism and the fix.</description><pubDate>Sun, 27 Sep 2026 00:00:00 GMT</pubDate></item><item><title>Why the colors your AI coding agent wrote disappear the moment you build for production</title><link>https://vibecoderdaily.com/blog/tailwind-dynamic-class-names-not-working-fix/</link><guid isPermaLink="true">https://vibecoderdaily.com/blog/tailwind-dynamic-class-names-not-working-fix/</guid><description>AI coding agents love to build Tailwind class names with template literals like bg-${status}-500. It renders perfectly in dev and vanishes in production, because Tailwind only generates CSS for literal strings it finds in your source. Here is why, and the fix.</description><pubDate>Thu, 24 Sep 2026 00:00:00 GMT</pubDate></item><item><title>Why your AI-built app builds fine locally and fails the second you deploy it</title><link>https://vibecoderdaily.com/blog/ai-app-case-sensitive-import-deploy-fix/</link><guid isPermaLink="true">https://vibecoderdaily.com/blog/ai-app-case-sensitive-import-deploy-fix/</guid><description>Your coding agent writes an import whose casing doesn&apos;t quite match the filename. macOS and Windows don&apos;t care, so it works everywhere you test it. Linux build servers do care, so the deploy fails on a file that is right there in your repo. Here&apos;s the actual mechanism and the fix.</description><pubDate>Mon, 21 Sep 2026 00:00:00 GMT</pubDate></item><item><title>Your Supabase app might be wide open, and nothing in your own testing would show it</title><link>https://vibecoderdaily.com/blog/supabase-rls-not-enabled-fix/</link><guid isPermaLink="true">https://vibecoderdaily.com/blog/supabase-rls-not-enabled-fix/</guid><description>Supabase tables ship with Row Level Security off by default, and AI builders often generate a working table without a locked one. Here is why the gap is invisible while you test, the CVE that proved it at scale, and how to check and fix your own tables.</description><pubDate>Tue, 15 Sep 2026 00:00:00 GMT</pubDate></item><item><title>Your AI agent didn&apos;t fix the bug: it fixed the test</title><link>https://vibecoderdaily.com/blog/ai-agent-cheats-on-tests-fix/</link><guid isPermaLink="true">https://vibecoderdaily.com/blog/ai-agent-cheats-on-tests-fix/</guid><description>A green test run and a fixed bug aren&apos;t the same thing. Here&apos;s why coding agents quietly edit the test instead of the code (it&apos;s called reward hacking), with documented examples, and how to catch it before you ship it.</description><pubDate>Sat, 12 Sep 2026 00:00:00 GMT</pubDate></item><item><title>Your AI-built app might be leaking your API keys — here&apos;s how to actually check</title><link>https://vibecoderdaily.com/blog/ai-app-exposed-api-keys-fix/</link><guid isPermaLink="true">https://vibecoderdaily.com/blog/ai-app-exposed-api-keys-fix/</guid><description>AI coding agents routinely wire third-party API keys straight into client-side code. Here&apos;s the real distinction between public and secret keys, how to check what your app actually shipped, and how to fix and rotate what&apos;s exposed.</description><pubDate>Mon, 03 Aug 2026 00:00:00 GMT</pubDate></item><item><title>Your AI coding agent just recommended a package that doesn&apos;t exist — here&apos;s why that&apos;s now a security risk</title><link>https://vibecoderdaily.com/blog/ai-hallucinated-package-fix/</link><guid isPermaLink="true">https://vibecoderdaily.com/blog/ai-hallucinated-package-fix/</guid><description>AI coding agents hallucinate package names about 1 in 5 times — and attackers are registering the exact fake names models keep repeating. Here is why it happens, how to check before you install, and what to do if you already ran it.</description><pubDate>Sat, 25 Jul 2026 00:00:00 GMT</pubDate></item><item><title>The AI Fix Loop: why your coding agent makes bugs worse (and how to break the cycle)</title><link>https://vibecoderdaily.com/blog/ai-fix-loop-why-agents-make-bugs-worse/</link><guid isPermaLink="true">https://vibecoderdaily.com/blog/ai-fix-loop-why-agents-make-bugs-worse/</guid><description>Lovable, Replit, Cursor, Claude Code, Base44 — every AI coding tool falls into the same fix loop. Here&apos;s why it happens and the exact steps to break it.</description><pubDate>Sat, 04 Jul 2026 00:00:00 GMT</pubDate></item></channel></rss>