Modify OmniFlow Runtime
Treat the packaged runtime as immutable. Make focused Python edits through the Android-managed developer override.
Workflow
- Call
get_omniflow_python_overridewithout a path and record the runtime version and modified files. - Call it again with the exact
omniflow/**/*.pypath to read current source and SHA-256. - Change one owning file with the smallest coherent edit.
- Call
apply_omniflow_python_overridewith the path and complete file content. It validates Python syntax, restarts the worker, checks the runtime contract, and rolls back on failure. - Exercise the affected operation. Use
reload_omniflow_python_overrideonly when a clean worker restart is needed without another edit. - If the override is unhealthy, call
clear_omniflow_python_overridewithconfirm=trueto restore the pinned runtime.
Ownership
- Modify planner and prompts under
omniflow/vlm/. - Modify retry, checker, replay, and execution policy under
omniflow/runtime/. - Modify Function and RunLog behavior in their OmniFlow packages.
- Do not modify, replace, or emulate OmniTransfer. Failed target mappings must use the normal VLM fallback and must never replay source-device coordinates silently.
- Do not weaken payment confirmation or other user-consent boundaries.
Apply whole-file content only. Never write directly into the pinned runtime installation directory.

