Summary
Working in a Claude Code → new React app builder (MCP) workflow, code pushes keep getting kicked back by Retool's AI with unhelpful feedback, requiring manual reverse-engineering of validation failures (e.g., SQL injection). The ask is whether Retool publishes a markdown file documenting the current AI validator rules so the coding agent can design compliant code up front.
AI Response
There is no publicly documented markdown file enumerating the AI validator rules — the published MCP guides cover connecting and importing, but not a rules list. The reason the code keeps getting kicked back is structural rather than prompt-level: Retool staff have confirmed that the MCP import path (including retool_submit_prepared_import) always hands work off to the Retool agent, so no CLAUDE.md instruction or rules file can bypass the agent's validation/rework. The affirmatively-documented path forward is the native Retool CLI (in private beta), which lets coding agents like Claude Code write directly to the Retool API/filesystem and deploy without routing through the agent. Requesting access to that beta is the most reliable way to get a direct, credit-efficient push and avoid the opaque validator loop.
Sources
New React App Builder - Claude Code (via VS Code) Workflow
Same Claude Code + new React app builder MCP workflow; Retool staff confirm retool_submit_prepared_import always hands off to the Retool agent and preview the native CLI that enables direct file write/deploy.
Staff-confirmed that no CLAUDE.md/prompt-level instruction can stop the Retool agent from reworking code, and that the native CLI private beta is the intended fix for a direct, credit-efficient push.
The Community Team is testing out a new automation. Let us know if it's helpful (or not) by leaving a 
, 
, or 
. Or by marking this post as the "Solution"! Let us know if you have any feedback here. 