Projects & Albums

A project owns a generation workflow, output settings, draft and execution records, and a durable result collection. Project data is user-scoped and stored in PostgreSQL; media is stored under the user's project prefix in the configured object store.

Project Types

Choose the type according to the output you want:

Project type	Output	Common settings
Text	Generated text	System prompt, temperature, maximum tokens
Image	Generated images	Aspect ratio, quality, format, background
Video	Generated video	Duration, resolution, sound, format
Audio	Speech or music, depending on model	Voice/speaker or music mode, output format

Available controls come from the selected model profile. A project also stores a default provider/model, description, filename prefix, shuffle setting, and workflow.

Project Management

The Projects screen supports search, pagination, and active/archived/all filters. You can:

• Create, edit, and permanently delete projects.
• Archive a project to remove it from the default active view, then restore it later.
• Duplicate a project by starting a new project with an existing workflow as the source.
• Rename project folders from the project list.

Archiving is organizational; it does not delete jobs, media, exports, or storage. Deleting a project removes its workflow records, jobs, album records, project objects, and associated export tasks/files. Move individual album items to the recycle bin when you need a recoverable deletion.

Project Workspace Tabs

Draft

Drafts are resolved workflow combinations that have not started. Each stores its prompt, media contexts, provider/model choice, output options, filename, and workflow snapshot. Start one, a selection, or every draft.

Queue

Pending, processing, and failed jobs appear in Queue. You can inspect resolved prompts and contexts, retry failures, delete records, or operate on a selection. See Queue & Concurrency.

Done

Done holds completed job records. It is useful for inspecting or reusing the exact configuration that produced a result. Removing a completed job record is separate from deleting the corresponding durable album item.

Album, Texts, or Audios

The final tab is named for the project modality. It contains durable AlbumItem records created by generation or direct upload:

• Image and video projects provide visual browsing and a lightbox/player.
• Text projects show generated text and its prompt/context; multiple text results can be compared.
• Audio projects provide audio result controls.

The collection supports selection, page-size choices, filename changes, export, copy-to-library, workflow reuse, and recycle-bin deletion. The active tab, page, and supported filters live in URL search parameters, so navigation and shared links can preserve the same view.

Copying Results to a Library

Copy selected results or the entire collection into a compatible library. You may create a library from the dialog or append to an existing library of the project output type.

For generated media, choose:

• Optimized — smaller derived asset when available.
• Raw — original generated/uploaded asset.

Copying creates library items; it does not move or delete the album results.

Exports

Export selected album items or the full collection as a named ZIP. For supported assets, choose raw or optimized versions. Image projects can open the watermark configuration screen before queueing the archive.

Exports run outside the generation queue in their own persistent worker and appear on the global Exports page. See Exports & Delivery.

Reusing Configuration

Job rows retain a workflow snapshot and resolved generation settings. The Reuse configuration action restores those settings into the project editor so a prior result or failure can be used as the starting point for new drafts.

The same action is available from the results themselves, so you can pick a setup by looking at the finished piece instead of a job row:

• Album, text, and audio entries each carry a Reuse workflow control that resolves the settings through the job that produced them.
• The image lightbox offers the same control (shortcut R), and closes on confirmation so you land on the restored workflow.

Reuse changes the current editable workflow/settings only after confirmation; it does not alter the old job or album item. The workflow snapshot lives on the job record, so reusing from an album item whose Done record was deleted reports that the workflow is no longer available.

Orphan Files

An orphan is an object under a project's storage prefix that is no longer referenced by a workflow item, job, album item, or protected trash record. Uploads, retries, edits, and interrupted operations can leave such objects behind.

The Project Orphans screen:

1. Lists every object below the user's project prefix.
2. Collects storage keys still referenced by direct media workflow steps, job outputs/contexts, album outputs/contexts, and trash items for that project.
3. Reports stored objects outside that referenced set, with preview and size where possible.

Selected orphans can be deleted in a batch.

DANGER

Orphan cleanup deletes directly from object storage and cannot be undone. It does not use the recycle bin. Trash records are included in the protected reference set, so valid recycle-bin media is not reported as orphaned.

Use orphan cleanup when project usage is unexpectedly high after many uploads, retries, or edits. It is not a routine replacement for deleting visible album items through Trash.

Live Updates

An authenticated WebSocket project hub publishes job, album, trash, and project changes. The viewer refreshes the relevant data when events arrive and falls back to periodic refresh while work is processing if a live connection is unavailable.

The connection validates the user, account status, project ownership, and session version. It does not expose another user's project events.

Related

• Workflows & Combinations — how drafts are composed.
• Recycle Bin — recoverable album deletion.
• Libraries & Prompts — reusable inputs and result copying.