Generated App Editor

Applies to: App Generation projects that use the SaaS Engine template

The generated app editor combines AI-assisted changes, application preview, source access, version controls, and hosted VM controls.

The project navigation labels the main editor page Edit via Chat.

Main editor areas

The editor can provide these areas:

Available controls depend on project state, template version, account permissions, and environment status.

Separate unrelated changes into different requests. This practice makes testing and rollback easier.

AI work can consume AppWizzy credits. Review the billing page for the related transactions.

The preview shows the application from the hosted development environment. It can be unavailable while the VM starts or a change runs.

Use Reload preview after a completed change. Test the affected workflow, permissions, forms, and stored data.

Do not rely only on the visual result. Review logs when a request reports success but the application does not work.

Select Code Editor to edit project files directly. The browser editor is separate from Edit via Chat.

Direct source changes can bypass assumptions in the initial schema and specification. Test these changes before you save a version.

Do not place secrets in source files. Use the supported settings or environment configuration for sensitive values.

Select Save after a tested change. Enter a clear message that identifies the completed work.

A saved version is a code checkpoint. It is not a VM snapshot or a database backup.

Uncommitted changes can be lost during some code reset or rollback operations. Save useful work before you use a recovery control.

The editor can show Pause VM when the project uses a managed VM. Pausing stops the running environment and stops hosting charges.

Project files and disk data remain on the persistent disk during a normal pause or resume.

Select Resume VM before you use the editor, application URL, or SSH. Read VM Lifecycle and Billing.

The editor can show publish controls when the required environment is ready. Domain publication and application deployment are different operations.

Manual stable deployment and synchronization controls are currently unavailable. Use the development environment for current editing and testing.

Read Deploying a Generated App for current behavior.

Check the project status, VM state, latest AI message, deployment history, and build logs.

Record the exact request, time, error, and last working version. Do not run a destructive database reset as a general repair step.