refactor: optimize sorting performance with sort_unstable_by_key and update CLI init to support interactive multi-agent configuration

Author: fajarhide

README.md

@@ -111,8 +111,8 @@ Omni is incredibly easy to set up. It natively integrates into your terminal.
 # 1. Install via Homebrew
 brew install fajarhide/tap/omni
 
-# 2. Setup Omni (Hooks + MCP Server)
-omni init --all
+# 2. Setup Omni (Interactive Menu for Claude, VS Code, OpenCode, Codex, Antigravity)
+omni init
 
 # 3. Verify it's working
 omni doctor
@@ -138,7 +138,7 @@ irm omni.weekndlabs.com/install.ps1 | iex
 
 ## How to Use It
 
-Once installed via `omni init --all`, OMNI works invisibly in the background. Whether your AI Agent runs a terminal command via MCP or you manually pipe output (`ls | omni`), OMNI automatically jumps in as a transparent layer. It intelligently filters terminal output, removes the noisy logs, and hands the clean signal back to the AI.
+Once installed via `omni init`, OMNI works invisibly in the background. Whether your AI Agent runs a terminal command via MCP or you manually pipe output (`ls | omni`), OMNI automatically jumps in as a transparent layer. It intelligently filters terminal output, removes the noisy logs, and hands the clean signal back to the AI.
 
 To review how many tokens (and how much money) you've saved today, just type:
 ```bash
@@ -148,6 +148,29 @@ omni stats
 Need to see the filters in action or add your own custom rules?
 You can easily create your own rules using simple TOML files.
 
+### Multi-Agent Support & Integrations
+
+By default, `omni init --claude` automatically hooks into **Claude Code**. However, OMNI works perfectly with any agentic AI through its built-in integrations! Run `omni init` to see the interactive menu.
+
+1. **VS Code & Continue.dev**: Use our MCP context provider (`integrations/continue-dev/`).
+2. **OpenCode & Codex CLI**: Built-in wrappers automatically pipe command output to OMNI.
+3. **Generic Webhook (Antigravity IDE etc)**: Run `omni serve --port=7891` to launch an ultra-lightweight local HTTP server for agents to drop payloads into OMNI.
+
+**Multi-Agent Tuning (`~/.omni/config.toml`)**
+Different agents have different pain points. Keep VS Code chat clean, whilst letting OpenCode read more data. Tune them individually:
+```toml
+[global]
+aggressiveness = "balanced"
+
+[agents.vscode_continue]
+aggressiveness = "aggressive"
+enable_readfile_distillation = true
+
+[agents.opencode]
+aggressiveness = "conservative"
+enable_readfile_distillation = false
+```
+
 ### Documentation Index
 
 **For Users:**

docs/HOW_TO_USE.md

@@ -55,7 +55,7 @@ Nothing to type. Nothing to configure per-session. Just use Claude Code normally
 
 ```mermaid
 flowchart TD
-    Install([Install OMNI]) --> Init["omni init --all"]
+    Install([Install OMNI]) --> Init["omni init (Interactive)"]
     Init --> Doctor["omni doctor"]
     Doctor --> OK{All checks pass?}
     OK -- No --> Fix["omni doctor --fix"]
@@ -116,10 +116,10 @@ cp target/release/omni ~/.local/bin/
 This is the most important step. Without this, OMNI cannot intercept Claude Code's terminal output.
 
 ```bash
-omni init --all
+omni init
 ```
 
-**What `--all` does:**
+**What `omni init` does:**
 - Installs the `PostToolUse` hook — intercepts every command output after it runs
 - Installs the `SessionStart` hook — injects your working context at session start
 - Installs the `PreCompact` hook — preserves context during Claude's memory compaction
@@ -897,11 +897,17 @@ cargo test 2>&1 | omni             # standard distillation
 Setup OMNI hooks in Claude Code.
 
 ```bash
-omni init --all        # Recommended: Full Setup (Hooks + MCP)
-omni init --hook       # Setup Hooks only
-omni init --mcp        # Setup MCP Server only
-omni init --status     # Check installation status
-omni init --uninstall  # Remove all OMNI components
+omni init              # Interactive Menu for any AI Agent
+
+# Or bypass the menu for a specific agent
+omni init --claude     # Full Setup for Claude Code (Hooks + MCP)
+omni init --vscode     # Setup for VS Code Continue.dev
+omni init --opencode   # Setup for OpenCode plugin
+omni init --codex      # Setup for Codex CLI
+omni init --hook       # Setup Claude Hooks only
+omni init --mcp        # Setup Claude MCP Server only
+omni init --status     # Check Claude installation status
+omni init --uninstall  # Remove all OMNI components from Claude
 ```
 
 **What it does:**
@@ -1085,7 +1091,7 @@ Hooks **always** exit 0 — they never crash the host agent.
 
 | Issue | Likely Cause | Fix |
 |---|---|---|
-| OMNI not filtering anything | Hooks not installed | Run `omni init --all` |
+| OMNI not filtering anything | Not installed | Run `omni init` and select your agent |
 | `omni stats` shows no data | First session not complete | Use Claude Code for a bit, then check |
 | Filter not matching a command | `match_command` regex wrong | Test regex at regex101.com, then `omni learn --verify` |
 | Session not persisting | DB not writable | Run `omni doctor`, check `~/.omni/` permissions |
@@ -1108,7 +1114,7 @@ omni doctor --fix  # Self-repair
 
 ### First-Time Setup
 - [ ] Install OMNI (`brew install fajarhide/tap/omni` or script)
-- [ ] Run `omni init --all`
+- [ ] Run `omni init` for your chosen agent
 - [ ] Run `omni doctor` — all checks should be green
 - [ ] If any checks fail, run `omni doctor --fix`
 - [ ] Use Claude Code normally for one session

docs/MIGRATION.md

@@ -25,13 +25,7 @@ OMNI 0.5.0 is a **full rewrite in Rust** — replacing the previous Node.js + Zi
 
 ### ⚠️ Hooks Must Be Reinstalled
 
-The hook format has changed. Run:
-
-```bash
-omni init --hook
-```
-
-This will update `~/.claude/settings.json` with the new hook entries.
+The hook format has changed. Make sure to run `omni init` after upgrading to update the `PostToolUse` and `SessionStart` hooks in your Claude settings.
 If you had custom hooks, they will be backed up to `settings.json.bak`.
 
 ### ⚠️ `omni monitor` → `omni stats`
@@ -63,7 +57,7 @@ The MCP server is now built-in. Update your Claude config:
 }
 ```
 
-Or run `omni init --hook` which handles this automatically.
+Or run `omni init --claude` which handles this automatically.
 
 ## What's Compatible (No Action Needed)
 
@@ -83,7 +77,7 @@ Or run `omni init --hook` which handles this automatically.
 ```bash
 brew update
 brew upgrade omni
-omni init --hook    # Reinstall hooks
+omni init           # Select Claude Code, or run: omni init --claude
 omni doctor         # Verify everything
 ```
 
@@ -102,7 +96,7 @@ omni doctor
 curl -LO https://github.com/fajarhide/omni/releases/download/v0.5.0/omni-v0.5.0-aarch64-apple-darwin.tar.gz
 tar xzf omni-v0.5.0-aarch64-apple-darwin.tar.gz
 mv omni ~/.local/bin/
-omni init --hook
+omni init           # Reinitialize hooks via interactive menu
 omni doctor
 ```
 
@@ -124,7 +118,7 @@ The `~/.omni/` directory and `omni.db` are safe to keep — they're compatible w
 | `omni doctor` | Diagnose installation (hooks, DB, filters) |
 | `omni stats` | Token savings analytics dashboard |
 | `omni learn` | Auto-generate TOML filters from passthrough output |
-| `omni init --hook` | Setup/update Claude Code hooks |
+| `omni init` | Interactive agent setup menu |
 | `omni --mcp` | Built-in MCP server mode |
 
 ## Troubleshooting

integrations/opencode/package-lock.json

@@ -33,7 +33,7 @@ def install
   def caveats
     <<~EOS
       Quick start:
-        omni init --all        # Initialize OMNI setup
+        omni init              # Initialize OMNI setup (interactive)
         omni doctor            # Verify installation
         omni stats             # View token savings