Skip to main content
Paige automatically tracks every change the AI makes to your bot code. Each save creates a commit — a snapshot of your bot at that moment in time. You can browse this history, inspect what changed in any commit, and restore your bot to a previous version if something goes wrong. There’s no manual saving required.

​
How commits work

Every time you ask the AI agent to change your bot code and it saves those changes, a commit is recorded. Each commit holds a complete snapshot of your code at that moment, so you always have a full record of how your bot evolved. The message on a commit is the request you typed. If you asked “add a confirmation step after booking,” that’s what you’ll see in the history — which makes the list read like a log of what you asked for. One reply from the agent produces one commit, however many files it touched along the way.
Commits are created automatically by the AI when it saves code. You don’t need to do anything to enable version history — it’s on for every project.

​
View your commit history

1

Open your project

From the Paige dashboard, select the project whose history you want to review.
2

Open the history panel

Click the History icon in the header, just to the right of the Paige logo. Version history opens in place of the chat sidebar, listing every commit for this project from newest to oldest. Click the icon again to switch back to chat.
3

Open a commit

Click any commit to expand it. You’ll see the request that produced it, when it happened, and which files changed — grouped into added, modified, and deleted. The commit that’s currently live on your WhatsApp number is marked with a green Live tag.

​
Restore a previous version

If a recent change broke your bot or you want to go back to an earlier working state, you can restore any commit.
1

Find the commit to restore

Browse your commit history and open the commit you want to revert to. Review the diff to confirm it’s the right version.
2

Click Restore this version

Expand the commit and click Restore this version, then Confirm. Paige rewrites your working copy back to that snapshot.
3

Confirm your bot is working

Use Paige Dev to send a test message and verify the restored version behaves as expected.
4

Deploy when you're happy

Restoring doesn’t reach your customers on its own. Click Deploy once you’ve confirmed the restored version works.
Restoring changes your working copy only — the version your customers are talking to keeps running untouched. That’s what makes restore safe to reach for: you can go back, look around, and test through Paige Dev without anyone on the outside noticing.

​
After a restore

Your history is never rewritten. Restoring doesn’t delete newer commits and it doesn’t rewind a pointer — it records the restore as a new commit on top, named Restored to followed by the short ID of the commit you went back to. If the AI makes further changes afterwards, those stack on top as normal. Two things you’ll notice straight away:
  • The Deploy button picks up an orange dot, because your working copy no longer matches what’s live.
  • The green Live tag stays where it was — on the commit you last deployed, not on the one you just restored. That’s the panel telling you the restore hasn’t gone out yet.
Both resolve once you deploy.
If you want to experiment with a change without risk, describe the change to the AI agent and ask it to explain what it plans to do before saving. Once you’re confident, tell it to go ahead.