August 21, 2026
A running Pod's assets are now fully editable — inject, remove, or swap without a restart — plus staging on stopped Pods and a path-grouped assets view.
Until now, changing what’s on a Pod usually meant an edit and a restart. This release makes a Pod’s asset set editable live: linked assets can be injected while the Pod runs, attached assets can be removed or swapped in place, and stopped Pods accept assets ahead of their next start.
Major features
Section titled “Major features”Inject linked assets into a running Pod
Section titled “Inject linked assets into a running Pod”Linked assets — Hugging Face and CivitAI imports and direct-link registrations — previously could only be added when a Pod started. They can now be injected into a running Pod: the download runs alongside your workload and the files appear in place, with no restart and no interruption. Downloads run one at a time per Pod; each shows its place in the queue, then live progress with size and — once the transfer speed settles — time remaining, and an in-progress download can be canceled. Read more →
This also completes ComfyUI model sets in place: inject a set’s missing member and the bundled workflow arrives on its own within a few minutes — no restart needed. Read more →
Remove or swap assets without a restart
Section titled “Remove or swap assets without a restart”Assets can now be removed from a running Pod: Remove deletes that asset’s files from the Pod, and Swap replaces it with another asset in the same location. Each removal shows its own state while it runs, and one that stalls returns to its attached state automatically — typically within about 15–20 minutes — so the Pod never gets stuck. Read more →
Stage assets on a stopped Pod
Section titled “Stage assets on a stopped Pod”A stopped Pod now accepts new assets in advance: they appear as Scheduled and are downloaded and placed automatically the next time the Pod starts — no need to start the Pod first just to add files. Staging applies to assets held in storage; linked assets are fetched by the running Pod itself, so inject those once it’s up. Read more →
Improvements
Section titled “Improvements”- Aim injections at a subfolder. When adding an asset to a Pod you can type a subfolder under the destination path, so files land exactly where your tools expect them instead of only at the folder root.
- Assets grouped by destination. The Pod’s Assets tab now groups assets by the folder they land in inside the Pod, so it’s clear what each folder contains, which paths can accept files right now, and where new files will go. The add-assets dialog shows each asset’s destination up front the same way.
- Delete local storage with the Pod. The Pod delete confirmation can now delete the Pod’s attached local storage in the same step. Previously the volume was always left behind — still billed for the space it occupied — and had to be found and deleted separately.
- Failure messages that match the source. Asset download failures now explain what actually went wrong for each source — an expired or broken direct link, a missing Hugging Face or CivitAI token — and the retry action matches the fix, instead of one generic error. The message shown for partially selected assets was also corrected: deselected files are removed on the next restart.
- Assets added to a running Pod are now reliably kept when the Pod is stopped and started again, restarted, or edited — previously some could silently disappear after these operations. Conversely, removed assets no longer come back after a restart, and leftover files from removed assets are cleaned up fully, including in subfolders and on split volumes.
- Opening a page for something that no longer exists shows a clear “not found” response instead of a server error, and Pod detail pages no longer fail to load when they reference items that have since been deleted.
- Tightened access checks on workspace activity views.