Skip to main content
These answers cover working with Agent. For full reference, see the Agent overview, Agent modes, and AI billing.
  1. Open the Shell pane in your project—not the Agent chat.
  2. Type kill 1 and press Enter to stop the frozen process. (kill 1 is safe in Replit—it restarts your project’s main process, it doesn’t delete anything.)
  3. Open a new Agent chat and describe your task again to continue.
While Agent looks frozen, stop sending messages—extra messages create conflicting instructions. If Agent keeps freezing on the same task, break the work into smaller, focused prompts.
  1. Select Stop in the Agent panel to halt it immediately.
  2. Open the Shell pane (not the Agent chat), type kill 1, and press Enter.
  3. Open a new Agent chat and rephrase your task more specifically.
To avoid loops:
Three settings make the biggest difference:It also helps to start a new Agent chat when you switch tasks and use Plan mode to scope work first. Check your usage dashboard to see which tasks cost the most.
Agent has three top-level modes plus an optional speed toggle. See Agent modes for full guidance.
  • Lite—fast, lightweight models for quick, scoped edits.
  • Economy—optimized for cost; a strong default for everyday builds.
  • Power—the most capable models for complex tasks and larger codebases.
  • Turbo—a toggle in Advanced settings, available in Power mode, that runs the fastest models. It’s significantly faster but costs more, so use it intentionally.
Separately, Plan mode lets Agent scope work before making changes, while Build mode applies changes directly. See Plan vs. Build mode. All modes use credits, including Plan mode reasoning.
Replit saves checkpoints as Agent works. In the Agent chat, find the message before the change you want to undo and select the rollback option next to it to restore your project to that point.For full rollback options—including recovering specific files and live deployments—see Checkpoints and rollbacks.
During the build and edit phase, Agent works in a sandboxed environment with restricted outbound access. Your deployed app can still make external API calls when it runs—the sandbox applies to Agent’s editing environment, not your running app.If an API call fails in your running app, confirm your keys are saved in the Secrets pane, then check the provider’s status page. On a corporate or school network, outbound connections from your app may be blocked—check with your network admin.
Yes. Add your keys to the Secrets pane and your app uses them for its API calls. Open the Secrets tool, select + New secret, and enter a name (such as OPENAI_API_KEY) and value.You can bring your own AI provider keys for the models your app calls. The model that powers the Agent experience itself runs on Replit’s infrastructure and can’t be swapped.
Keep Agent focused with tighter prompts:
  • Start with the word Only—for example, “Only add a delete button to the user card. Don’t change anything else.”
  • Use Plan mode first to review what Agent intends to do before it changes anything.
  • If Agent makes an unwanted change, ask it to undo that change in the same chat right away.
For more, see Effective prompting.

Still need help?

If your Agent question isn’t answered here, contact Replit Support.