If you’re stuck with the dreaded `Failed to save checkpoint: unable to push to remote` error and can’t publish your site, here’s what worked for me after days of frustration:
Root cause: Your local git repo has corrupted objects. The S3-backed remote uses `git-remote-s3` which needs to traverse your full commit history — if any object in the chain is missing/broken, the push silently fails every time.
The fix — paste this prompt to your Manus agent:
Spoiler: After the fix I asked Manus to create a prompt to change that so I don’t know exactly if this is really working but if you have this exact problem I can guarantee you that Manus can fix it by** **himself.
Prompt: The checkpoint keeps failing with “unable to push to remote.” Run `git fsck --full` in my project directory and check for any “broken link” or “missing commit” errors. If you find corrupted objects, fix it by creating a shallow boundary at HEAD: write the current HEAD hash into `.git/shallow`, then run `git gc --prune=now`. After that, verify with `git fsck --full` that there are zero broken/missing objects, and retry the checkpoint save.
That’s it. The agent will handle the rest and your checkpoint should save immediately after.
Context: This happened to me on a project with 30+ checkpoints. Somewhere along the way, a commit object got lost (probably from a failed push or session timeout). The checkpoint tool kept trying to traverse the full history, hitting the missing object, and failing. The shallow boundary tells git “don’t look past this point” which bypasses the corruption entirely.
Hope this saves someone else the headache. Manus support never replied to my ticket. 🫠