auto
Smart router - Single entry point with natural language intent detection
[Legacy] Redirects to /octo:auto — the smart router
> /plugin marketplace add nyldn/claude-octopusHow it fires
How this command gets triggered: by you, by Claude, or both.
/octoContext preview
What this command does when you run it.
[Legacy] Redirects to /octo:auto — the smart router
command: octo disable-model-invocation: true description: "[Legacy] Redirects to /octo:auto — the smart router" version: 3.0.0 category: workflow tags: [router, legacy, redirect] created: 2025-02-03 updated: 2026-03-18
This v10 compatibility command delegates to `/octo:auto`. It is scheduled for removal in v11.
When the user invokes `/octo:octo <query>`, you MUST:
1. Inform the user: "Note: `/octo:octo` has been renamed to `/octo:auto`. Routing your request now." 2. Immediately read `${HOME}/.claude-octopus/plugin/commands/auto.md` and execute it with the full user query. Do not use the Skill tool; Octopus commands are explicit-only and hidden from model invocation. 3. If the routed workflow dispatches multiple providers, surface `${HOME}/.claude-octopus/plugin/scripts/orchestrate.sh agent-summary` before final synthesis when available.
Do NOT duplicate the routing logic here — delegate entirely to `/octo:auto`.
Every AI model has blind spots. Claude Octopus supports twelve external provider integrations — Codex, Antigravity CLI, Copilot, Qwen, Ollama, Perplexity, OpenRouter, OrcaRouter, OpenCode, Cursor CLI, Grok, and Kimi Code — alongside the built-in Claude Code
Repo: nyldn/claude-octopus
Smart router - Single entry point with natural language intent detection
Start a creative thought partner brainstorming session
Switch Octopus model routing to the configured budget tier
[advanced] Activate destructive command warnings for the session
[advanced] Compatibility view of the deterministic Octopus usage report
Multi-LLM council for advice, decision support, implementation plans, and gated implementation