Skip to main content
In this guide, 2.0 means the earlier Clark app format (YAML APIs, flat project layout). 3.0 means the current format (TypeScript APIs under a client/ and server/ layout). Apps built with Clark before April 2026 are often still on 2.0.
Upgrading to 3.0 makes Clark faster and more accurate and unlocks the latest editor and Git features. Clark runs the upgrade for you, rewriting and testing your APIs. The change is one-way once you finalize.

​
How do I know if my app is on 2.0?

Open the app in the editor. If it is still on 2.0, you will see a banner that lets you Upgrade. If you can open the Code tab (< >) and view the app source, the app is already on 3.0 and will not show the upgrade banner.

​
Why upgrade?

For how TypeScript APIs work after upgrade, see Backend APIs.

​
Features that need alternatives in 3.0

Some 2.0 patterns are not supported the same way in 3.0 apps:
  • Custom backend libraries used inside APIs
  • Environment variables in APIs (removed for credential security; use integrations and secrets instead)
  • One-off REST requests (ad hoc REST steps outside a configured REST integration)
  • Python API steps
Clark will help you find alternatives during the upgrade. If you need additional support, contact us.

​
How to upgrade

1

Start the upgrade

Open your application in the Superblocks editor, then click the Upgrade button in the banner at the top of the page.Application banner with button to upgrade
2

Confirm and begin migration

Confirm the migration details and settings, including adjustment of API write permissions to prevent Clark from testing APIs that write to sensitive integrations. Click Upgrade now to start the migration.Application modal with with upgrade details for user to confirm
3

Let Clark migrate and test

Clark will create a checklist and get to work migrating and testing your application. At any point in time you can select Abort migration to restore the previous version.Application in the process of migration
4

Finish and finalize

Finalizing permanently deletes the pre-upgrade backup. You cannot abort or roll back to the 2.0 app after that. Clark also loses access to the legacy API code as a reference for future edits.
Once the upgrade completes and you are satisfied with the results, click Finish upgrade then Finalize upgrade to confirm.Button to finish upgrade

​
Abort and restore

To cancel the upgrade at any point, click Abort upgrade, then confirm with Abort and restore. Aborting does the following:
  • Upgrade progress is discarded
  • Clark generation stops
  • The app restores to the pre-upgrade backup checkpoint
  • Clark chat context is cleared
  • The page reloads when restore finishes

​
Troubleshooting

​
APIs could not be upgraded or verified

  • Use Fix with Clark for APIs that failed conversion
  • Use Get testing instructions when Clark could not auto-test some APIs (for example write APIs you blocked from testing)
  • Manually verify those APIs before you finalize

​
Unsupported integrations

The upgrade details modal may also list specific integrations that are not fully supported in 3.0 for your app. Clark still attempts the upgrade, but those APIs may need manual attention. See Features that need alternatives in 3.0.