How can we help you today?

Download an available installer, sign in with your CyberAI account, open or clone a folder you trust, then choose and configure an AI provider. Start with Ask before approving edits or commands.

Use only the official download shown as available below. On Windows, run the signed .exe if published, close the app before updating, and use Windows Settings > Apps to uninstall. Keep workspaces backed up. macOS or Linux instructions apply only when those artifacts are listed as available.

Use the same CyberAI account as the website. The browser-to-desktop handoff creates a revocable desktop session; never paste its token into chat or support. Manage sessions from Dev Devices.

Open or clone only folders you are authorized to use. Files, local paths and indexes stay on the device by default; the app can sync opaque workspace metadata when that feature is enabled. Review repository state and keep backups before Agent changes.

Configure a supported provider in Dev settings. Keys should remain in protected operating-system storage and are not synced to the website. Provider terms, quotas, charges, model behavior, input handling and availability remain the provider's responsibility.

Ask explains without changing files. Agent can inspect context, propose edits and use approved tools. Treat plans, commands and generated code as suggestions: inspect every diff, test the result and reject actions you do not understand.

Git and terminal actions run against the workspace and can change or delete data or contact external systems. Check the current branch and diff, avoid destructive commands, protect credentials, and approve commits or pushes only when intended.

Dev Usage and Spending show synced records when available; missing data is not zero and cost stays unavailable without verified pricing. Billing uses the existing CyberAI billing history and may show Preview/Development Access without a separate Dev price. Review and revoke desktop sessions in Devices.

Connect only accounts and organizations you control. Review requested OAuth scopes and linked workspaces. Disconnecting stops future CyberAI access but does not undo prior actions or change data the provider retains under its terms.

Use the exact project URL/reference and the least-privilege credential appropriate to the supported check. Do not paste database or service-role secrets into prompts or support. CyberAI Dev does not offer arbitrary SQL through the website.

Treat every MCP server as third-party code. Verify its operator, URL or local command, exposed tools/resources, environment-variable names and permissions. Remote servers receive tool-call data; local stdio runs on your device. Never store secret values in shared MCP metadata.

Keep provider keys in protected credential storage, use least privilege, inspect diffs and commands, update supported builds, and revoke unknown sessions. Do not send workspace contents, source code, API keys, tokens, passwords or other secrets in a support request.

Restart the app, confirm the current release is installed, verify sign-in, provider status and workspace permissions, then reproduce with the smallest safe example. Contact support with the Dev topic, app version, OS, steps, expected result and sanitized error text—never code or secrets.