omniroute-cli-cloud

Orchestrate cloud coding agent tasks via OmniRoute CLI.

44.0k|5.9k|Updated Feb 13, 2026
One-click install
npx skills add https://github.com/diegosouzapw/OmniRoute --skill omniroute-cli-cloud
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: omniroute-cli-cloud
Source: https://github.com/diegosouzapw/OmniRoute/tree/main/skills/omniroute-cli-cloud
Command: npx skills add https://github.com/diegosouzapw/OmniRoute --skill omniroute-cli-cloud

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It removes the friction of managing coding agent workflows across multiple providers by giving you a single CLI interface to create, monitor, and control cloud tasks.

Core Features & Use Cases

  • Agent authentication & provider setup: Configure OpenAI Codex, Devin, and Jules (Google) with the required keys or OAuth flow.
  • Task orchestration: Create tasks, list them, fetch full task records, and poll status until completion or failure.
  • Execution control & collaboration: Approve plans for agents that pause, message running tasks, inspect touched sources, and cancel tasks.
  • Use Case: When you want to refactor an auth module or fix failing tests, you can create a cloud task, approve the plan if needed, and then review exactly which files were changed.

Quick Start

Tell the OmniRoute CLI to create a Codex cloud task titled "Refactor auth module" with the prompt "Extract JWT logic to src/auth/jwt.ts".

Frequently Asked Questions about omniroute-cli-cloud

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

FAQPage Schema
How do I manage cloud coding agent tasks from a terminal?

You can manage cloud coding agent tasks from a terminal by using a CLI interface to create, monitor, and control workflows. This provides a single command-line entry point for task orchestration across multiple providers, including status polling and task cancellation.

Can I control OpenAI Codex, Devin, and Jules from the same command line tool?

Yes, you can control OpenAI Codex, Devin, and Jules from the same command line tool. The CLI supports agent-specific authentication and orchestrates task lifecycle actions like plan approval and messaging for these specific cloud agents deterministically.

How do I approve a plan or message a running cloud coding task?

To approve a plan or message a running cloud coding task, you use specific CLI commands driven by the task ID. This allows you to interact with agents that pause for plan approval or send messages during active execution directly from your terminal.

Do I need separate authentication setup for each cloud coding agent?

Yes, you need separate authentication setup for each cloud coding agent. The CLI requires correct agent-specific authentication, such as required keys or OAuth flows, to manage tasks for Codex, Devin, and Jules successfully.

What is the best way to inspect which source files a cloud agent changed?

The best way to inspect which source files a cloud agent changed is using the CLI's source inspection commands. By providing the specific task ID, you can review exactly which files were touched during the task lifecycle after polling reaches completion.