Product Surface & Workflow

Understand how chat, library, workspace, scheduling, and settings fit together as one creator runtime.

Start by seeing one continuous product surface

DreamCreator is not a single-purpose screen. It organizes chat, library, workspace, scheduling, and settings into one continuous creator runtime. The most useful mental model is:

  • chat handles goals, research, and execution coordination
  • the library holds tasks, files, and state
  • the workspace keeps subtitles, preview, styles, and exports inside project context
  • scheduling and settings turn one-off actions into something that can keep running

Chat is an entry point, not just a message box

Chat is where work gets framed, refined, and pushed forward. You can select assistants, change models, call tools, inspect execution feedback, and then continue into files and tasks without leaving the app.

That is why DreamCreator describes itself as an executable AI assistant rather than a conventional chat surface. The value is not the generated text by itself, but whether the system can continue moving the work.

The library holds tasks, assets, and history

Most workflows enter the system through the library. Download jobs, imports, subtitle tasks, transcoding tasks, and their outputs become persistent records there.

That structure matters because:

  • task status stays visible
  • outputs do not disappear into temporary folders
  • finished work can continue into the next step without losing context

The workspace is where follow-up work stays connected

Once downloads finish or subtitle work begins, the workspace takes over the “continue processing” part of the job. Video preview, subtitle timing, styles, and export settings stay around the same project context.

This is one of the main differences between DreamCreator and a fragmented toolchain. You do not need one app for download, another for subtitles, and another for final delivery.

Scheduling and settings determine whether the app can work long-term

Once DreamCreator starts carrying daily work, scheduling and settings stop being side pages.

  • settings determine whether providers, external tools, skills, memory, connectors, and channels are healthy
  • scheduled jobs determine whether a workflow can only be run manually once or can continue over time