Skip to main content

​
What it does

The Builder Agent is the conversational assistant inside the Discord Custom Builder. Describe the outcome you want; it can inspect the current builder workspace and create or edit commands, event projects, timed events, variables, and message templates. It can connect blocks and save a validated project. You can also attach a screenshot to explain an existing flow or layout. This is different from Magic Builder, which creates a Verb’s character and personality. The Builder Agent works on Discord bot workflows.

​
Start a build

  1. Connect the Verb’s Discord bot and open Discord Custom Builder.
  2. Open the assistant at the bottom of the builder.
  3. Describe the behavior, including its trigger, channel, permissions, message, and any choices you care about. If you want the agent to invent the wording or layout, say so.
  4. Review the agent’s result and open the projects or resources it created.
  5. Test the saved flow with the connected bot in Discord.
For example: “Create a /poll command with a required question and four choices. Post the poll in the invocation channel and add numbered reactions to the posted message.” You can continue the same conversation to revise a project, open conversation history, start a new conversation, stop an active run, or retry a stopped/failed request. A prompt can include up to four images, each up to 5 MB.
The assistant is available only when the Builder Agent is enabled on the backend serving your workspace. If the builder says it is unavailable, a plan upgrade alone will not enable a backend that has not activated it.

​
Daily messages by plan

The allowance is per account, shared across its Verbs, and resets at 00:00 UTC. The assistant shows your remaining messages before you send and displays an upgrade link when the allowance is exhausted. An eligible failed or interrupted run with no saved changes can have its message restored. Manually stopping a run does not automatically restore its message. These are Builder Agent messages, not ordinary chat messages or a limit on manual canvas edits. See plans and limits for the full plan comparison.

​
Saved does not mean tested

When the agent says a project was saved, inspect its trigger, options, block connections, message payload, and enabled state. Runtime synchronization confirms that the bot accepted updated configuration; it does not prove that every Discord permission, channel, interaction, or external action will succeed when a member uses it. If the project sends a Components V2 message, open its Message Builder and check the card/text layout and any button or dropdown When used… action. See Components V2 messages for the editor and runtime requirements. For a slash command, run it in the target server and confirm the expected public or private response. For an event, trigger it with a test account. For a timed event, inspect its schedule and test the underlying actions before depending on it. Keep the bot connected and give it the permissions the flow needs. If a command says “Builder command finished, but no message block sent a response”, check that a Send or Edit a Message block is connected to the command path, that it is configured to send a response, and that the bot runtime is running the version that supports the saved message format. A saved graph or a reported sync alone is not proof that the response appeared in Discord.

​
Review and undo

The assistant can show links to the projects and other builder resources it changed. Undo changes restores builder configuration from that run when undo is available. It cannot retract messages already delivered to Discord or reverse other external side effects. Review those separately. The manual builder remains available for fine-tuning. Unsaved manual canvas changes stay local until you save them; the agent’s completed, applied changes are saved by the agent.