Default Dry-Run Mode for Write Operations

One of GameCatalyst’s most important safety features is dry-run mode. All file write operations simulate changes by default instead of actually executing them. This lets you see what would happen before it happens.

What is dry-run mode?

Dry-run mode means the AI goes through all the steps of a file operation (validation, path checking, content preparation) but stops just before actually writing to disk. Instead, it returns a message like:

[DRY RUN] Would create file at Assets/Scripts/PlayerController.cs with 150 lines of code.

You see exactly what would happen, but your project files remain unchanged.

Which commands use dry-run mode:

All FileSystem write operations default to dry-run:

• file.create — Creating new files
• file.edit — Modifying existing files
• file.delete — Deleting files
• file.copy — Copying files
• file.move — Moving files
• file.rename — Renaming files
• folder.create — Creating folders
• folder.delete — Deleting folders
• folder.copy — Copying folders
• folder.move — Moving folders
• folder.rename — Renaming folders

Read operations (file.read, folder.read, file.info, folder.info) never use dry-run because they don’t modify anything.

How to disable dry-run for a specific operation:

When you want the AI to actually execute a file operation, you tell it to set dry_run to false. For example:

You: “Create a PlayerController script at Assets/Scripts/PlayerController.cs”

AI: [DRY RUN] Would create file at Assets/Scripts/PlayerController.cs...

You: “That looks good. Create it for real with dry_run set to false.”

AI: Created file at Assets/Scripts/PlayerController.cs (150 lines)

The AI includes dry_run: false in the command parameters, and the file is actually created.

Disabling dry-run globally:

If you trust the AI completely and want to skip dry-run confirmations, you can disable dry-run mode globally:

1. Open the Dashboard Settings → Advanced tab
2. Find the “File System” section
3. Locate the “Dry-Run Default” toggle
4. Turn it off (gray)

Now all file operations execute immediately without dry-run simulation. Use this carefully — you lose the safety preview.

Best practices:

• Keep dry-run enabled when working with important files or unfamiliar AI behavior
• Disable dry-run when you’re confident in the AI’s actions and want faster iteration
• Use per-operation dry_run=false for selective execution without changing the global default

Dry-run mode is your safety net. It prevents accidental file deletions, overwrites, and other destructive operations. When in doubt, leave it enabled.