
Grepai Embeddings Ollama
- 629 installs
- 18 repo stars
- Updated February 1, 2026
- yoanbernabeu/grepai-skills
grepai-embeddings-ollama is an agent skill that configures Ollama as the local embedding provider for GrepAI so developers can run private semantic code search without external API calls.
About
grepai-embeddings-ollama is an agent skill from yoanbernabeu/grepai-skills that configures Ollama as GrepAI's embedding backend for fully local, private code search. The workflow covers choosing an Ollama embedding model, wiring GrepAI to the local endpoint, and tuning performance while keeping source code on-machine with zero API cost. Developers reach for grepai-embeddings-ollama when corporate policy blocks cloud embeddings, air-gapped environments need offline search, or recurring embedding API fees are undesirable. The skill also documents troubleshooting for Ollama connection failures and latency tuning without network round-trips.
- Configures Ollama as the embedding provider for GrepAI
- Enables 100% private, local code embeddings with zero data leaving your machine
- Supports custom endpoints and explicit embedding dimensions
- Provides offline operation with no API costs or rate limits
- Includes troubleshooting guidance for connection and performance issues
Grepai Embeddings Ollama by the numbers
- 629 all-time installs (skills.sh)
- +4 installs in the week ending Jul 28, 2026 (Skillselion tracking)
- Ranked #1,546 of 16,546 AI & Agent Building skills by installs in the Skillselion catalog
- Security screen: HIGH risk (skills.sh audit)
- Data as of Jul 28, 2026 (Skillselion catalog sync)
npx skills add https://github.com/yoanbernabeu/grepai-skills --skill grepai-embeddings-ollamaAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 629 |
|---|---|
| repo stars | ★ 18 |
| Security audit | 1 / 3 scanners passed |
| Last updated | February 1, 2026 |
| Repository | yoanbernabeu/grepai-skills ↗ |
How do you run GrepAI embeddings locally with Ollama?
Configure Ollama as the local embedding provider for GrepAI and enable fully private code search without sending data to external APIs.
Who is it for?
Developers setting up GrepAI who require on-machine embeddings for privacy, offline use, or zero per-token API spend.
Skip if: Teams already standardized on a managed cloud embedding API who do not run Ollama locally.
When should I use this skill?
A user asks to configure GrepAI with Ollama, enable local embeddings, or troubleshoot private semantic code search setup.
What you get
GrepAI configured with an Ollama embedding model, verified local index generation, and documented connection settings for offline code search.
- GrepAI Ollama provider configuration
- Selected embedding model recommendation
- Connection troubleshooting checklist
Files
GrepAI Embeddings with Ollama
This skill covers using Ollama as the embedding provider for GrepAI, enabling 100% private, local code search.
When to Use This Skill
- Setting up private, local embeddings
- Choosing the right Ollama model
- Optimizing Ollama performance
- Troubleshooting Ollama connection issues
Why Ollama?
| Advantage | Description |
|---|---|
| 🔒 Privacy | Code never leaves your machine |
| 💰 Free | No API costs or usage limits |
| ⚡ Speed | No network latency |
| 🔌 Offline | Works without internet |
| 🔧 Control | Choose your model |
Prerequisites
1. Ollama installed and running 2. An embedding model downloaded
# Install Ollama
brew install ollama # macOS
# or
curl -fsSL https://ollama.com/install.sh | sh # Linux
# Start Ollama
ollama serve
# Download model
ollama pull nomic-embed-textConfiguration
Basic Configuration
# .grepai/config.yaml
embedder:
provider: ollama
model: nomic-embed-text
endpoint: http://localhost:11434With Custom Endpoint
embedder:
provider: ollama
model: nomic-embed-text
endpoint: http://192.168.1.100:11434 # Remote Ollama serverWith Explicit Dimensions
embedder:
provider: ollama
model: nomic-embed-text
endpoint: http://localhost:11434
dimensions: 768 # Usually auto-detectedAvailable Models
Recommended: nomic-embed-text
ollama pull nomic-embed-text| Property | Value |
|---|---|
| Dimensions | 768 |
| Size | ~274 MB |
| Speed | Fast |
| Quality | Excellent for code |
| Language | English-optimized |
Configuration:
embedder:
provider: ollama
model: nomic-embed-textMultilingual: nomic-embed-text-v2-moe
ollama pull nomic-embed-text-v2-moe| Property | Value |
|---|---|
| Dimensions | 768 |
| Size | ~500 MB |
| Speed | Medium |
| Quality | Excellent |
| Language | Multilingual |
Best for codebases with non-English comments/documentation.
Configuration:
embedder:
provider: ollama
model: nomic-embed-text-v2-moeHigh Quality: bge-m3
ollama pull bge-m3| Property | Value |
|---|---|
| Dimensions | 1024 |
| Size | ~1.2 GB |
| Speed | Slower |
| Quality | Very high |
| Language | Multilingual |
Best for large, complex codebases where accuracy is critical.
Configuration:
embedder:
provider: ollama
model: bge-m3
dimensions: 1024Maximum Quality: mxbai-embed-large
ollama pull mxbai-embed-large| Property | Value |
|---|---|
| Dimensions | 1024 |
| Size | ~670 MB |
| Speed | Medium |
| Quality | Highest |
| Language | English |
Configuration:
embedder:
provider: ollama
model: mxbai-embed-large
dimensions: 1024Model Comparison
| Model | Dims | Size | Speed | Quality | Use Case |
|---|---|---|---|---|---|
nomic-embed-text | 768 | 274MB | ⚡⚡⚡ | ⭐⭐⭐ | General use |
nomic-embed-text-v2-moe | 768 | 500MB | ⚡⚡ | ⭐⭐⭐⭐ | Multilingual |
bge-m3 | 1024 | 1.2GB | ⚡ | ⭐⭐⭐⭐⭐ | Large codebases |
mxbai-embed-large | 1024 | 670MB | ⚡⚡ | ⭐⭐⭐⭐⭐ | Maximum accuracy |
Performance Optimization
Memory Management
Models load into RAM. Ensure sufficient memory:
| Model | RAM Required |
|---|---|
nomic-embed-text | ~500 MB |
nomic-embed-text-v2-moe | ~800 MB |
bge-m3 | ~1.5 GB |
mxbai-embed-large | ~1 GB |
GPU Acceleration
Ollama automatically uses:
- macOS: Metal (Apple Silicon)
- Linux/Windows: CUDA (NVIDIA GPUs)
Check GPU usage:
ollama psKeeping Model Loaded
By default, Ollama unloads models after 5 minutes of inactivity. Keep loaded:
# Keep model loaded indefinitely
curl http://localhost:11434/api/generate -d '{
"model": "nomic-embed-text",
"keep_alive": -1
}'Verifying Connection
Check Ollama is Running
curl http://localhost:11434/api/tagsList Available Models
ollama listTest Embedding
curl http://localhost:11434/api/embeddings -d '{
"model": "nomic-embed-text",
"prompt": "function authenticate(user, password)"
}'Running Ollama as a Service
macOS (launchd)
Ollama app runs automatically on login.
Linux (systemd)
# Enable service
sudo systemctl enable ollama
# Start service
sudo systemctl start ollama
# Check status
sudo systemctl status ollamaManual Background
nohup ollama serve > /dev/null 2>&1 &Remote Ollama Server
Run Ollama on a powerful server and connect remotely:
On the Server
# Allow remote connections
OLLAMA_HOST=0.0.0.0 ollama serveOn the Client
# .grepai/config.yaml
embedder:
provider: ollama
model: nomic-embed-text
endpoint: http://server-ip:11434Common Issues
❌ Problem: Connection refused ✅ Solution:
# Start Ollama
ollama serve❌ Problem: Model not found ✅ Solution:
# Pull the model
ollama pull nomic-embed-text❌ Problem: Slow embedding generation ✅ Solutions:
- Use a smaller model (
nomic-embed-text) - Ensure GPU is being used (
ollama ps) - Close memory-intensive applications
- Consider a remote server with better hardware
❌ Problem: Out of memory ✅ Solutions:
- Use a smaller model
- Close other applications
- Upgrade RAM
- Use remote Ollama server
❌ Problem: Embeddings differ after model update ✅ Solution: Re-index after model updates:
rm .grepai/index.gob
grepai watchBest Practices
1. Start with `nomic-embed-text`: Best balance of speed/quality 2. Keep Ollama running: Background service recommended 3. Match dimensions: Don't mix models with different dimensions 4. Re-index on model change: Delete index and re-run watch 5. Monitor memory: Embedding models use significant RAM
Output Format
Successful Ollama configuration:
✅ Ollama Embedding Provider Configured
Provider: Ollama
Model: nomic-embed-text
Endpoint: http://localhost:11434
Dimensions: 768 (auto-detected)
Status: Connected
Model Info:
- Size: 274 MB
- Loaded: Yes
- GPU: Apple MetalRelated skills
How it compares
Use grepai-embeddings-ollama when GrepAI must index code without leaving the machine; cloud embedding skills apply when local Ollama ops are not feasible.
FAQ
Why use grepai-embeddings-ollama instead of a cloud embedding API?
grepai-embeddings-ollama keeps code on the local machine with no API fees or network latency. The skill documents Ollama model selection and GrepAI wiring for 100% private embedding generation.
What problems does grepai-embeddings-ollama help troubleshoot?
grepai-embeddings-ollama covers Ollama connection failures, model choice, and performance tuning when GrepAI indexes a repository locally. Invoke it during initial setup or when embeddings fail to generate.
When should developers choose local Ollama embeddings for GrepAI?
grepai-embeddings-ollama fits air-gapped machines, strict data-residency policies, or teams avoiding recurring embedding API spend. Cloud APIs remain simpler when local GPU or Ollama ops are unavailable.
Is Grepai Embeddings Ollama safe to install?
skills.sh reports 1 of 3 security scanners passed. Review the Security Audits panel on this page before installing in production.