Environment

Ask whether the current call came from executor-owned code. This is useful in a diagnostic callback that may be reached by both your script and the host.

Discard all source strings previously registered with queue_on_teleport. Call it when the user cancels a planned follow-up action before travelling.

Read the operating-system process ID of the running host. It helps distinguish two local logs that came from separate launches.

Take a snapshot of live Luau threads in the current VM. It is handy for a debugger that wants to inspect active coroutines without keeping them alive.

Get just the Kawaii version string. This is the shorter form of the second result from identifyexecutor.

Open the shared Kawaii environment for the current executor session. This is a useful home for a tool's state when separate scripts need to find the same table.

Read the opaque device identifier supplied by Kawaii's Android bridge. Use it only for a local integration that genuinely needs to recognize this installation.

Inspect the Luau registry for the current VM. The registry holds runtime-owned references that ordinary globals do not expose; it is most useful while diagnosing a missing reference.

Read the Roblox runtime environment as seen from this session. Reach for it when you specifically need a host global rather than a value in Kawaii's shared environment.

Collect the runtime's _G and shared tables in one record. It is convenient when checking state another Roblox script has placed in those tables.

Get the environment table attached to a coroutine. Pass a thread when inspecting another coroutine, or omit it to check your own.

Read the execution identity attached to the calling coroutine. Log it when an operation behaves differently under another script context.

Get the running Kawaii build name and version together. Include both in a bug report so someone reading the log knows which runtime produced it.

Check whether a coroutine is classified as an executor thread. Pass the thread you are inspecting, or leave it out to ask about the caller.

Check whether the running interpreter is Luau. Kawaii always returns true, but the check lets a script shared with other Lua runtimes choose its Luau-specific path.

Queue a Luau source string to run after the next eligible game teleport. Use it for a small piece of setup that should follow the player into the new session.

Run a callback in the context of a specified Script, LocalScript, or ModuleScript, then receive its results. It is useful when a callback must observe the same script environment as the code it accompanies.

Change the execution identity of the calling coroutine. If a task temporarily changes identity, save the previous value and restore it even when the task fails.