Skip to content

Commit 6c1a346

Browse files
committed
fix: clarification on uses
1 parent 33ecef9 commit 6c1a346

File tree

1 file changed

+7
-5
lines changed

1 file changed

+7
-5
lines changed

docs/guides/ollama-guide.mdx

Lines changed: 7 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -86,16 +86,17 @@ schema: v1
8686
models:
8787
- uses: ollama/deepseek-r1-32b
8888
- uses: ollama/qwen2.5-coder-7b
89-
- uses: ollama/mistral
89+
- uses: ollama/gpt-oss-20b
9090
```
9191
9292
<Warning>
93-
**Important**: When using hub blocks like `ollama/deepseek-r1-32b`, you must first pull the exact model locally:
93+
**Important**: Hub blocks only provide configuration - you still need to pull the model locally. The hub block `ollama/deepseek-r1-32b` configures Continue to use `model: deepseek-r1:32b`, but the actual model must be installed:
9494
```bash
95-
# The hub block name must match the pulled model
96-
ollama pull deepseek-r1:32b # For ollama/deepseek-r1-32b hub block
95+
# Check what the hub block expects (view on hub.continue.dev)
96+
# Then pull that exact model tag locally
97+
ollama pull deepseek-r1:32b # Required for ollama/deepseek-r1-32b hub block
9798
```
98-
If the model isn't pulled, you'll get: `Error: 404 model "deepseek-r1:32b" not found, try pulling it first`
99+
If the model isn't installed, Ollama will return: `404 model "deepseek-r1:32b" not found, try pulling it first`
99100
</Warning>
100101

101102
### Method 2: Manual Configuration
@@ -167,6 +168,7 @@ models:
167168
**Known Issue**: Some models like DeepSeek R1 may show "Agent mode is not supported" or "does not support tools" even with capabilities configured. This is a known limitation where the model's actual tool support differs from its advertised capabilities.
168169
</Warning>
169170

171+
170172
#### If Agent Mode Shows "Not Supported"
171173

172174
1. First, add `capabilities: [tool_use]` to your model config

0 commit comments

Comments
 (0)