Choose what to add to this project. Scene objects appear in the Hierarchy; scripts appear in the script list.
Enter the five-character developer code to unlock diagnostics and the custom-command workbench. This is a convenience lock only, not real security.
Create commands without editing Flow Studio's source. Each command name is registered with a built-in safe action, then becomes available to the Flow parser and syntax checker in this browser.
Alert.Alert("Hello from Flow!").Arguments are Flow expressions, so variables also work: Alert(PlayerName). Custom commands are included in a .flowproj export. They are local to this browser unless you share/import a project that contains them.
Available actions are deliberately limited to safe built-in engine actions. Adding a completely new kind of behaviour still requires an engine plugin; this workbench lets you create new command names and assign supported actions without changing the source.
Sign in with your own Supabase project, create a private-by-code room, and collaborate on the active Flow script. Your Supabase publishable key belongs here; never paste a secret or service-role key.
Latency note: Flow sends edits in short batches (about 25 ms after typing) and cursor updates frequently. Actual delay depends on Wi-Fi, mobile data, distance to the Supabase region and service load; no browser app can guarantee every keystroke arrives in under 100 ms. This first shared editor is snapshot-based, so avoid typing into the exact same part of a file simultaneously.