Ships with octo. Installing the plugin gets this command.
⚡ How it fires
How this command gets triggered: by you, by Claude, or both.
Fires itselfClaude auto-loads it when your prompt matches the work.
You can call itInvoke it directly when you want it.
Slash command/auto
👁️ Context preview
What this command does when you run it.
Smart router - Single entry point with natural language intent detection
📊 Stats
Stars3,869
Forks362
LanguageShell
LicenseMIT
📦 Ships with octo
</> Command definition
auto.md
---command: auto
description: Smart router - Single entry point with natural language intent detection
version: 3.0.0
category: workflow
tags: [router, intent-detection, workflow, smart-routing]
created: 2025-02-03
updated: 2026-03-12
---# Smart Router (/octo:auto)
Single entry point for all Claude Octopus workflows. Analyzes your natural language request and routes to the optimal workflow automatically.
```
/octo:auto research OAuth authentication patterns
/octo:auto debug the failing test in auth.ts
/octo:auto should we use Redis or Memcached?
/octo:auto write tests for the payment module
/octo:auto create a complete e-commerce platform
```
All `/octo:*` commands also work directly, bypassing the router.
---## EXECUTION CONTRACT (Mandatory)
When the user invokes `/octo:auto <query>` or says `octo <query>`, you MUST follow these steps in order:
### STEP 1: Input Validation
If the query exceeds 500 characters, use only the first 500 characters for intent analysis. Pass the full original query to the target workflow.
| Build (Clear) | build X, create X, implement X, develop X — where X is a specific target noun | `octo:develop` |
| Build (Vague) | build, create, make — without a clear target noun | `octo:plan` |
| Quick | quick, just do it, simple, fast, straightforward | `octo:quick` |
**Priority resolution:** When keywords from multiple intents match, the highest-priority intent wins. Example: "analyze the security of our API" matches both Research ("analyze") and Security ("security") — Security wins because Priority 1 > Priority 2.
### STEP 4: Determine Confidence
Apply this decision tree (NOT percentage-based scoring):
```
Single intent matched + specific target noun present
→ HIGH confidence
Single intent matched + target is vague or absent
→ MEDIUM confidence
Multiple intents matched + resolved by priority ordering
→ HIGH confidence (route to the higher-priority intent)
Multiple intents matched at same priority level
→ MEDIUM confidence (present top 2 candidates)
No explicit intent + query asks between two named technologies/options (`X or Y`, `X vs Y`, two code-formatted names)
→ MEDIUM confidence debate candidate (`octo:debate`)
No explicit intent + substantial what/how/why/which question (40+ characters)
→ MEDIUM confidence research candidate (`octo:discover`)
No intent keywords matched
→ LOW confidence
```
### STEP 5: Route Based on Confidence
**STEP 5a — HIGH confidence (auto-route):**
Display:
```
Routing to [Workflow Name] (/octo:[command])
```
Then display the visual indicator banner (STEP 6) and invoke:
```
Skill(skill: "octo:[command]", args: "<full user query>")
Then render the provider banner from actual provider checks. Do not hand-write or summarize this banner; run this block and display its output exactly. The output MUST include the Antigravity line even when `agy` is missing.
