Release notes

What changed in Palatial, newest first. Only changes you can see or act on are listed here.

September 23, 2026

Codex CLI and Claude Code

Version 0.1.5. See Codex CLI and Claude Code for the current install command. Run palatial-agent update --apply to move up from an earlier version, then restart your coding agent and rerun setup.

Asset reads now report whether a finished asset was built with diffusion, parametric, or mad_max. The route label is informational; use the documented create settings when starting a new asset.
A reference image is now optional for CAD. Supply one when you want textures generated from it, or send the mesh on its own and it is built untextured.
You can now give the exact real-world scale of a direct mesh, as the number of metres one unit of your file represents, instead of naming its units. Give one or the other; if you give both and they disagree, the request is refused.
A GLB whose textures are embedded in the file can now keep its own appearance. The file is checked before the request is accepted. Other single-file mesh uploads still cannot prove they carry an appearance, so USD, STEP, and IGES remain the formats that reliably keep one.
You can now ask for more effort on a text or image build that uses the parametric shape model. The higher levels gather evidence about a named product and build to it. They cost more and take longer, so ask for the standard level for everyday objects.
Reference images can now be WebP, alongside PNG and JPEG, for single-image, multi-view, multi-photo, and CAD reference requests.

September 22, 2026

Codex CLI and Claude Code

See Codex CLI and Claude Code for the current install command and the full tool list.

Your coding agent now comes with built-in Palatial guidance: how the workflow runs, what every build setting does, worked examples for text, image, and CAD requests, and what to do when something fails. Claude Code loads it on its own. Any client, including Codex CLI, can read it on request. You can read the same pages yourself with palatial-agent guide, with no key and no network call.
The asset-detail, listing, progress, reprocessing, and variant tools are now available. They were previously described as planned.
You can ask for soft objects such as cloth, garments, cable, and rope, so the asset deforms instead of staying solid. A single asset can also combine solid and deforming parts. Soft objects simulate in Newton, so include Newton as a target simulator.
Mesh repair, glass replacement, and automatic real-world scaling can now be requested on any input type. Use glass replacement for clear plastic, acrylic, resin, and lenses too, not only for things called glass.
If your CAD model is already correct, you can now run it through collision, physics, and validation without rebuilding its appearance or its parts. Keep the existing textures, keep the existing shape and parts, or do both at once.
Requests that contradict themselves are now refused before anything is charged, and the message names the setting and the values your input type accepts. Keeping a CAD appearance needs a format that can carry one, so a single uploaded mesh is refused with the formats that do work.
Downloading the export of a failed build is now an explicit, separate step. A failed build can still have a partial export, so your agent has to confirm with you first.
For CAD requests, you now state only what your file cannot tell us. A direct mesh still needs its source units and up axis, STEP and IGES need only the up axis, and USD files need neither.
Updating is now built in: run palatial-agent update to check for a newer version and palatial-agent update --apply to install it. Restart your coding agent afterwards, and rerun setup so the installed guidance matches.
Setup will not overwrite a Palatial skill folder it did not create, including one you edited, and it now tells you when part of setup did not complete.