Frequently asked questions

Do I need to know how to code?

No. You can describe what you want in plain language, start from a template, or assemble workflows in the visual builder. The code is always there to read if you're curious, and developers can edit handlers directly.

Does Botwright ever ask for my Discord password?

Never. Signing in with Discord uses Discord's official OAuth2 flow, and your bot connects with a bot token that you create in the Discord Developer Portal. The token is encrypted at rest, never shown again after you paste it, and never sent to the AI.

Where does my bot actually run?

On Botwright's hosting. Each bot runs in its own isolated container with strict CPU, memory and process limits. The status, uptime and logs you see come from that running process — nothing is simulated.

What permissions will my bot ask for?

Only what its features need. Botwright derives the permission list from your bot's commands and automations, shows the reason for each one, and builds the invite link from it. Bots are never granted Administrator.

Can I change my bot after it's live?

Yes. Edit settings, tweak a workflow, or ask the assistant for a change. Every change becomes a new version that you review before deploying, and you can roll back to any earlier version.

What are AI credits?

Each request to the assistant uses credits in proportion to the work it does. Every plan includes a monthly allowance that resets on the first of the month. Templates, the visual builder, hosting and the dashboard don't use credits.

What happens if my bot crashes?

It is restarted automatically with a short backoff. If it keeps failing, it is stopped, you are notified, and the logs show the error — with an option to have the assistant diagnose it.

What isn't allowed?

Self-bots, token grabbers, mass unsolicited DMs, raid tools, and anything built to evade Discord's safeguards or rate limits. Bots must follow Discord's Developer Policy and Community Guidelines.