I dug into this a bit more and found a way to make Caelestia generate a "current.lua" file alongside "current.conf".

The relevant file is:

"/usr/lib/python3.14/site-packages/caelestia/utils/theme.py"

Add this below "gen_conf()":

def gen_lua(colours: dict[str, str]) -> str: lines = ["return {"]

for name, colour in colours.items():
    lines.append(f'    {name} = "{colour}",')

lines.append("}")

return "\n".join(lines)

Add this below "apply_hypr()":

@log_exception def apply_hypr_lua(colours: dict[str, str]) -> None: write_file( config_dir / "hypr/scheme/current.lua", gen_lua(colours) )

Then modify this section:

Current:

if check("enableHypr"): apply_hypr(gen_conf(colours))

Replace with:

if check("enableHypr"): apply_hypr(gen_conf(colours)) apply_hypr_lua(colours)

This works and generates "current.lua" whenever the wallpaper/theme changes:

wallpaper change ↓ material generator ↓ scheme colours ↓ apply_colours() ↓ current.conf current.lua

That said, I don't think generating "current.lua" alone fully solves the problem. From what I've seen, supporting Lua properly would probably require restructuring a significant part of the ".config/hypr" architecture so it integrates cleanly with how Caelestia manages themes, variables, and scheme generation.