Capability list

Status: Implemented for the names: clight check, the loader and the website accept exactly these, and the Permissions screen lets the player allow or deny each one. The APIs behind most of them are Planned (the “API” column).

Every mod is sandboxed: it can use the game API and its own folder, nothing else. Capabilities go in permissions (the mod needs them) or optional_permissions (it works without them). The player allows or denies each one on Mods → Permissions. See Capabilities and permissions.

Capability	Grants	Default	Level	API
game	The full CLight game API	always	—	yes
fs.mod_data	Read and write mods/<id>/data/	always	—	yes (WASI /data)
fs.config	Your own config files	always	—	yes (config API)
net.http:<host>	HTTPS to that host (*. wildcard allowed); downloads only into mods/<id>/data/, size-limited, never run	declared	info	planned
net.http:*	HTTPS anywhere, same download rules	declared	warn	planned
os.open_url	Open a link in the browser (with a confirmation)	declared	info	planned
os.clipboard	Read the clipboard (writing is always allowed)	declared	warn	planned
os.notifications	OS notifications while the game is unfocused	declared	info	planned
account.profile	Player name, UUID, skin (never tokens)	always (client)	—	planned
input.synthesize	Send chat, commands, key presses, movement	declared	warn	planned
packets.raw	Raw packet listeners and packet replacement	declared	warn	planned
ui.inject	Change other screens’ documents	declared	info	planned

Some mixin targets name one of these capabilities; injecting into such a target needs the player’s grant (CLL-7007 otherwise).

Never available (rejected by clight check, the loader and the website): reading other folders (saves, screenshots, logs, other mods), raw sockets, starting processes, Vulkan handles, environment variables.

“info” lines are listed neutrally on the Permissions screen; “warn” lines are highlighted. The website shows each version’s capabilities on its page.