Managing apps & bots
Create, rename, pause, delete, and iterate on apps and Discord bots in your FlareX workspace.
Updated
A bot in FlareX is a self-contained unit: its own source, its own runtime, its own secrets, and optionally its own Postgres schema. You can have multiple bots in one workspace — the limit depends on your plan.
Creating a bot
From the panel dashboard, click Create bot and describe what you want in one sentence. The first chat turn sends your prompt to FlareX AI, which returns a structured proposal:
- A one-paragraph summary of what the bot does.
- A list of affected files and their full contents.
- A diff you can scroll through before accepting.
Accept the proposal and the bot appears in your workspace with version v1. You can iterate further by chatting — every accepted change is a new version.
Be specific in your first prompt. "Build a moderation bot" gets you a minimal skeleton. "Build a moderation bot with warn/mute/ban commands, a modlog channel, and timeout escalation after three warnings in seven days" gets you a near-complete implementation.
Bot settings
Each bot has a Settings tab with:
- Name — shown in the panel and in audit logs. Doesn't affect the Discord-side bot username.
- Region — optional pin to a specific runner region. FlareX picks automatically if unset.
- Paused — suspend the bot without deleting it. Container stops, keeps config + data.
- Delete — owner-only. Soft-delete with 30-day tombstone; bot + data can be restored within the window.
Iterating via chat
The chat panel is where most of your work happens. Send a message like:
Add a /warn command that DMs the user a copy of the warning and logs it to the modlog.
FlareX returns a proposal showing:
- Which files changed
- The full source of new/edited files
- A diff highlighting what's different from the current version
Accept → new version. Hit Deploy to push it live.
Need to try two approaches in parallel? Open a new thread. Each thread keeps its own history; you can archive or delete threads you don't need anymore. The main thread can't be deleted.
Versions and rollback
Every accepted proposal is a version. The Deployments tab shows which version is currently live and which were deployed historically.
To roll back:
- Open Deployments.
- Click Deploy on the version you want live.
- FlareX rebuilds from that version and swaps the runtime.
Rollbacks are near-instant because the build is cached.
Moving bots between workspaces
Not supported in V1. If you need to transfer ownership, export the workspace data (Settings → Export), create the bot in the new workspace from the exported source as the first chat turn, and deploy.
Deleting a bot
In Settings, scroll to Danger zone → Delete bot. Confirm by typing the bot slug. The bot enters a 30-day tombstone — the panel still shows it (greyed out) and you can restore it from the deleted-bots list. After 30 days it's permanently erased, including the Postgres schema and R2 archives.