Replit Agent apps hold up when the builder plans in Plan mode before Agent writes code, ends every request in a checkpoint, and tests the published app before real users reach it. The playbook below runs in that order, from the first prompt to the live URL.
When you need this
- Builders get a working first version fast, then later requests break features that worked.
- Spend climbs because every fix runs as a new paid request in Power or Max mode.
- Apps reach real users without anyone checking the published version, its data, or its access settings.
- A builder rolls back after a bad change and loses work, or data, they meant to keep.
The playbook
Before work: plan in Plan mode
Does Agent know what the app must do, and in what order, before it writes code?
In practiceWrite a short brief and turn it into an ordered task list in Plan mode, which reads the project without changing files. Choose Build here or Build in background once the plan is right. Replit recommends starting in Plan mode when a request involves several features. Builders who wrote requirements first report fewer surprises, and Jason Lemkin at SaaStr now decides whether an app can be finished before the first prompt.
Before work: write the rules once
Are approved libraries, security rules, and data-handling policies written down where Agent reads them?
In practicePut the few rules that always apply in Custom Instructions in Workspace Settings, and reusable approaches in Skills. Keep instructions short and specific.
During work: build in checkpoints
Can the builder return to the last good state without losing data they meant to keep?
In practiceKeep requests small so each one ends in a checkpoint. A checkpoint captures files, the conversation, and optionally the development database, and appears as a Git commit. Rollbacks leave the database alone unless you select it, and never restore production automatically. Break large features into background tasks, which run in isolated copies and change nothing until you apply them.
During work: stop the fix loop
Who decides when to stop asking Agent for another fix?
In practiceStop after two failed fixes, roll back, and restate the problem, or read the logs yourself. Practitioners describe the loop this rule prevents. The first prompts work, then Agent loops on one error and spends the plan. Turn on App Testing in Power or Max mode for flows that matter, so Agent checks them in a real browser.
Before publishing: check the live app
Has someone tested the published version as well as the development URL?
In practiceRun the security review before publishing and choose the access level: public, password protected, Workspace only, or invite only. Keep secrets and test data out of the release. After publishing, open the live URL and run the main user journey, then watch Monitoring for failed requests and slow responses.
Pre-publish checklist
- Is live data in the production database, which Agent cannot change, with only test data in the development database?
- Who can open this app today, and is that the access level we intended?
- Have we tested the main journey on the published URL after the last change?
- Which mode and Effort is this work running in, and does the task need it?
- If we need the code outside Replit, is it synced to GitHub or only in the project?
Red flags
- Repeated paid fix requests on the same error with no rollback or restated plan.
- Real user data copied into the development database for testing.
- Apps published publicly by default with no review of access settings.
- No Git remote, so the only history is the checkpoint list inside one project.
Products in this piece
Sources
- Official documentation
- 8
- Public source
- 3
- Replit docs: Plan vs. Build mode
- Replit docs: Build with Agent
- Replit docs: Custom Instructions
- Replit docs: Checkpoints and rollbacks
- Replit docs: Task system
- Replit docs: App Testing
- Replit docs: Publish your app
- Replit docs: Development and production databases
- Jason Lemkin, SaaStr: From Zero to Replit Fluent, 9 apps and 500,000 users (published Oct 20, 2025)
- tluyben2 on Hacker News: first prompts work, then the agent loops on one error (published May 24, 2025)
- r3dditor in r/replit: Agent 4 loops that cost more than US$8,000 in a month (published May 1, 2026)