# Supporting surfaces

Beyond the headline views, the Stage hosts a set of supporting surfaces — a media vault, a session library, recalled memory, the usage meter, schedules, and a file explorer.

## Media — the asset vault

The media surface is a gallery of standalone assets: files you shared and one-offs the agent generated — images, audio, video, PDFs, generated docs and data — kept separate from your project files. Tiles show a thumbnail where they can, badge each asset’s origin (shared, or which agent made it), filter by type, and download on hover. Click one to preview it on the Stage.

## Library — everything this session used

The library collects everything the session produced or touched — files, attachments, links, and generated artifacts — in one filterable list. Click an item to re-open it: a file opens the editor, a link opens the browser surface.

## Memory — what the Den recalled

The memory surface is a read-only view of what the memory den recalled for the current context, grouped by layer — Session, Project, and You — with each memory’s category and when it was learned. It’s how you see why the agent knows what it knows.

## Usage — the session bill

The usage surface is the session’s token-and-cost meter: headline totals (cost, tokens in, tokens out), a live context-window fill, and a per-model breakdown. Everything routes through the gateway, so this is the real, attributable cost for the session.

## Schedule — automations

The schedule surface lists triggers and scheduled automations for deployed agents — one row per schedule with its cadence, next run, last outcome, and enabled state.

## Files — the explorer

The directory surface is a navigable folder listing — a real file explorer on the Stage. It lists a folder live, navigates in place with its own breadcrumb, sorts folders before files, and opens any file as its own Stage surface.

> Resilient by designThe Stage maps each surface kind to a renderer, and a kind with no renderer yet degrades to a friendly placeholder rather than a crash — so new capabilities can appear on the Stage the moment the engine starts emitting them.