# Complete Guide to CLI Tools Compatible with OmniRoute: 11 Native Integrations > Discover 11 CLI tools compatible with OmniRoute including Claude Code Codex Gemini and Cursor Streamline your workflow with native integrations and easy setup - Repository: [Diego Rodrigues de Sa e Souza/OmniRoute](https://github.com/diegosouzapw/OmniRoute) - Tags: how-to-guide - Published: 2026-08-31 --- **OmniRoute natively supports 11 command-line coding assistants—including Claude Code, Codex, Gemini, and Cursor—automatically registered via `bin/cli/cli-manifest.mjs` and configurable through dedicated setup scripts in `bin/cli/commands/`.** The diegosouzapw/OmniRoute repository provides a unified routing layer for AI-assisted development workflows. Understanding which CLI tools are compatible with OmniRoute is essential for developers configuring their local environment, as the system maintains a strict catalog of supported integrations backed by concrete implementation files. These tools are automatically discovered and loaded by OmniRoute’s CLI manifest, enabling seamless routing of requests to the appropriate provider. ## CLI Tools Compatible with OmniRoute: The Official Catalog OmniRoute maintains an authoritative list of **11 supported CLI tools** in [`docs/reference/CLI-TOOLS.md`](https://github.com/diegosouzapw/OmniRoute/blob/main/docs/reference/CLI-TOOLS.md). Each tool receives a canonical ID mapped to its implementation in `bin/cli/cli-manifest.mjs`. The supported CLI tools compatible with OmniRoute include: - **Claude Code** (`claude`) — Anthropic's model-driven code assistant. Aliases: `claude-code`, `cc`, `anthropic`. - **Codex** (`codex`) — OpenAI's coding assistant integration. - **Gemini** (`gemini`) — Google Gemini LLM for coding and chat workflows. - **OpenCode** (`opencode`) — Open-source LLM provider integration. - **Cline** (`cline`) — Proprietary coding assistant CLI. - **KiloCode** (`kilocode`) — Lightweight coding assistant optimized for speed. - **Continue** (`continue`) — Interactive code-completion CLI tool. - **Kiro-CLI** (`kiro-cli`) — Specialized interface for Kiro AI services. - **Cursor** (`cursor`) — Cursor AI code-assistant CLI. - **Droid** (`droid`) — Mobile-focused coding assistant. - **OpenClaw** (`openclaw`) — Community-driven open-source AI tool. ## Tool Registration Architecture in OmniRoute OmniRoute discovers CLI tools compatible with OmniRoute through a centralized manifest system rather than dynamic scanning. The **`bin/cli/cli-manifest.mjs`** file serves as the JavaScript registry that binds each tool's canonical ID to its implementation module, handling alias resolution and export name mapping. When the CLI initializes, it loads this manifest to determine available routing targets. Each entry specifies: - The canonical tool ID (e.g., `claude`, `codex`) - Alternative aliases for user convenience - Module paths pointing to handler implementations - Export names for the specific integration functions ## Configuring CLI Tools: Setup Commands and API Endpoints Each CLI tool compatible with OmniRoute requires profile-specific configuration managed through dedicated setup scripts. The **`bin/cli/commands/setup-*.mjs`** files (such as `setup-claude.mjs` and `setup-codex.mjs`) generate local configuration files, handle API key storage, and manage OAuth flows. For programmatic access, **`bin/cli/api-commands/cli-tools.mjs`** exposes REST endpoints that enable the dashboard UI to read and write tool settings. Dashboard logic in `src/app/(dashboard)/dashboard/providers/providerPageUtils.ts` consumes these endpoints to display tool categories and configuration states. ## Practical Commands for Managing CLI Tools Compatible with OmniRoute Use the following commands to interact with the supported toolset: **Listing all available integrations:** ```bash # Display the complete catalog of supported CLI tools omniroute cli-tools list ``` **Launching a specific tool with profile selection:** ```bash # Initialize Claude Code using a named profile configuration omniroute launch --tool claude --profile my-profile ``` **Configuring a new tool installation:** ```bash # Create a Cursor profile in the default directory (~/.cursor) omniroute setup-cursor --name my-cursor ``` **Retrieving stored configuration:** ```bash # Fetch the current settings for the OpenCode integration omniroute api get-api-cli-tools-opencode-settings ``` ## Critical Source Files for CLI Tool Integration Understanding the following files is essential for extending or debugging CLI tools compatible with OmniRoute: - **[`docs/reference/CLI-TOOLS.md`](https://github.com/diegosouzapw/OmniRoute/blob/main/docs/reference/CLI-TOOLS.md)** — Master documentation listing all supported tools with descriptions and external links. - **`bin/cli/cli-manifest.mjs`** — The JavaScript object registry mapping tool IDs to implementation modules and aliases. - **`bin/cli/commands/setup-*.mjs`** — Individual setup scripts (e.g., `setup-cursor.mjs`, `setup-gemini.mjs`) that bootstrap configuration files. - **`bin/cli/api-commands/cli-tools.mjs`** — API endpoint definitions for settings management via the UI. - **[`docs/reference/PROVIDER_REFERENCE.md`](https://github.com/diegosouzapw/OmniRoute/blob/main/docs/reference/PROVIDER_REFERENCE.md)** — Documentation for provider-specific registries and authentication flows. ## Summary - OmniRoute natively supports **11 CLI tools** including Claude Code, Codex, Gemini, Cursor, and OpenCode. - Tool discovery relies on **`bin/cli/cli-manifest.mjs`**, which maps canonical IDs and aliases to implementation handlers. - Configuration management occurs through **`bin/cli/commands/setup-*.mjs`** scripts and API endpoints in **`bin/cli/api-commands/cli-tools.mjs`**. - The master reference list lives in **[`docs/reference/CLI-TOOLS.md`](https://github.com/diegosouzapw/OmniRoute/blob/main/docs/reference/CLI-TOOLS.md)**, while dashboard integration is handled by `src/app/(dashboard)/dashboard/providers/providerPageUtils.ts`. ## Frequently Asked Questions ### How do I add a custom CLI tool to OmniRoute? OmniRoute does not support dynamic addition of CLI tools outside the official catalog. To add a new integration, you must modify **`bin/cli/cli-manifest.mjs`** to register the tool ID and aliases, create a corresponding **`bin/cli/commands/setup-[tool].mjs`** script for configuration handling, and update **[`docs/reference/CLI-TOOLS.md`](https://github.com/diegosouzapw/OmniRoute/blob/main/docs/reference/CLI-TOOLS.md)** with documentation references. ### What aliases exist for Claude Code in OmniRoute? According to the source manifest in `bin/cli/cli-manifest.mjs`, Claude Code responds to four identifiers: the canonical `claude`, plus the aliases `claude-code`, `cc`, and `anthropic`. All resolve to the same implementation module regardless of which alias you specify in `omniroute launch --tool`. ### Where does OmniRoute store CLI tool configuration files? Individual setup scripts in `bin/cli/commands/` generate configuration files in tool-specific directories (e.g., `~/.cursor` for Cursor). The **`bin/cli/api-commands/cli-tools.mjs`** endpoints provide the interface for reading and writing these settings programmatically, while the dashboard UI consumes these endpoints to display current configurations. ### Can I use web-based AI tools through OmniRoute's CLI interface? No. OmniRoute maintains separate routing layers for web and CLI tools. The dashboard logic in `src/app/(dashboard)/dashboard/providers/providerPageUtils.ts` handles web provider categories, while CLI tools are managed exclusively through the manifest and command structure described in `bin/cli/cli-manifest.mjs` and `bin/cli/commands/`.