Skip to main content

Versioning

Versions are full snapshots of your app (tools, mock data, endpoints, and configuration) saved at a point in time. Create a version before making risky changes so you can always roll back to a known good state.

What a Version Includes

Each version snapshot captures:

Create a Version Snapshot

1

Open version history

In your app, click Versions in the left sidebar to open the version history panel.
2

Click 'Create Snapshot'

Click the Create Snapshot button at the top of the version history panel.
3

Add a description of what changed

Write a short, specific description. Focus on what changed and why.Good examples:
  • “Added order lookup tool with pagination support”
  • “Switched auth from API key to OAuth2 before demo”
  • “Removed deprecated inventory endpoint”
Bad examples:
  • “Update”
  • “Changes”
  • “v2”

Restore a Previous Version

1

Browse version history

Open the Versions panel. Each entry shows the description, timestamp, and who created it.
2

Select the version to restore

Click on the version you want to return to. A preview shows what the app looked like at that point.
3

Confirm the restore

Click Restore This Version. Chippy replaces the current app state with the selected snapshot.
Restoring does not delete your current state. Chippy automatically creates a snapshot of the current state before restoring, so you can undo the restore if needed.
4

Verify the app works as expected

Open Preview and run through your key test scenarios. Confirm that tools, mock data, and endpoints behave correctly after the restore.

When to Create Snapshots

Create a snapshot at each of these moments:

Writing Good Descriptions

Treat version descriptions like release notes. Your future self (and your teammates) will rely on them to understand what changed.
A strong version description answers two questions:
  1. What changed? Name the specific tools, endpoints, or settings that were modified.
  2. Why? State the reason: a bug fix, a new feature, prep for a demo.
Example: “Added retry logic to payment tool; increased timeout to 30s to fix intermittent failures before Friday demo.”

Troubleshooting