grepai-troubleshooting

Diagnose and resolve GrepAI configuration, indexing, and MCP integration issues.

18|2|Updated Jan 28, 2026
One-click install
npx skills add https://github.com/yoanbernabeu/grepai-skills --skill grepai-troubleshooting
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: grepai-troubleshooting
Source: https://github.com/yoanbernabeu/grepai-skills/tree/main/skills/advanced/grepai-troubleshooting
Command: npx skills add https://github.com/yoanbernabeu/grepai-skills --skill grepai-troubleshooting

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill offers a structured troubleshooting guide to diagnose and fix common GrepAI issues across configurations, indexing, embeddings, and MCP integrations.

Core Features & Use Cases

  • Diagnostic playbook: provides an actionable sequence to identify misconfigurations, stale indices, or connectivity problems with Ollama or MCP.
  • Unified workflow: combines CLI checks, configuration verifications, and quick-recovery steps to restore normal operation.
  • Use Case: You encounter a "Cannot connect to embedding provider" error; apply this skill to verify the embedder config, test the endpoint, and reinitialize indexing if needed.

Quick Start

To begin diagnosing GrepAI, run a few core checks: grepai version, grepai status, and inspect the config at .grepai/config.yaml. If issues are detected, follow the diagnostic steps described in this guide, including verifying Ollama and MCP endpoints, checking indexing with grepai watch, and reinitializing configuration if necessary.

Frequently Asked Questions about grepai-troubleshooting

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I fix the GrepAI "Cannot connect to embedding provider" error?

To resolve the GrepAI embedding provider error, verify the embedder configuration in .grepai/config.yaml, test the endpoint connectivity, and reinitialize indexing if required.

What is the best way to troubleshoot stale indexes in GrepAI?

Troubleshoot stale GrepAI indexes by running the grepai watch command to monitor indexing status and reinitialize the configuration to force a fresh index rebuild.

How do I diagnose MCP server connectivity problems in GrepAI?

Diagnose GrepAI MCP connectivity issues by running grepai status to verify endpoint availability and checking the MCP server configuration defined in your .grepai/config.yaml file.

Why is my local GrepAI setup not working with Ollama?

Your GrepAI setup fails with Ollama due to misconfigurations or endpoint connectivity issues, requiring you to verify the Ollama server status and adjust settings in .grepai/config.yaml.

Do I need command-line knowledge to troubleshoot GrepAI issues?

Yes, troubleshooting GrepAI issues requires familiarity with command-line utilities to run diagnostic commands like grepai version, grepai status, and grepai watch to identify and resolve errors.

What steps should I follow to start diagnosing GrepAI configuration issues?

Start diagnosing GrepAI configurations by running grepai version and grepai status, then inspect .grepai/config.yaml to verify Ollama, MCP, and embedding provider settings.