VAMOS Studio

VAMOS Studio is an experimental Panel application for inspecting canonical run and study artifacts, visualizing Pareto fronts, and trying local problem definitions. Its inspection paths use the same inert, data-only readers as the stable Python API; loading a study or run does not execute recorded code.

Launching Studio

Install the optional UI dependencies, then launch the console command:

pip install "vamos-optimization[studio]"
vamos studio --study-dir results/

The server binds to 127.0.0.1:5006 by default. To choose another loopback address or port:

vamos studio --address ::1 --port 5010 --study-dir results/

A non-loopback address is rejected unless you separately acknowledge the network exposure:

vamos studio --address 0.0.0.0 --allow-remote-binding --no-browser

Remote binding exposes an experimental local application to other network users. Apply operating-system firewall and access controls appropriate to the environment; Studio does not provide an authentication boundary.

Trusted local Python

The Problem Builder can compile and execute Python entered by the user or generated by an LLM. This is disabled by default. Before a preview can run, Studio displays the complete objective and constraint code and requires the user to select an explicit acknowledgement for the current code. Editing or regenerating that code clears the acknowledgement.

Trusted local Python code executes with the permissions of your current operating-system user. Review the complete code before opting in.

Generated code is never executed automatically. Syntax-tree validation, restricted built-ins, a child process, timeouts, and best-effort resource limits reject some unsupported inputs and reduce accidental damage; they do not isolate untrusted Python and are not a security boundary. Do not opt in for code from an untrusted source. Studio does not log generated code or API-key values.

Generating a standalone script only displays text; running that exported script remains a separate user action outside Studio.

Data-only exploration

The Results page reads vamos.run-manifest and StudyManifest artifacts through load_run, load_result, and load_study. It does not resolve plugins, reconstruct components, or invoke replay. Use the explicit stable vamos reproduce command when execution is intended.

Studio also provides experimental ranking and export helpers. These features are not part of the stable VAMOS 1.x compatibility surface.

Optional dependencies

Interactive plots and tables use Panel, Plotly, and pandas from the studio extra. Provider-backed code generation may require a provider-specific API key. Prefer environment-based credentials; values entered in the password field are held only in the running process and are not included in Studio status output.