Skip to content

instruktlabs/kiln-engine

v1.2.2MIT

Set up a local Kiln workspace to create, inspect and revise editable 3D assets with Claude Code or Codex.

GitHubOpen Website

Kiln local plugin

Plugin version 1.2.2, maintained by Instrukt Labs under the MIT license. This plugin pins engine 1.2.2. Registry setup requires that exact version to be published. Use a published release tag for normal installation or a reviewed local archive for development qualification. The installation ID remains kiln-engine@instruktlabs.

Set up Kiln in an existing project or a new asset workspace, then create and revise editable 3D assets with your coding agent. Use a supported Node.js installation with npm. No Bun, engine checkout, Kiln account or separate model API key is needed. The plugin requires a local shell and filesystem; Claude chat and Cowork are not supported by this local bundle.

Install

For Claude Code:

claude plugin marketplace add instruktlabs/kiln
claude plugin install kiln-engine@instruktlabs

For Codex:

codex plugin marketplace add instruktlabs/kiln
codex plugin add kiln-engine@instruktlabs

Restart or reload your coding agent's plugins as its installation message directs. Then ask it to set up a Kiln workspace. The maintained setup skill runs this plugin's bin/kiln-setup-workspace.mjs with Node, installs @instruktlabs/kiln@1.2.2 outside the project and configures your chosen workspace. The same initializer supports existing projects and new workspaces.

The plugin registers setup only. The workspace supplies authoring skills and one local MCP server, kiln_workspace. Open Claude Code in that workspace or launch Codex there with codex. For headless Codex execution, use node codex.mjs "TASK" with an explicit prompt. Read .kiln/START.md after adoption or START.md in a legacy workspace, accept the host's ordinary trust prompts and verify live tool discovery before authoring.

Setup examples

  1. Create: “Set up a new Kiln workspace in an empty directory outside this checkout, using my current coding agent. Verify its tools before I author an asset.” The installer downloads the pinned engine when needed, creates the selected workspace and keeps its engine in a separate runtime store. npm also uses its normal cache and log directories.
  2. Adopt: “Add Kiln to this project without replacing my instructions or other MCP settings. Show the planned changes first.” Use --adopt --check to preview, then --adopt to apply. Read .kiln/AGENTS.md alongside the project's instructions. Repeat with another supported --harness to add that integration around the same saved assets. The engine's adapter list is included in runtime.json; it does not imply this plugin can be installed in every listed client. Published engine 1.0.0 does not support adoption.
  3. Check: “Check my existing Kiln workspace without changing it.” The helper's --check mode reports whether managed files and the installed engine are current. A missing runtime is reported without installing one.
  4. Upgrade: “Upgrade my managed Kiln workspace while preserving my sources, saved assets and customizations.” Stop the workspace's harness session first. The helper's --upgrade mode uses the pinned engine and refuses conflicts rather than replacing customized managed files.

The engine installation and your assets stay outside the disposable plugin cache. Removing or updating the plugin does not delete them. Existing workspaces stay on their installed engine until an explicit managed upgrade. Read the setup and upgrade guide for paths, repair and failure recovery.

Execution and network access

The setup skill asks your coding agent to execute a bundled Node installer. That installer runs npm with lifecycle scripts disabled and invokes Kiln's workspace generator. It does this before the workspace MCP server exists; it does not silently install a global MCP server or grant itself shell permissions.

Adoption and managed project updates temporarily keep recovery copies outside the project. Client configuration can already contain credentials, so these private copies may too. They are removed after successful setup or recovery; interrupted transactions retain them. See local privacy for the storage location and protection limits. Use --recover before retrying an interrupted project update.

Marketplace installation and updates contact https://github.com. First engine installation and dependency downloads use https://registry.npmjs.org. npm can use your existing npm configuration and environment. No npm login or token is required for this public package. Normal local asset work does not upload your assets to Instrukt Labs. Tool results can enter your coding assistant's model context; its provider handles those copies.

CPU rendering is local. Material appearance needs a compatible local renderer or one you explicitly configure on another machine; a remote renderer receives the GLB and requested capture settings. Follow the setup skill's renderer checks. The separate hosted Kiln integration has its own authentication and privacy notice.

Support and security

Send private security or privacy questions to support@instruktlabs.com. Never include passwords, tokens, recovery codes or private assets in public issues. For a normal bug report, provide the plugin and engine versions, operating system and a small sanitized reproduction at GitHub issues.

If setup fails, retain the error, check Node/npm and network access, and follow the setup guide. Do not delete an unfamiliar runtime or another installer's lock.

Local privacy notice · MIT license · Source