omo-recommend-models 1.0.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +78 -0
- package/bin/omo-recommend-models +3948 -0
- package/bin/omo-validate-config +449 -0
- package/lib/omo-shared.js +734 -0
- package/lib/recommend/apply.js +43 -0
- package/package.json +30 -0
package/README.md
ADDED
|
@@ -0,0 +1,78 @@
|
|
|
1
|
+
# omo-recommend-models
|
|
2
|
+
|
|
3
|
+
A CLI utility that profiles your GPU and recommends the most optimized local and cloud AI models for OpenCode and OmO. Run this whenever a new model drops to instantly optimize your configuration for performance and price, completely eliminating the need to manually calculate VRAM footprints or benchmark throughput.
|
|
4
|
+
|
|
5
|
+
## Quick Start
|
|
6
|
+
|
|
7
|
+
Run the utility in your project directory to evaluate your hardware and update your model registry:
|
|
8
|
+
|
|
9
|
+
```
|
|
10
|
+
$ npx npx omo-recommend-models --cloud-only --yes
|
|
11
|
+
│
|
|
12
|
+
◇ Checking GPU: skipped by --cloud-only
|
|
13
|
+
│
|
|
14
|
+
◇ Checking Ollama: skipped by --cloud-only
|
|
15
|
+
│
|
|
16
|
+
◇ Discovering local model catalog: skipped by --cloud-only
|
|
17
|
+
│
|
|
18
|
+
◇ Loading cloud provider cache: 5 provider(s)
|
|
19
|
+
✓ Model picture: 5 cloud provider(s), 0 installed local model(s)
|
|
20
|
+
|
|
21
|
+
│
|
|
22
|
+
◇ Verifying paid models availability: done
|
|
23
|
+
|
|
24
|
+
This run would query:
|
|
25
|
+
1. opencode: nemotron-3-ultra-free
|
|
26
|
+
mimo-v2.5-free
|
|
27
|
+
deepseek-v4-flash-free
|
|
28
|
+
big-pickle
|
|
29
|
+
north-mini-code-free
|
|
30
|
+
|
|
31
|
+
│
|
|
32
|
+
◇ Verifying panel models availability: 5 of 5 model(s) available
|
|
33
|
+
|
|
34
|
+
== AI Panel: 21 agents, 5 panel models ==
|
|
35
|
+
Models:
|
|
36
|
+
• opencode/nemotron-3-ultra-free: 19/21 successful responses
|
|
37
|
+
• opencode/mimo-v2.5-free: 21/21 successful responses
|
|
38
|
+
• opencode/deepseek-v4-flash-free: 21/21 successful responses
|
|
39
|
+
• opencode/big-pickle: 21/21 successful responses
|
|
40
|
+
• opencode/north-mini-code-free: 13/21 successful responses
|
|
41
|
+
evaluating -
|
|
42
|
+
• tasks: 105/105
|
|
43
|
+
• agents: 21/21
|
|
44
|
+
|
|
45
|
+
|
|
46
|
+
📊 AI Analysis (via panel(nemotron-3-ultra-free+mimo-v2.5-free+deepseek-v4-flash-free+big-pickle+north-mini-code-free)):
|
|
47
|
+
Per-agent consensus across 5 panel models for 21 agent(s)
|
|
48
|
+
|
|
49
|
+
```
|
|
50
|
+
|
|
51
|
+
[ [complete output](./output.md) ]
|
|
52
|
+
|
|
53
|
+
---
|
|
54
|
+
|
|
55
|
+
## Why Run This?
|
|
56
|
+
|
|
57
|
+
* **Smart Routing**
|
|
58
|
+
|
|
59
|
+
Local models are automatically used in OpenCode *only* when they will outperform your cloud AI providers.
|
|
60
|
+
* **Hardware Profiling**
|
|
61
|
+
|
|
62
|
+
Detects your GPU architecture and VRAM to shortlist the best models that fit locally.
|
|
63
|
+
* **Cross-Provider Evaluation**
|
|
64
|
+
|
|
65
|
+
Stack-ranks local execution (Ollama, vLLM, Llama.cpp) against cloud providers (Anyscale, Together AI, Groq, OpenRouter) based on cost, speed, context window, and hallucination-free outputs.
|
|
66
|
+
|
|
67
|
+
## Problems omo-recommend-models solves
|
|
68
|
+
|
|
69
|
+
* **Bypass Sisyphus UI Overrides**
|
|
70
|
+
|
|
71
|
+
OpenCode's UI actively fights your OmO configuration for the primary orchestrator (Sisyphus), unconditionally overriding your fallback models. This is a known bug which will not be fixed in opencode.
|
|
72
|
+
|
|
73
|
+
**The fix:**
|
|
74
|
+
|
|
75
|
+
omo-recommend-models saves your configuration file at the project level (`.opencode/oh-my-openagent.jsonc`) instead of the global directory (`~/.config/`). Project-level configs force the pipeline to respect your JSON file over the UI. Add `.opencode` directory to your `.gitignore` file to prevent pushing your configuration to the repository.
|
|
76
|
+
* **Remove delays while running opencode**
|
|
77
|
+
|
|
78
|
+
If a provider is out of credits, OmO will waste time hitting a rejection wall on every single task before triggering the fallback model. Manually removing empty-quota keys from your OpenCode config, or stripping those models from `oh-my-openagent.jsonc` is a nuisance. Run omo-recommed-models to automatically get the latest configuration optimized for performance and price, through your preferred AI providers.
|