cc: @straight-sundown-84319 @millions-afternoon-47582 Please see this PR fix: make local runtime use host-writable paths and local cache defaults TL;DR: Wang Siyuan is trying to use V1 Web UI + process/local app-server. We figured below that

RUNTIME=local

goes to V0 pathways through the code. And V0 has a bug, a paths issue they are fixing in the PR. Follow-up question below. What kind of fix do we prefer, among these 1, 2, 3 options in the thread below, or maybe some other? I'm not sure if you still use local runtimes on the cloud, and if that PR affects stuff.

Quick update on `RUNTIME=process`: On current

main

,

RUNTIME=process

still fails at startup: •

StandaloneConversationManager.__aenter__

→

get_runtime_cls(config.runtime).setup(...)

•

get_runtime_cls

only knows

eventstream/docker/remote/local/kubernetes/cli

• So

RUNTIME=process

raises

ValueError: Runtime process not supported

(the success I saw before was on a custom branch where V0/legacy lifespan was disabled). So on vanilla

main

, setting

RUNTIME=process

still walks the legacy runtime init path and blows up. So maybe possible fix directions are: 1) keep RUNTIME (or OH_LEGACY_RUNTIME) for legacy runtime only, and introduce a separate env for V1 sandbox (e.g., OH_SANDBOX_MODE / OH_SANDBOX_KIND) or 2) add a switch that skips the legacy conversation_manager/runtime setup and legacy routes, so process sandbox runs without touching legacy runtime.