Quick start

Start from an existing GLB

Import an asset you already own instead of generating one:

glina import ./my-asset.glb
glina workspace
glina verify

The import stages the exact bytes, runs the canonical structural and configured Blender gate, then persists and activates only accepted content. The final command omits a path and verifies that active copy. glina onboarding --asset ./my-asset.glb performs the same operation from first use; skipping leaves an empty, usable workspace.

The examples below show the command paths. Generation and rendering require live external systems; a successful config or process probe alone does not prove that Blender or Weles can complete a job.

Use a checkout

This repository is the current artifact; registry availability is not assumed. From the checkout:

npm install
node pipeline/cli.js help

The package defines two bins for an installed or linked copy: glina (the CLI, pipeline/cli.js) and glina-mcp (the MCP stdio server, pipeline/mcp.js). The rest of this page uses the checkout form where captured output matters.

See the surface

node pipeline/cli.js --help prints the current command table from the CLI's one command registry. Use node pipeline/cli.js <command> --help for one command. The CLI reference links each command to its full contract.

To keep a second accepted model as a variant of the first, use glina import second.glb --name alternate --variant-of first-id. glina workspace shows the parent link. glina preview scene renders the active asset on neutral ground through Blender; see the preview refusal and diagnostic contract.

Run the quality gate — no config, no vault, no Blender

verify works with defaults when the config file is absent:

node pipeline/cli.js verify assets/models/smok.glb --config /nonexistent.json

The repository's smok.glb passes the structural gate with 38 meshes, 748 triangles, five materials, and two moving clips. The command exits 0 and prints the complete report; no Blender session is needed when render smoke is disabled.

A failing gate exits 1 and names every reason in errors — see the verify walkthrough.

Check the toolchain

glina setup --check locates Blender and uv without installing them. glina doctor probes a real code round trip through the Blender MCP bridge; a present executable is not proof of a usable add-on. Plain setup provisions Blender and uv, but a connected Blender session is still required for rendering.

Configure for generation

Sculpting and studio generation need pipeline.config.json (default path: the repo/package root; override with --config):

cp pipeline.config.example.json pipeline.config.json   # then edit

Every secret in it must be a role://<role>/<field> reference — the loader refuses inline values:

An inline credential value is refused before a job starts with error: config key 'credentials.password' holds an inline value; secrets must be role://<role>/<field> references.

Store referenced credentials through Skarbiec's supported intake, never on a command line. config check validates the file and prints <resolved: ok> instead of the values. See configuration for every key.

Generate

glina sculpt "gothic dwarven tower, low-poly"        # LLM drives Blender
glina create "dwarven axe warrior" --race dwarves    # studio flow via Weles browser
glina doctor                                         # check the bridges first

Both flows end in the verification gate; a broken or off-budget asset fails the job. For agent hosts run glina-mcp (MCP reference); the desktop app runs these same commands once per operation.