Introduction
What Lynx is, what it ships with, and how these docs are organized.
Lynx is a Luau script executor for Roblox on Windows. Its built-in emulator loads it into every Roblox client you start, it gives you a real editor, and exposes a sUNC-compatible API for scripting, inspecting and reverse-engineering experiences.
These docs cover Lynx 0.0.0. The version is shown next to the wordmark in the app's title bar.
What's inside
- A scripting API. Hooks, files, HTTP, WebSockets, drawing and more, under the names the UNC and sUNC standards use. See the API reference.
- Built-in emulator. Lynx ships its own emulator, which loads Lynx automatically the moment a game starts. There's no attach button and nothing to turn on. Lynx is the only lifetime-license executor with an emulator of its own.
- Multi-instance. Run as many Roblox clients as you like. Every one shows up in one list. Execute on one, some or all of them. See Multi-instance.
- decompile(). A script can turn a LocalScript or ModuleScript back into readable Luau. See Decompiling scripts.
- A sandboxed workspace. A private folder your scripts can read and write, and nothing else. See Workspace & files.
- Auto-execute. Drop a file in a folder and it runs every time Lynx attaches. See Auto-execute.
- Script Hub. The scripts of three community sites in one search, one click from the editor. See Script Hub.
- Projects. Open a folder as a project: a file tree, a build step, Quick Open, Find in Files and a local Git history with diffs.
- AI access. Let apps such as Claude, Cursor or Codex use Lynx through its MCP server. You approve what they may do in Settings → AI.
How Lynx works
Lynx is two pieces. The app is the window you work in: editor, output, files and settings. The module is the part that runs inside Roblox and executes your code. Lynx's emulator loads it as the game starts, and the client appears under Clients. From then on, every script you run is compiled by Lynx and scheduled on Roblox's own task scheduler, exactly like a game script.
Because the module lives inside the Roblox client, it has to match the exact Roblox build you're running. When Roblox ships an update, Lynx needs a matching module. Lynx checks for new files every time it starts. Updating explains the details.
One license key
Lynx uses one license key, activated once. There are no daily keys, no checkpoints and no ad-gated keys. You buy a Lifetime license key from a reseller, redeem it once in the dashboard, sign in to the app with your username and password, and that's it: Lynx remembers the sign-in. Your license is bound to one PC, and you can move it from the dashboard whenever you need to.
How these docs are organized
Conventions
- Code samples are Luau. Paste them into the editor and press CtrlEnter.
- Keyboard shortcuts are written for Windows, the only platform Lynx runs on.
- Function signatures use Luau type syntax. A
?marks an optional parameter or a value that may benil.
Where to next
Written for Lynx 0.0.0
Something unclear? Tell us on Discord