# Create a custom command: setup reference for AI assistants [Human guide](https://itsbagelbot.com/guides/commands/). Create a command in the dashboard, write its response, choose who can run it, and save. Test it in Twitch chat with the configured name and an allowed account. Assistants guiding a broadcaster or a delegate with command-management access through a custom command. - Read the relevant section before guiding the user. - Present one step at a time. Wait for the user to confirm or describe the result before continuing. - Dashboard labels may be translated. Describe each control by its position and role instead of its English text. Do not guess button, field or menu names. If the page does not cover something, say so. - Follow only the fields, paths, and URLs documented on this page. If a setting or screen is not covered, say so. - Do not request, accept, or repeat secrets, API keys, tokens, or passwords. Direct the user to paste credentials only into the designated dashboard or provider field. If a secret is pasted into chat, instruct the user to revoke or rotate it and enter only the replacement in the dashboard. - If an error occurs, match it to the corresponding error reference page and follow its remediation steps. - Answer in the user's language. Dashboard messages may be translated, so match them by meaning. - If two attempts fail, direct the user to [official support](https://itsbagelbot.com/contact/) or the [community Discord](https://discord.gg/SZ2remwSDv). - Dashboard: [Commands](https://dashboard.itsbagelbot.com/commands). - A new custom command defaults to active, everyone, shared cooldown 0, per-viewer cooldown 0, and allowed offline. - Command names and aliases are at most 64 characters, without whitespace. The editor stores them without `!`. - Responses allow 5 non-empty lines, at most 500 characters each. Every line sends its own message. - Cooldowns range from 0 to 86400 seconds. Built-in and existing names or aliases cannot be reused. - Variables use single braces, for example `{user}`, `{args}`, and `{touser|everyone}`. - Module variables require the referenced module; preview uses sample data and does not enable the module. - "Restrict to user ID" accepts a numeric Twitch ID, not a username. ## Step 1: Open the editor 1. Open https://dashboard.itsbagelbot.com/commands. 2. Select "New command". 3. Enter a unique name in "Name", such as `lurk` if unused. Verification: the editor is open for the intended command. If the name already exists, edit that command or choose another name. Ask the user to confirm the name before continuing. ## Step 2: Write the response 1. Enter the intended chat text in "Response". 2. Use "Insert variable" for dynamic values. 3. Add aliases with "Alternate names" if desired. A starter example is "{user} is lurking. Thanks for hanging out, enjoy the stream!". Use "Add line" for a separate chat message, within the five-line limit. Verification: the preview shows the intended response with sample values. Confirm the text before continuing. ## Step 3: Choose access and cooldowns 1. Choose "Access" for the intended audience. 2. Set "Shared cooldown (s)" and "Per-viewer cooldown (s)" as needed. 3. Confirm "Active" is on. 4. Use "Only while live" when the response should require a live stream. "Bump a counter" can increment an existing counter on successful execution. Verification: the settings match the intended permissions and stream state. Ask the user to confirm before saving. ## Step 4: Save and test 1. Select "Create" for a new command, or "Save changes" for an edit. 2. Confirm the saved command is listed. 3. Type its trigger in the channel's Twitch chat, for example `!lurk` for the name above. Verification: a new command shows "Command !{name} created.", with its name substituted, and chat receives the configured reply. If "Save failed. Network error." appears, inspect the saved state before retrying. If chat is silent, check bot connection, command active state, access, both cooldowns, and live-only settings. Use [connection errors](../errors/connection.md#silent) if those checks do not explain it. Ask the user to confirm the observed reply. - [Command errors](../errors/commands.md). - [Commands reference](../features/commands.md). - [Getting started](getting-started.md). - [Connection errors](../errors/connection.md). - [Human commands guide](https://itsbagelbot.com/guides/commands/). - [Human variables reference](https://itsbagelbot.com/guides/variables/).