# Web Workspace

Use the web app when people need to see the media, compare actual results, make
the selection, organize the Space, or collaborate. The CLI and MCP operate on
the same state; changes appear across all three interfaces.

## Review a Space

Open a Space to see its Assets on the full-screen canvas. Search by Asset name,
open an Asset to compare its Variants, and open Variant details to inspect its
prompt, Recipe, References, status, and media facts.

The main Variant represents the Asset on the Space canvas. From a completed
non-main Variant, choose **More → Use as main variant** to change that
selection explicitly.

## Continue or replay a Variant

Use **Vary…** to restore a completed Variant's Recipe in Forge and change its
prompt, model, References, or media settings. Vary creates a sibling Variant in
the same Asset. Use **More → Regenerate unchanged** to run the exact Recipe
again without opening Forge.

Use **Fork into new Asset** to restore and edit the Recipe while branching into
a new Asset. Use **Derive new Asset** when the selected Variant should become an
explicit input to a new Recipe. Use **Copy to new Asset** for the same media
bytes and no provider call.

A failed Variant remains visible. Use **Retry** when the same Recipe should run
again unchanged. If the creative instruction or settings should change, start
Vary from a completed Variant instead.

Generation started through the CLI or MCP appears in the same Space canvas and
generation tracker as Web work. The durable Asset, Variant status, and Recipe
are the source of truth; the browser that started a run does not need to remain
open.

## Inspect history

Open **Variant details → History** to see exact input Variants and the
Regenerate, Vary, Fork, and Copy origin and descendant groups. **View full
history** loads the bounded ancestor and descendant graph. Relationships are
read-only facts derived from Recipes, not editable canvas connectors.

## Organize the Space

Type and Recent are automatic views: they always reflect the Space and are not
editable containers. Collections are saved, user-curated sets. An Asset stays
in its automatic view and may belong to more than one Collection.

Use the folder action on an Asset to add or remove it from a Collection without
leaving the canvas. For many Assets, enter selection mode, narrow the Space with
search, choose **Select all matching**, then apply one Collection action. Drag an
Asset onto a visible Collection for the direct-manipulation shortcut.

Open **Collections** to create, find, rename, show, hide, or delete Collections.
This compact panel manages Collections themselves rather than loading every
Asset into a separate organizer. Collection changes do not alter media, Recipes,
or References.

## Copy, update, and delete

Use **Copy to new Asset** from Variant details to create a new Asset from the
selected media without generation. Renaming an Asset changes its mutable metadata without
creating a Variant. Asset and Variant actions can also copy their stable public
references for use in the CLI, MCP, or another collaborator's message.

Asset and Variant actions expose permanent deletion for eligible objects.

There is no trash:

- activate another completed Variant before deleting the current main Variant;
- delete the Asset to remove its only Variant;
- deleting a Collection keeps the Assets it organized;
- deleting a Space removes the complete Space and its stored media.

Destructive actions require confirmation and current permission.

## Choose another interface

Use the [CLI](/docs/cli) for terminal automation and local file transfer. Use
[MCP](/docs/mcp) for structured agent operations. See [Core
Concepts](/docs/concepts) for the shared product model.