
Grepai Ollama Setup
- 726 installs
- 18 repo stars
- Updated February 1, 2026
- yoanbernabeu/grepai-skills
grepai-ollama-setup is an agent skill that installs and configures Ollama as GrepAI's local embedding provider for developers who need private, on-machine semantic code search without cloud APIs.
About
grepai-ollama-setup is a skill from yoanbernabeu/grepai-skills for installing and configuring Ollama as GrepAI's local embedding backend. It walks through first-time Ollama installation, embedding model selection, and connection troubleshooting so code never leaves the machine. The readme positions Ollama as enabling 100% private code search for GrepAI indexing workflows. Developers reach for this skill when setting up GrepAI with local embeddings, choosing models, or fixing Ollama connectivity during private repo search setup.
- Install paths for macOS (Homebrew and DMG), Linux one-liner, and Windows installer
- Documents privacy, zero API cost, offline, and low-latency local embedding generation
- Covers choosing and downloading embedding models required by GrepAI
- Includes troubleshooting guidance for Ollama service and connection issues
- Positions 100% on-machine code search so source never leaves the machine
Grepai Ollama Setup by the numbers
- 726 all-time installs (skills.sh)
- +8 installs in the week ending Jul 28, 2026 (Skillselion tracking)
- Ranked #1,400 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-ollama-setupAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 726 |
|---|---|
| repo stars | ★ 18 |
| Security audit | 1 / 3 scanners passed |
| Last updated | February 1, 2026 |
| Repository | yoanbernabeu/grepai-skills ↗ |
How do you set up local embeddings for GrepAI?
Install Ollama and pull embedding models so GrepAI can index and search your repo locally without sending code to cloud APIs.
Who is it for?
Developers configuring GrepAI who require private local embeddings instead of cloud embedding APIs.
Skip if: Teams already using a cloud embedding provider or developers who do not need local semantic code search.
When should I use this skill?
The user sets up GrepAI with local private embeddings, installs Ollama for the first time, or troubleshoots Ollama connection errors.
What you get
Running Ollama service, downloaded embedding model, and GrepAI configured for on-machine indexing.
- configured ollama service
- pulled embedding model
- connected grepai setup
By the numbers
- Enables 100% private code search with on-machine embeddings
Files
Ollama Setup for GrepAI
This skill covers installing and configuring Ollama as the local embedding provider for GrepAI. Ollama enables 100% private code search where your code never leaves your machine.
When to Use This Skill
- Setting up GrepAI with local, private embeddings
- Installing Ollama for the first time
- Choosing and downloading embedding models
- Troubleshooting Ollama connection issues
Why Ollama?
| Benefit | Description |
|---|---|
| 🔒 Privacy | Code never leaves your machine |
| 💰 Free | No API costs |
| ⚡ Fast | Local processing, no network latency |
| 🔌 Offline | Works without internet |
Installation
macOS (Homebrew)
# Install Ollama
brew install ollama
# Start the Ollama service
ollama servemacOS (Direct Download)
1. Download from ollama.com 2. Open the .dmg and drag to Applications 3. Launch Ollama from Applications
Linux
# One-line installer
curl -fsSL https://ollama.com/install.sh | sh
# Start the service
ollama serveWindows
1. Download installer from ollama.com 2. Run the installer 3. Ollama starts automatically as a service
Downloading Embedding Models
GrepAI requires an embedding model to convert code into vectors.
Recommended Model: nomic-embed-text
# Download the recommended model (768 dimensions)
ollama pull nomic-embed-textSpecifications:
- Dimensions: 768
- Size: ~274 MB
- Performance: Excellent for code search
- Language: English-optimized
Alternative Models
# Multilingual support (better for non-English code/comments)
ollama pull nomic-embed-text-v2-moe
# Larger, more accurate
ollama pull bge-m3
# Maximum quality
ollama pull mxbai-embed-large| Model | Dimensions | Size | Best For |
|---|---|---|---|
nomic-embed-text | 768 | 274 MB | General code search |
nomic-embed-text-v2-moe | 768 | 500 MB | Multilingual codebases |
bge-m3 | 1024 | 1.2 GB | Large codebases |
mxbai-embed-large | 1024 | 670 MB | Maximum accuracy |
Verifying Installation
Check Ollama is Running
# Check if Ollama server is responding
curl http://localhost:11434/api/tags
# Expected output: JSON with available modelsList Downloaded Models
ollama list
# Output:
# NAME ID SIZE MODIFIED
# nomic-embed-text:latest abc123... 274 MB 2 hours agoTest Embedding Generation
# Quick test (should return embedding vector)
curl http://localhost:11434/api/embeddings -d '{
"model": "nomic-embed-text",
"prompt": "function hello() { return world; }"
}'Configuring GrepAI for Ollama
After installing Ollama, configure GrepAI to use it:
# .grepai/config.yaml
embedder:
provider: ollama
model: nomic-embed-text
endpoint: http://localhost:11434This is the default configuration when you run grepai init, so no changes are needed if using nomic-embed-text.
Running Ollama
Foreground (Development)
# Run in current terminal (see logs)
ollama serveBackground (macOS/Linux)
# Using nohup
nohup ollama serve &
# Or as a systemd service (Linux)
sudo systemctl enable ollama
sudo systemctl start ollamaCheck Status
# Check if running
pgrep -f ollama
# Or test the API
curl -s http://localhost:11434/api/tags | head -1Resource Considerations
Memory Usage
Embedding models load into RAM:
nomic-embed-text: ~500 MB RAMbge-m3: ~1.5 GB RAMmxbai-embed-large: ~1 GB RAM
CPU vs GPU
Ollama uses CPU by default. For faster embeddings:
- macOS: Uses Metal (Apple Silicon) automatically
- Linux/Windows: Install CUDA for NVIDIA GPU support
Common Issues
❌ Problem: connection refused to localhost:11434 ✅ Solution: Start Ollama:
ollama serve❌ Problem: Model not found ✅ Solution: Pull the model first:
ollama pull nomic-embed-text❌ Problem: Slow embedding generation ✅ Solution:
- Use a smaller model
- Ensure Ollama is using GPU (check
ollama ps) - Close other memory-intensive applications
❌ Problem: Out of memory ✅ Solution: Use a smaller model or increase system RAM
Best Practices
1. Start Ollama before GrepAI: Ensure ollama serve is running 2. Use recommended model: nomic-embed-text offers best balance 3. Keep Ollama running: Leave it as a background service 4. Update periodically: ollama pull nomic-embed-text for updates
Output Format
After successful setup:
✅ Ollama Setup Complete
Ollama Version: 0.1.x
Endpoint: http://localhost:11434
Model: nomic-embed-text (768 dimensions)
Status: Running
GrepAI is ready to use with local embeddings.
Your code will never leave your machine.Related skills
How it compares
Use grepai-ollama-setup for local Ollama embeddings; use cloud-provider skills when off-machine managed embeddings are acceptable.
FAQ
Why use Ollama with GrepAI?
Ollama with GrepAI enables 100% private code search where code never leaves the machine. grepai-ollama-setup configures Ollama as the local embedding provider so GrepAI can index and search repositories without cloud APIs.
When should grepai-ollama-setup run?
grepai-ollama-setup should run when setting up GrepAI with local embeddings, installing Ollama for the first time, choosing embedding models, or troubleshooting Ollama connectivity during private search setup.
Is Grepai Ollama Setup safe to install?
skills.sh reports 1 of 3 security scanners passed. Review the Security Audits panel on this page before installing in production.