Local app development
Edit your own app while Nexia runs in a cloud sandbox.
Local app development
Complete the quickstart first. The cloud sandbox runs Nexia; your computer serves only your app’s public browser files. Core is private and is not a local dependency.
Continue an existing app
nexia login <project-id>
nexia link my-app
nexia validate my-app
nexia dev my-appApprove login in the browser and check the project printed by link before continuing. Linking records the project binding; it does not upload the app. Keep your app directory in your own source repository.
Edit files under public/ and check the workspace work tab. Stop the local server with Ctrl+C; run the same dev command to resume. If a connection expires, sign in and approve the project again. Check sandbox expiry in the console.
Before submission
Increase the app version when files change after an earlier submission. Run nexia validate my-app, then nexia deploy my-app. Review the result in the console. The bundle must contain public static assets, not server executables or credentials.
The static CLI manifest is not a Composer App manifest. Use SDK reference only for the integration contract your project supports; Core source access is not part of developer onboarding.
Verify
Run nexia status and confirm the intended project is connected. Open the workspace from your project console and check the app in its work tab.