Everyday setup checklist
After installing EvoX Desktop, use this checklist to verify your accounts, models, plugins, and saved work. Repeat the relevant checks when changing a model, adding a plugin, or moving devices. For installation, start with Quickstart.
Identify your accounts
Your EvoMap account, model-provider account, and external plugin accounts are separate. Signing in to EvoMap does not sign you in to a model provider or grant access to external files and messages.
Check connection names and identities against your intended use. Give multiple connections to the same provider distinguishable names and confirm which account pays. Keep keys out of chats and project instructions. Follow Change accounts and remove connections when replacing access.
Check settings with a small task
Choose material you are allowed to read, ask EvoX for a short summary, and save it to a specified location. Complete this before adding external writes, more plugins, or long-running work.
| Check | Evidence |
|---|---|
| Model connection | The intended model responds through the selected connection |
| Files | The chosen input is readable and output is saved where expected |
| Plugin account | Returned resources belong to the intended accessible account |
| Writes | Actual content appears in the destination file or service |
| Usage | The request appears in the relevant period with a known charge source |
Use Configuration for connection fields. A connection test covers that test; verify images, tools, and external writes in tasks that require them. If a reply is missing after submission, check the destination before submitting again.
Enable the capabilities you need
Review plugin sources, identities, and permissions under Manage plugins and access. Before removing an unused connection, check dependent tasks; remove the local entry and revoke remote authorization separately. Set file, command, and external-action boundaries under Permissions and approvals.
For a locked setting, use Settings sources and locks. Even on a personal device, use the actual source shown in the report. Do not reset all configuration to repair a single overridden value.
Save your work and understand charges
Locate project files, generated artifacts, and experience you want to keep. Before moving devices or cleaning up, follow Back up and move devices. A completion message is not a substitute for a saved file.
Usage and cost reconciliation separates local estimates, provider bills, and EvoMap credits. Changing an estimated unit price does not change real charges. Set budgets through a service or execution path that actually enforces them.
Repeat checks after changes
After an app update, account or model change, plugin update, or project move, repeat the affected small task. Confirm access, saved output, and absence of duplicate execution. Use Find problems and collect diagnostics to narrow failures.
Your setup is ready when you know which account and model you use, where results are saved, where charges arise, and can complete your intended task.