Bansun — Support and Troubleshooting

Check the app status and backend health. An installed model is not necessarily ready: the owned runtime downloads missing files and performs a real warm-up. Wait for a verified ready model before starting a conversation.

A 503 busy response means the inference queue is full; wait and try again. Persistent unavailability should be checked by the operator against runtime logs, network access and available memory. Do not change models or reinstall the app just to bypass a temporary capacity limit.

Use SmolLM2 135M CPU if no usable WebGPU adapter is available. GPU models need compatible hardware and enough memory. Keep the page open until the model and engine are fully cached; offline reload is only available after the offline-ready state.

Use the same site origin and browser profile. Private browsing, clearing site data, low disk space or moving from a preview domain can make a previous cache unavailable. Free space or choose a smaller model. Do not clear the entire site's data before exporting your personal records.

Live balances, approvals, ENS, prices and gas need internet and reachable providers. Confirm the Ethereum mainnet address or transaction hash. Deep approval scans can be slow or miss history outside provider coverage. Missing price data does not prove an asset has no value, and an empty approval result is not a complete security audit.

Check that you are using the same domain, browser profile and device. Unlock the vault before opening a store set to Vault mode. Import a verified encrypted backup only after reading the replacement warning. Recovery requires the matching vault backup and enough matching shares.

There is no server-side password reset or automatic cloud copy. Bansun cannot reconstruct a deleted local record if you have no usable backup. Do not share passphrases or recovery pieces in a support request.

Use the official Bansun X profile, @bansun_ai, for project contact. Do not publish private records, passphrases, seed phrases, recovery shares or wallet keys. For privacy requests, describe the request without posting the underlying sensitive data.

For a general bug, describe the tool, what you expected, what happened, approximate UTC time and browser/device type. Redact wallet labels, personal notes, tokens, passphrases and sensitive identifiers. For vulnerabilities, follow responsible reporting. For product instructions, read Docs.

There is no official $BANSUN claim page in this release. Ignore impersonators offering private fixes or requesting funds.