ohmyclaw

Route coding tasks across multi-provider accounts with quota balancing and Plan→Work→Review cycles.

61|21|Updated Mar 25, 2026

Search Tags:#automation #routing #orchestration #multi-provider #multi-account #ohmyclaw

Ready to run

npx skills add https://github.com/jkf87/ohmyclaw --skill ohmyclaw

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: ohmyclaw
Source: https://github.com/jkf87/ohmyclaw/tree/main/skills/ohmyclaw
Command: npx skills add https://github.com/jkf87/ohmyclaw --skill ohmyclaw

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

OpenClaw harness for multi-provider multi-account routing to orchestrate complex coding tasks across Z.ai GLM and Codex OAuth, enabling rate-limit distribution, plan-driven workflows, and cross-provider model selection.

Core Features & Use Cases

Deterministic routing: routing.json + select-model.sh guide the model-choice and task routing.
Multi-account pools: pool.sh distributes work across account pools to balance quotas and cooldowns.
OMX-style composable verbs: exec, plan, review, ralph, team, etc., enable flexible, decentralized task execution.
End-to-end workflow orchestration: Plan → Work → Review with 5-perspective review and gap detection, plus bridge notifications.

Quick Start

Invoke the ohmyclaw skill via the /ohmyclaw slash command to display the HUD and routing dashboards.

Frequently Asked Questions about ohmyclaw

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

FAQPage Schema

How do I balance rate limits and cooldowns across multi-provider LLM accounts?▼

To balance rate limits and cooldowns across multi-provider LLM accounts, you need a deterministic routing engine that orchestrates work across account pools. ohmyclaw distributes coding tasks automatically, balancing quotas and cooldowns across Z.ai and OpenRouter/OpenAI Codex providers.

What is deterministic routing for multi-provider coding workflows?▼

Deterministic routing for multi-provider coding workflows uses a routing configuration and model selection script to guide task distribution. ohmyclaw implements this to orchestrate Plan, Work, and Review cycles across distributed accounts, ensuring predictable model-choice and task allocation.

How do I set up multi-account orchestration for Z.ai GLM and Codex OAuth?▼

Setting up multi-account orchestration for Z.ai GLM and Codex OAuth involves invoking a routing hub via slash command to display dashboards. ohmyclaw manages this by distributing work across account pools to coordinate plan-driven workflows and cross-provider model selection.

Can I automate Plan, Work, and Review cycles across different LLM providers?▼

Yes, you can automate Plan, Work, and Review cycles across different LLM providers using composable OMX-style verbs. ohmyclaw enables flexible, decentralized task execution with 5-perspective review, gap detection, and bridge notifications to keep agents aligned throughout the workflow.

Does multi-provider routing support Korean-language coding tasks?▼

Multi-provider routing supports Korean-language coding tasks through deterministic orchestration. ohmyclaw is explicitly applied to distributed multi-account coding workflows and Korean-language tasks, coordinating execution and evaluation across Z.ai and OpenRouter/OpenAI Codex providers.

What are the limitations of deterministic routing for rate-limit management?▼

Deterministic routing for rate-limit management relies on routing configurations and account pool distribution scripts. ohmyclaw requires proper setup of these components to function, and its effectiveness depends on accurate quota and cooldown balancing across the configured providers.