1. Verify the plugin
The RobloxAIBuilder author's DevForum post links to Creator Store asset ID 80854193145549. Confirm that ID against the RobloxAIBuilder Creator Store page.
The author describes RobloxAIBuilder as a first version that needs additional testing and refinement, so a reproducible failure may originate in the plugin rather than Studio configuration.
2. Restore the Plugins tab
Roblox documents Plugins as one of Studio's default tool tabs. To show a hidden tab:
- Right-click an empty area of the toolbar or mezzanine.
- Select Manage Tabs.
- Set Plugins to show.
3. Review plugin web permissions
Roblox documents that the first time a Studio plugin attempts to use HttpService, Studio might request permission for the plugin to communicate with a particular web address. Users can accept, deny, or revoke these permissions through Plugin Management.
If RobloxAIBuilder displays a permission or web-request error, review its permissions in Plugin Management. Grant access only when you recognize and trust the destination.
Do not enable Allow HTTP Requests in Experience Settings solely as a speculative plugin fix. Roblox documents that this experience-level setting enables HttpService:GetAsync(), PostAsync(), and RequestAsync() for the game, while Studio-plugin web permissions are handled through Plugin Management.
4. Inspect Output
Open Output from Studio's Window menu or Script tab. Roblox documents that Output displays errors captured from running scripts, Roblox Engine messages, print() messages, and errors from warn() calls.
Retry the failing action once and record the first relevant Output message. Remove API keys, tokens, private URLs, and private project information before sharing diagnostic details.