>_ tool archive
Any AI tool fixes & guides
10 guides · what breaks in Any AI tool, why it happens, and the exact steps that fix it.
Follow fixes that apply to any AI tool
- In a feed reader: paste this address into any RSS reader, such as Feedly, Inoreader or NetNewsWire.
- In Slack: add the RSS app to your workspace, then in a channel type
/feed subscribefollowed by this address. - In Discord: add a feed bot that accepts an RSS address, and give it this one.
New fixes that apply to any AI tool only. The feed collects nothing about you.
History cleared. New tags start again after your next visit.
- New
Your AI coding agent wrote code that renders differently on the server, and React throws a hydration error
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.
Read the fix - New
Your AI coding agent wrote a useEffect that fires forever, and the fix is one line
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.
Read the fix - New
Your AI coding agent wrote process.env into your Vite app, here's why that breaks in production
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 'process is not defined' or silently returns undefined. Here's the real mechanism and the fix.
Read the fix - New
Why the colors your AI coding agent wrote disappear the moment you build for production
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.
Read the fix - New
Why your AI-built app builds fine locally and fails the second you deploy it
Your coding agent writes an import whose casing doesn't quite match the filename. macOS and Windows don'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's the actual mechanism and the fix.
Read the fix - New
Your Supabase app might be wide open, and nothing in your own testing would show it
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.
Read the fix - New
Your AI agent didn't fix the bug: it fixed the test
A green test run and a fixed bug aren't the same thing. Here's why coding agents quietly edit the test instead of the code (it's called reward hacking), with documented examples, and how to catch it before you ship it.
Read the fix - New
Your AI-built app might be leaking your API keys — here's how to actually check
AI coding agents routinely wire third-party API keys straight into client-side code. Here's the real distinction between public and secret keys, how to check what your app actually shipped, and how to fix and rotate what's exposed.
Read the fix - New
Your AI coding agent just recommended a package that doesn't exist — here's why that's now a security risk
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.
Read the fix - New
The AI Fix Loop: why your coding agent makes bugs worse (and how to break the cycle)
Lovable, Replit, Cursor, Claude Code, Base44 — every AI coding tool falls into the same fix loop. Here's why it happens and the exact steps to break it.
Read the fix