Studio

Introduction

WorldFoundry Studio is a thin visual entrypoint around repo pipelines. The model is fixed at launch time; use a new process for a different model family.

Studio exposes multiple frontends:

What it shows

By default, Studio hides most advanced panels. Use --show-aux-panels for history, notes, catalog, 3DGS import, and low-level runtime controls.

Workspace Mode

For multi-model validation and release QA, run the workspace app instead of a single-model Studio process:

source tmp/worldfoundry_unified_env.sh
conda activate "${WORLDFOUNDRY_UNIFIED_ENV_PREFIX}"

bash scripts/workspace/run_workspace.sh \
  --host 127.0.0.1 \
  --port 7870 \
  --max-jobs 8

Use explicit roots when your checkpoints or benchmark data live outside the default cache:

bash scripts/workspace/run_workspace.sh \
  --ckpt-dir /path/to/checkpoints \
  --data-dir /path/to/benchmark-data

The launcher is open-source friendly and does not depend on machine-specific paths. It resolves assets in this order: command-line option, already exported environment variable, repo-sibling ckpt/ or data/ directory when present, env-file value from tmp/worldfoundry_unified_env.sh, then ~/.cache/worldfoundry/....

Start the Workspace from the unified model runtime environment, not from a lightweight UI-only environment. For CUDA 12.8 hosts this is usually worldfoundry-unified-cu128 after source tmp/worldfoundry_unified_env.sh. If LOAD or START fails with a missing import such as cv2, restart 7870 from that unified environment before debugging model code.

Do not copy or relocate a prepared conda environment between machines. Native Python and OpenSSL links can point back to the original prefix, which makes resident inference workers fail even when the browser server starts. If the Workspace reports a missing python3.x, missing cv2, or libssl/libcrypto error, recreate or verify the unified env through the public setup command:

bash scripts/setup/bootstrap_worldfoundry.sh --verify-only
source tmp/worldfoundry_unified_env.sh
bash scripts/workspace/run_workspace.sh

Open:

http://127.0.0.1:7870/

The workspace is the preferred UI for release validation. Use it to submit inference jobs, inspect model-specific forms, review artifacts, and compare runs without switching between multiple one-off scripts.

Workspace also supports evaluation jobs. For VBench, select Evaluation, choose benchmark vbench, put generated videos in Dataset Root (or an official VBench results JSON in Results Path), and set Metrics to one or more dimensions such as aesthetic_quality, motion_smoothness, or the preset custom_supported. VBench-specific runtime options such as {"mode":"custom_input","load_ckpt_from_local":true} go in Eval Runtime JSON.

Create Job configuration

There is no separate Settings page in the Workspace UI. Configure each job in the Create Job dialog before submission.

When you open Create Job or switch task profiles, the form is prefilled from Workspace defaults loaded at startup. Model-specific official demo values from the catalog and task profile still take precedence over those shared defaults.

Default values when no settings file is present:

Optional persisted defaults

To reuse the same defaults across Workspace restarts, point the server at a JSON settings file:

export WORLDFOUNDRY_STUDIO_SETTINGS_FILE=/path/to/studio-settings.json

On startup, the Workspace loads that file into /api/settings. The Create Job form reads those values through GET /api/settings. Operators can also update the file programmatically with POST /api/settings:

curl -sS -X POST http://127.0.0.1:7870/api/settings \
  -H 'Content-Type: application/json' \
  -d '{"values":{"fps":12,"num_frames":49,"attention_backend":"torch"}}'

When WORLDFOUNDRY_STUDIO_SETTINGS_FILE is unset, defaults live only in the running Workspace process and reset on restart.

Fast jobs and preflight checks

Workspace inference defaults to a fast job path. It assumes the selected conda environment, checkpoint roots, and viewer dependencies were prepared before the server was launched. Keep this default for normal repeated inference.

Turn checks on only for setup debugging or release preflight:

For the fastest finish path, model runtimes should return explicit preview_image, preview_video, artifact_paths, rrd_path, and output_dir values in their run record. Use always scanning only as a compatibility mode for older runtimes that write files without reporting them.

Resident workers keep the conda child process alive across jobs so the child StudioManager can reuse its pipeline cache. Set WORLDFOUNDRY_STUDIO_RESIDENT_WORKERS=0 when debugging process startup or when you need every job to release GPU memory immediately after completion.

Use Visualizers, Gallery, and Artifacts for quick visual QA. They expose recent generated videos, images, manifests, and direct artifact links. Before making release claims, record the verified run in the model inference validation page.

Workspace Visualizers

The 7870 Workspace is the browser entrypoint for the visualization stack. Open the Visualizers tab, then use each card's Launch, Open, and Stop buttons. The iframe under each card embeds the live viewer, so users do not need to copy URLs during normal QA. The Embodied Simulator Bridge card is marked Planned: unlike Viser, Spark, Rerun, and World Rollout, it does not yet launch an in-tree embodied viewer.

World Rollout Viewer

• Port7868
• Aliasesinteractive-world, world-model, world-rollout

Buffered realtime target for action-conditioned roaming. Controls are sampled continuously while generated chunks are prefetched.

Artifactsimage, video, action_trace

Launch routepython -m worldfoundry.studio.app matrix-game-2 --frontend world --port 7868

Viser Geometry Viewer

• Port18590
• Aliasesviser, geometry, pointcloud

Point clouds, depth-derived point sets, meshes, camera poses, and trajectories.

Artifactsply, pcd, xyz, glb, gltf, obj, npz

Launch routepython -m worldfoundry.studio.app pi3 --frontend points --asset /path/to/scene.ply

Rerun Timeline Viewer

• Port9876
• Aliasesrrd

`.rrd` timelines and recordings with synchronized cameras, frames, tracks, and 3D entities.

Artifactsrrd

Launch routepython -m worldfoundry.studio.app vggt --frontend rerun --asset /path/to/recording.rrd

Spark Gaussian Splat Viewer

• Port8765
• Aliases3dgs, splat

3D Gaussian splats via the in-tree Spark frontend. Live preview uses the Spark.js Hello World butterfly demo.

Artifactssplat, spz, ksplat, sog, splat-ply

Launch routepython -m worldfoundry.studio.app vggt --frontend spark --asset /path/to/scene.splat

Embodied Simulator Bridge

Planned

• Port18610
• Aliasessim, simulator

Planned integration. Studio only registers an external simulator URL and tunnel hints today; there is no in-tree embodied viewer yet. Start the simulator separately, then paste its URL in Visualizers.

Artifactsaction_trace, trajectory, simulator_url

Launch routepython -m worldfoundry.studio.app openvla --frontend embodied --simulator-url http://127.0.0.1:18610

world defaults to port 7868. Set a port manually only when your deployment requires a fixed proxy route.

For remote workstations, expose the Workspace port and the viewer ports you use. For example:

ssh -L 7870:127.0.0.1:7870 \
    -L 18590:127.0.0.1:18590 \
    -L 8765:127.0.0.1:8765 \
    -L 9876:127.0.0.1:9876 \
    user@host

Artifact Visualization Routing

When an inference job finishes, the Workspace scans the run record and output directory for visualizable artifacts. The Artifacts tab shows Open and Open in ... actions for supported files. Job Detail keeps inline preview video/image only; it does not duplicate viewer launch shortcuts.

Open the run in Workspace and use the Artifacts tab to confirm viewer routing for files that already exist on disk. The table above is the routing reference; the Artifacts actions are authoritative for a specific run.

For model authors, the most reproducible path is to write outputs under the Studio run output directory and include stable paths in the run record:

• preview_image or preview_video for quick media review.
• artifact_paths for raw generated assets.
• rrd_path for Rerun recordings.
• output_dir for additional files that should be discoverable from the run.

3D reconstruction models should export browser-readable geometry such as .ply, .glb, .gltf, .obj, .pcd, .xyz, or compact point-cloud/depth .npz files. 3DGS models should export a native splat file, or a binary little-endian Gaussian-splat PLY whose header contains splat attributes such as scale, rotation, opacity, and spherical-harmonic color fields. The Workspace distinguishes ordinary PLY geometry from Gaussian-splat PLY files before choosing Viser or Spark.

Studio Screenshots

These screenshots are from the 7870 workspace used for model release validation.

Inference Jobs

The queue shows submitted runs, final status, and inline preview video or image when the run record exposes them.

Create Job

The form should expose the model's actual input contract. The screenshot below is only a UI-shape example; release demo claims should be checked against the validation reference and the matching run manifest.

Catalog

Catalog filtering is useful for checking which world-model entries are visible to the workspace before submitting jobs.

Gallery

The Gallery gives a compact visual pass over recent inference outputs and preview artifacts.

Inference Demo Results

The gallery below is for visual orientation. It shows representative artifacts from in-tree Studio or Studio-compatible API runs. It is not a release-claim table; exact parameters, environment notes, run ids, and remaining gaps live in the validation reference. Only curated nontrivial examples are embedded here.

Launch matrix

Recommended local start:

cd /path/to/WorldFoundry
PYTHONPATH=. WORLDFOUNDRY_STUDIO_PORT=7868 conda run -p "${WORLDFOUNDRY_UNIFIED_ENV_PREFIX}" python -m worldfoundry.studio.app \
  lingbot-world \
  --variant fast \
  --model-ref /path/to/checkpoints/lingbot-world-fast \
  --device cuda:1

For an editable checkout that is not installed into the active environment, keep PYTHONPATH=. in the command.

Studio prints the resolved workspace, model, cache, and Hugging Face cache roots at startup, so path issues are visible before a run begins.

Open:

http://127.0.0.1:7868

For remote GPU nodes, use the SSH tunnel printed by Studio.

The world frontend follows the same pattern as the LagerNVS Browser Viewer: the remote process serves both the page and the WebSocket control/frame-update channel, while the local browser reaches it through one tunneled port.

ssh -N -L 7868:127.0.0.1:7868 user@gpu-host
# local browser:
# http://127.0.0.1:7868

The world status strip shows WS VIEW ... / GPU ... so you can separate browser/network latency from model-side render latency. If WebSocket is unavailable, the page automatically falls back to the HTTP API.

Interaction modes

Keyboard/live controls:

WASD = move
Arrow keys / IJKL = look

Dragging a stick or holding a keyboard direction waits for the previous step to finish before sending the next request.

Launch flags

Environment

Only WORLDFOUNDRY_* Studio environment variables are supported.

Release Evidence

Only add public demo media after the matching official configuration has run through the in-tree Studio or Studio-compatible API path. Keep the run manifest, decoded media metadata, and visual QA record with the validation artifacts so the embedded video can be traced back to an actual release candidate run.