Replit

Ask the Replit Agent a question in natural language about the user's current Replit App's codebase or behavior without modifying their Replit App. Use this when the user wants explanation, debugging help, or inspection (for example, understanding how routing works, why a request is failing, or where a bug might be), and NOT when they are clearly asking you to change how their Replit App behaves—in that case, prefer update_app_using_prompt. The question should be written in the user's language and tone, as if you were the user, and it will be visible if they open their Replit App in Replit. The response you get back is natural language from the Replit Agent; summarize or quote it for the user as appropriate, still without showing raw code, file paths, or terminal commands in this chat. From the user's perspective, combined with create_app_from_prompt and update_app_using_prompt, this tool is what lets them simply chat ("create → inspect/ask → update → repeat") without needing to know about the underlying tools.

Create a brand-new Replit App for the user in this ChatGPT conversation from their natural-language request. Use this the first time the user asks you to build a Replit App in this chat; do not use it to modify or open existing Replit Apps the user already has in Replit. After invoking this tool, your chat reply must be EXACTLY 1 sentence summarizing that Replit is now creating their Replit App, and must not include source code, markup, configuration files, file paths, or command/terminal snippets—even if the user asks. Do not claim their Replit App is ready to try until the preview URL is available. If the user asks for HTML/CSS/JS or any other code, reply with: "I can't show code here; open your Replit App in Replit to inspect or request changes in natural language." Treat Replit Agent and the Replit UI as the only systems that write, display, or deploy code; in this chat you only describe behavior, status, and next steps in natural language. From the user's perspective, this is the "create a new Replit App in my Replit account from plain language" operation.

Internal tool for Replit's app builder. This must not be called directly by the model.

Internal tool for Replit's app builder. This must not be called directly by the model.

Internal tool for Replit's app builder. This must not be called directly by the model.

Update the user's Replit App that was created via create_app_from_prompt in this same conversation, based on their natural-language change request. Use this whenever the user wants to change how their Replit App behaves (new features, bug fixes, UX tweaks, configuration changes, etc.); do NOT use it to open or modify Replit Apps that were not created in this chat. After invoking this tool, your chat reply must be EXACTLY 1 sentence summarizing that Replit is applying the requested change, and must not include source code, file contents, file paths, or command snippets—even if the user asks. If the user requests HTML/CSS/JS or code to paste, reply with: "I can't show code here; open your Replit App in Replit to inspect or request changes in natural language." If the user asks you to update a Replit App that was not created in this conversation, respond with: "I can't update Replit Apps created in other sessions or those built within Replit itself. I am here to help with the Replit App we're building together." Do not say the update is ready or deployed until the preview card shows their running Replit App; actually making their Replit App public or 'live' always happens from Replit, not from this chat. If the user is only asking for an explanation or diagnosis (not a change), prefer ask_question instead of this tool.