Types

Types (MANAGE ▸ Types) define the kinds of assets your project works with (e.g. character, shot, cut, daily, LoRA). Each type carries the load-bearing facets that shape an asset: its tool profile, its metadata schema, its folder structure, and its repo type. Types are listed one per row.

Each row surfaces the type's facets as chips:

• Tools — how many tools (tabs) the type opens with
• Schema — the number of structured metadata fields
• Folders — the folder structure created for new assets of this type
• Repo — the repository type used for its files

Built-in types are seeded by Loft and read-only, but each can be toggled on or off per project. Custom types are project-scoped — use Add Type to create one with its own name, tools, schema, and folders. Editing a built-in Customizes it: Loft saves a project-specific copy that overrides the shared default for this project only.

Click a row to open the editor. It's organized into sections:

• Basic — name, code (fixed once the type exists), icon, and description
• Default tools — the tabs every new asset of this type opens with; users can still add or remove tools per-asset later
• Metadata schema — the structured fields shown under the Properties tool (users can still add per-asset custom fields there without touching the schema)
• Folder layout — repo type plus the folders created when an asset is initialized

The Metadata schema is a list of compact cards — one per field, showing its label, key, type, and group at a glance. Click a card to edit that field in a modal, use the trash icon to remove it, or Add fieldto create one. Each field has a key (machine name, auto-derived from the label), a label, a type (text / number / date), an optional group header, and optional placeholder hint.

A type's repo type decides how its files are version-controlled:

• None — no version control configured yet
• transport — Loft's resumable upload to the server (the default for new assets)
• git — legacy Git/LFS history and branches; opt-in for small text-based assets

New types default to None; an asset created without an explicit repo type gets transport. The Commit tab is opt-in — it appears only when the type (or an individual asset) includes the Commit tool. When it's shown for an asset whose repo isn't set up yet, the tab offers a form to configure version control (transport, or git for legacy assets) for that asset.

Not every registered type appears in the Add Asset picker. A few built-ins are kept out of it on purpose but still show here, badged:

• Hidden — plumbing or tool-only types (e.g. Library, AI Generation, Image Gallery) that back features under the hood; you don't hand-create them.
• Beta — types whose authoring flow isn't ready yet (e.g. AI Checkpoint, AI LoRA).

This is separate from enable/disable: Disabled is a per-project opt-out you control, while Hidden/Beta are ship defaults. Anything hidden stays fully active — generation and libraries keep working; it just isn't offered as a thing you manually add.