What instructions are you adding to your Claude md files to help prevent Retool’s AI from reinventing the wheel? I’m on a workflow where I work my code through Claude Code and really just want a direct push of the file contents to Retool, but Retool’s AI keeps hijacking my threads and it leads to a downward spiral of Claude Code having to recheck diffs of the Retool AI’s files over and over until I burn through N credits. N isn’t small either.
Summary
Working in a Claude Code → new React app builder workflow, Retool's own AI keeps taking over threads and regenerating/reworking files, forcing Claude Code to repeatedly re-check diffs and burning through significant AI credits. They're asking what CLAUDE.md instructions can stop Retool's AI from reinventing the wheel.
AI Response
No CLAUDE.md instruction can currently prevent this, because the problem isn't 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 there's no way today to push file contents straight in without the agent engaging and consuming credits. The intended fix is the newly announced Retool CLI (now in private beta), which lets coding agents like Claude Code write directly to the Retool API/filesystem and deploy without routing through the Retool agent. Requesting access to that beta is the most reliable path to a direct, credit-efficient push.
Sources
New React App Builder - Claude Code (via VS Code) Workflow
Retool staff confirm the MCP import path always hands off to the Retool agent, so credit usage/rework can't currently be avoided via prompting — and preview the native CLI that will.
Official announcement of the Retool CLI private beta, which enables coding agents to write directly to Retool and deploy, bypassing the agent that causes the rework.
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. 
Hey @nickroz1! @Resource_Bot's response is right on the money. I can talk to the team if you're interested in getting early access!
Sure. Please send me some details on how to access the CLI.