The code editor lists the app’s Pages and Functions. Open it with the code icon in the chat header.
When to use chat and when to use the editor
Use chat for changes that affect several parts of the app or are easier to describe.
Use the editor for a precise change you can identify, such as a label or field order.
After a manual edit, test the same paths you would test after an AI change. Direct edits are not safer for being small.
Saving manual edits
Saving a manual edit checks the change. If the save is rejected, correct the listed problems and try again.
Saving keeps the edit in the code editor, but it does not update the app. After editing a Page or Function, select Publish for the change to take effect.
Publish after a manual edit
Publish uses the current page state. It does not let you choose a snapshot during publishing.
-
Test the current preview
Complete the primary workflow. Check permissions, invalid input, empty states, and any external action.
-
Confirm the current state
Finish the edit or restore a snapshot before publishing.
-
Publish and wait for the build
The app rebuilds. Wait for it to return to Active rather than assuming the change is out.
If publishing fails, wait while Appaca shows Fixing…. If it reaches Error, restore the last working version.
Publishing does not grant access
Publishing does not change access. Workspace membership, member access, and Share settings control who can open the app.