Replit Agent stuck working: Stop, Cancel and rollback explained
For a Replit Agent turn that is stuck working or repeating a failed edit, select Stop in the status bar to interrupt the active turn, then inspect the work already saved. Do not confuse Stop with Cancel on a background task: Replit says Cancel discards that task's isolated work and cannot be undone. Check the task state and checkpoints before any destructive action. Replit steer and queue messages guide.
Sources checked: October 9, 2026.
Stop the active turn and inspect what survived
Select Stop in the status bar. Replit documents this as interrupting the current active turn so you can send another message without waiting for the turn or queued messages to finish. It does not document Stop as a guarantee that every unfinished edit was checkpointed.
Before asking Agent to retry, inspect the actual files and copy the specific failing output. Record which changes you want to retain. Treat repeated failed attempts or circular edits as a reason to narrow the next request, not proof of a particular infrastructure failure. Replit decision-time guidance.
Open the Agent tab in the Project Editor and review checkpoint descriptions. The history icon in Agent chat opens the checkpoint timeline. Identify the last version that you have actually tested before deciding whether to roll back. Replit checkpoints and rollbacks guide.
Check background-task state before Cancel
On the task board, Active means work is running in an isolated project copy. Queued means it is waiting for a prerequisite or an active-task slot. Ready means it has finished but has not yet been applied to the main version. Replit task lifecycle guide.
For Ready work, inspect the work log, tests and preview before selecting Apply changes to main version. Background tasks do not update the main version automatically. Replit task system guide.
Cancel permanently stops an Active, Queued or Ready task and discards its in-progress work without applying it to main. Archive is for a Draft that has not started building; that planning session can be restored from Done. Copy anything you need before using Cancel.
Roll back only when you want to undo saved changes
In the Agent tab, select the intended checkpoint and choose Rollback to here. Read the warning before confirming: later code changes are removed from the restored project state. This is not a way to recover discarded, uncheckpointed background work.
Development database restoration is optional: select Database under Additional rollback options only if you intend to restore it. By default a rollback leaves the database unchanged; production database restoration is a separate procedure.
After restoring, verify the files and the app behavior you need. Give the next request one failing case and the expected result, instead of asking Agent to repeat the whole unsuccessful task.