I just did something my AI agents couldn't

Description and use

The author attempted to refactor an ESP‑IDF project into a components folder, but AI tools failed to update include paths and CMake dependencies. Manual correction of the REQUIRES line resolved the build.

Problem

Automating the organization of an ESP-IDF project into a components folder failed when relying solely on AI tools.

Outcome

Manual inspection of include paths and CMake REQUIRES entries resolved build errors that AI tools could not detect.

Workflow

• 1. Copied project files using ReptClip.
• 2. Asked Gemini (various free/paid versions) to suggest files to move and new code.
• 3. Followed AI instructions blindly, resulting in widespread syntax errors.
• 4. Repeated the process with Gemini Pro, Gemini Flash Extended, Gemini Pro Extended, DeepSeek v4 Flash, DeepSeek v4 Pro, and GitHub Copilot, all failing to resolve errors.
• 5. Took a break, then returned with a new plan: manually edit #include lines and CMakeLists.txt.
• 6. Identified that incorrect REQUIRES/PRIV_REQUIRES names caused header resolution failures.
• 7. Searched Google for the correct REQUIRES entry, updated the line, and rebuilt successfully.

Evidence

I realized right away that the #include paths were the real issue.

Adding those fixed a few headers, but some specific headers still failed.