Help

Looking for a complete step-by-step? See the Monad Manual.

Short guides for the features the Monad application opens from buttons like "Need help?" and "See the troubleshooting guide".

Updating Monad

Version 1.25.29 brings the new blue identity, renewed icons, a more organized home page and the version visible in the title bar.

1. On the installed app, open Account (the person icon in the menu) and click Check for updates.
2. Wait for the download and choose Restart to update.
3. After the restart, check the version in the title bar.

Monad installed on Windows also checks for updates automatically every hour. If you have not installed the application yet, download the current installer for 64-bit Windows. Running a development copy or an executable without installing does not enable this flow.

GitHub

Connect Monad to GitHub in the app's settings to publish the code and keep a repository in sync.

Troubleshooting

• If the connection fails, disconnect and connect again; the authorization code expires in a few minutes.
• If the push is refused, check that the repository exists, that you have write permission and that the chosen branch is the right one.
• If there is a conflict with what is already on GitHub, resolve it or choose another branch before sending.
• Monad shows the full error text when it comes from Git; copy it when asking for help.

Mobile app (Capacitor)

The "Upgrade to hybrid app with Capacitor" button adds Capacitor to your project, so it runs on iOS and Android as well as the web. To do it by hand, install @capacitor/core, @capacitor/cli and the platforms you want, then run npx cap init and npx cap add android (or ios).

Troubleshooting

• For Android you need Android Studio; for iOS, a Mac with Xcode.
• After changing the web code, generate the production build and run npx cap sync before opening the native project.
• If the native project does not open, confirm that the platform tools are installed and on the PATH.

Select component to edit

The "Enable component selection" upgrade installs the Vite plugin that tags each component in the preview. That way you click what you want to change and Monad knows exactly which file and line to edit. To install by hand, add the Monad plugin to vite.config and install its dependencies; the button does this for you and is the recommended way.

Migrate to the current pnpm version

Monad uses its own pnpm, which writes the lock file (pnpm-lock.yaml) in a format that old pnpm versions cannot read. If your app still declares an old pnpm in packageManager, the warning appears in the console. The migration updates packageManager and the lockfile together, so the preview, CI and anyone who downloads the project use the same version.

• Before migrating, make a commit with the current state.
• If you publish the app elsewhere, update the pnpm version there as well.

Database migration (Portal template)

"Generate database migration" creates a new migration file from the schema changes and saves it in a commit. Review the generated file before applying it to a database with real data.

Security review

The security review reads the app's code and lists findings by severity (critical, high, medium, low). Use "Fix" to ask Monad to resolve the selected findings. Treat the result as support, not a complete audit: secrets, database policies and permissions deserve human review.

Restore settings from a backup

If Monad warns that it could not read the settings file and went back to the default, your previous data was not deleted. Close Monad and go to its data folder (on Windows, %APPDATA%\Monad). In it you will find:

• user-settings.json, the current file;
• user-settings.json.bak, the previous copy;
• user-settings.json.recovery-…bak files, kept when Monad needed to recover the file.

Copy the backup you want over user-settings.json (keep a copy of the current file first) and open Monad again.