ExtraExecutor — complete documentation

Documentation version: October 22, 2026. Covers the current local project build. Button names match the application.

Contents

  1. First launch and folders
  2. Editor, Run, Attach, console, and settings
  3. Accounts, password, and manager actions
  4. Launching, assigned scripts, memory, and recovery
  5. Roblox signals, timers, and multiple accounts
  6. Troubleshooting
  7. Feature status and known limitations
  8. Development, builds, and maintenance
  9. Log completion rules, MCP, and Dex++
  10. AND/OR builder, sequences, HTTP, Studio, and AI clients
  11. Standalone Luau VM
  12. Standard/Production, protection, installation, and updates
  13. Website sign-in, Discord, keys, and releases
  14. Device protection and HWID binding

Quick reference

TaskLocation
Add an accountAccounts → Add Account → Manual Login
Assign a scriptSelect account → Account settings → Accounts & sessions → Account setup → Script
Set game/VIPRecovery in the same profile
Submit automaticallyAuto-attach + Send selected script after attach
Reconnect on a timerSession cache, script signals & schedule → Connection interval
Script recovery requestPotassiumSession API
Memory limitsMemory and individual profile cards
Saved scripts%LOCALAPPDATA%\Potassium\scripts
Run has no effectRun/Attach troubleshooting

Readiness terminology

Implemented means a code path exists. Builds successfully means compilation succeeded. Verified in game would mean an actual live-client run; this build does not have that complete confirmation.

submitted means delivered to the client, not executed. running means a process is tracked, not that it joined the intended server. Documentation describes existing behavior; it does not implement missing features.