Get help with BringYour

Get help with installation, a local license, or a migration. Describe what you expected and what happened, without sharing private setup data.

• License delivery or payment issue: email hello@bringyour.ai from the purchase address.
• Installation or migration issue: include your OS/architecture, source and target tool names and versions, and a redacted description of the problem. Do not send raw configurations, API keys, license values, local paths, or raw command output.
• Existing install: run curl -fsSL https://bringyour.ai/install.sh | sh -s -- --force, then bringyour upgrade for future latest-channel updates.
• Windows install or upgrade: download bringyour-latest-windows-amd64.exe from the download index and verify it against its .sha256. This is a standalone executable. See the PowerShell command below to check it.
• Distill help: name the command, such as bringyour distill verify, and describe the problem. Leave out bundle contents, report paths, and private arguments.
• Sync help: name the source and target tools and describe which sync step failed, with private details removed. Auto sync is disabled by default.
• Remote MCP issue: include the tool name or HTTP status and a redacted symptom, without request arguments or private data. The remote MCP is no-data and only supports preview, target listing, install handoff, catalog, quote, and checkout.

Optional local diagnostic: run bringyour doctor --support and review the JSON before choosing to share it. This free command does not upload anything or include configuration contents, license values, or local paths. Use --support alone; ordinary doctor output is not this sharing format.

Windows PowerShell: open PowerShell in the folder containing the downloaded file, then run .\bringyour-latest-windows-amd64.exe doctor --support. If you renamed it to bringyour.exe, use .\bringyour.exe doctor --support instead. The .\ prefix runs a file from the current folder; downloading it does not add it to PATH. Run this in Windows when checking your Windows setup, since a Linux report from WSL checks the Linux home directory.

The report checks default tool-directory presence and local license status. It does not verify payment, a working setup, migration, or target behavior. A missing or invalid local license does not establish nonpayment or loss of entitlement. Sharing a report is optional and does not affect refund eligibility or lifetime access.