WEPPY

First Workflows

The basic flow for turning your first request into real work.

Once WEPPY is installed and connected, you can use an AI agent to control Roblox Studio directly. This page walks you through the basic flow for starting your first task and safely verifying the results.

Basic Workflow

Step 1 — Verify the Connection

Before starting a task, confirm the connection status.

Check the connection status

Or follow the steps on the Check Connections page. Check the plugin’s Connect status first, and use the dashboard’s Connection tab if you need more details.

Step 2 — Submit Your First Task

Start with something simple. Give instructions to the AI agent in natural language.

Create a red Part in Workspace. Set the size to 5x1x5.
Create a 'GameManager' ModuleScript in ServerScriptService.
Set the Lighting time to 6:00 PM.

Step 3 — Review the Results

When the AI performs a task, it’s reflected in Studio immediately. You can review changes Before & After in the dashboard’s Changelog.

See the Change History page for details.

Step 4 — Move to More Complex Tasks

Once you’ve verified the basics, move on to tasks that involve multiple changes at once.

Add a particle effect and sound when the player jumps, and include a cooldown.
Build a boss arena in the center of the map and place spawn points without collisions.
Change this module's interface and update all scripts that reference it.

Core Tool Examples

Creating Instances

Create a 'Platform' Part in Workspace and set its Position to (0, 5, 0).

Internally, the mutate_instances tool’s create action and the manage_properties tool’s set action are used.

Writing Scripts

Create a 'PlayerController' Script in ServerScriptService that prints a message when a player spawns.

Internally, the manage_scripts tool’s create and set_source actions are used.

Inserting Assets

Search for a 'Tree' model in the Creator Store and insert it into Workspace.

Internally, the manage_assets tool’s search_insert action is used (Pro only).

Batch Execution

When processing multiple tasks at once, using batch_execute saves AI tokens (Pro only).

Large-Scale Changes with Sync

To work from the full project structure, activate Sync first. With Sync enabled, the AI uses locally synced files as its reference to understand the entire structure and apply consistent changes across multiple files.

Check the Sync status and summarize only the risky changes based on recent history.
Refactor the scripts in ServerScriptService first and keep a change history.

See Bidirectional Sync for details.

Tool Categories

A grouped overview of what you can ask the AI to do. See the Tools & Stats page for detailed usage.

CategoryDescription
Instances & PropertiesSearch, create, modify, delete, and clone instances; manage properties and tags
Scripts & Code ExecutionWrite and edit scripts, execute arbitrary Luau code
World EnvironmentLighting and atmosphere, terrain generation and editing, spatial queries and raycasting, camera
Assets & Object PresentationAsset search and insertion, tweens, animations, audio, particles and effects, physics groups
Playtest & Automated TestingControl Run / Play mode, auto-inject test scripts, generate reports
SyncBidirectional Studio ↔ local file sync, multi-place support
System & DebuggingCheck connections, view logs, manage selection, batch execution

Tier Policy

  • Basic — Core tools for instances, properties, scripts, selection, camera, and logs, plus Studio → Local one-way Sync.
  • Pro — Adds bidirectional Sync, bulk operations, environment and presentation tools, spatial queries, assets, and Playtest automation to the core tools.

Next Steps