omniflow-runtime-modifier

Inspect, edit, validate, and hot reload the OmniFlow Python runtime through developer override tools.

2.0k|140|Updated Mar 18, 2026
One-click install
npx skills add https://github.com/omnimind-ai/OpenOmniBot --skill omniflow-runtime-modifier
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: omniflow-runtime-modifier
Source: https://github.com/omnimind-ai/OpenOmniBot/tree/main/plugins/omni-vlm-lite/agent-skill/omniflow-runtime-modifier
Command: npx skills add https://github.com/omnimind-ai/OpenOmniBot --skill omniflow-runtime-modifier

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Modifying the packaged OmniFlow Python runtime inside OpenOmniBot is risky because direct edits to the pinned installation can break the VLM planner, GUI execution policy, and replay logic with no recovery path. This Skill provides a controlled workflow for making focused runtime changes through the official Android-managed developer override, with automatic validation and rollback.

Core Features & Use Cases

  • Safe Runtime Inspection: Read current OmniFlow Python source files with SHA-256 checksums and track which files have been modified before making changes.
  • Validated Hot Reload: Apply whole-file edits that are syntax-checked, contract-verified, and automatically rolled back if the worker restart fails.
  • Recovery and Reset: Restore the pinned runtime at any time by clearing the override, or force a clean worker restart without new edits.
  • Use Case: You need to adjust the VLM planner prompt in omniflow/vlm/ to improve GUI automation accuracy. Use this Skill to read the current file, apply a minimal edit, and let the override tool validate and reload the worker, rolling back automatically if the runtime contract breaks.

Quick Start

Use the omniflow-runtime-modifier skill to inspect the current OmniFlow planner file and safely apply a prompt change with automatic validation and rollback.

Frequently Asked Questions about omniflow-runtime-modifier

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I modify the OmniFlow Python runtime in OpenOmniBot?

Use the get_omniflow_python_override tool to read the current source and SHA-256 of a file, then call apply_omniflow_python_override with the complete edited file content. The tool validates syntax, restarts the worker, checks the runtime contract, and rolls back on failure.

How do I recover the OmniFlow runtime after a bad edit?

Call clear_omniflow_python_override with confirm=true to restore the pinned runtime installation. The apply tool also rolls back automatically when validation or the runtime contract check fails after a worker restart.

Which OmniFlow files can I edit with the developer override?

You can edit planner and prompt files under omniflow/vlm/, retry, checker, replay, and execution policy files under omniflow/runtime/, plus Function and RunLog behavior in their OmniFlow packages. OmniTransfer must never be modified or emulated.

Can I edit the pinned OmniFlow runtime directory directly?

No, the packaged runtime is treated as immutable. All changes must go through the developer override tools with whole-file content, never partial patches or direct writes into the pinned installation directory.

What safety boundaries does the OmniFlow override enforce?

The workflow forbids weakening payment confirmation or other user-consent boundaries, and failed target mappings must use the normal VLM fallback rather than silently replaying source-device coordinates.