> ## Documentation Index
> Fetch the complete documentation index at: https://docs.cyberun.cloud/llms.txt
> Use this file to discover all available pages before exploring further.

# Models

> Custom checkpoints, LoRAs, and other model files distributed to your team's agents.

A **model** in Cyberun Cloud is a file (a checkpoint, a LoRA, an
embedding, a ControlNet, or a custom kind) that your team has uploaded
to the platform. Models are distributed to eligible agents so
workflows can reference them by name.

If custom models aren't enabled on this deployment, the **Models** entry
won't appear in the sidebar.

## What a model record holds

* **Display name** — the human-readable label shown in lists and
  parameter pickers. Up to 255 characters.
* **Type** — the ComfyUI models subdirectory the file belongs to
  (`checkpoints`, `loras`, `vae`, `controlnet`, …). Free-form
  string up to 50 characters — use the directory name your
  workflows expect.
* **Path** — relative path inside the agent's ComfyUI models
  directory (e.g. `models/checkpoints/sdxl_base_1.0.safetensors`).
  Required. Cannot be absolute or contain `..`.
* **Size and content hash** — file size in bytes, plus a content
  hash, recorded at upload as integrity metadata.
* **Status** — `active` (default; agents include it in their sync
  set) or `disabled` (kept in the catalog but excluded from sync).

## How models reach agents

When an agent connects and that team owns models marked `active`,
the agent pulls each file into its local cache. The agent
advertises status `syncing` (with a per-file progress percentage)
during the download. Tasks dispatched to that agent wait while it
syncs.

Once cached, subsequent tasks reuse the local copy. The first task
on a fresh agent is the slow one; later runs are not.

You don't need to push manually. Upload to the **Models** page, and
the next agent that needs the file fetches it.

## Updating a model

The model record's editable metadata is **display name**, **type**,
**path**, and **status**. Editing those does not change the file
bytes — the file uploaded at create time is the file that ships to
agents.

To ship different bytes under the same conceptual name, upload a
new record. To stop a model from syncing without deleting it, set
its status to `disabled`.

## Deleting a model

Deletes the record from Cloud. Agents may keep the cached file on
disk until they evict it locally; new agents will not see the
model.

## Related

* [Upload a model](/cloud/guides/upload-model) — walkthrough.
* [Custom nodes](/cloud/concepts/nodes) — for distributing custom
  node packages instead of model files.
* [Workflows](/cloud/concepts/workflows) — where models are
  referenced.