grepai-watch-daemon

Configure and manage the GrepAI watch daemon for real-time code indexing and file monitoring.

Updated May 12, 2026
One-click install
npx skills add https://github.com/eduardtomasek/codex-dev-stack --skill grepai-watch-daemon-eduardtomasek
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: grepai-watch-daemon
Source: https://github.com/eduardtomasek/codex-dev-stack/tree/main/skills/.agents/grepai-watch-daemon
Command: npx skills add https://github.com/eduardtomasek/codex-dev-stack --skill grepai-watch-daemon-eduardtomasek

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Keeping a semantic code index up to date manually is tedious: every file edit, rename, or deletion can leave search results stale. This Skill manages the GrepAI watch daemon so your codebase is continuously scanned, chunked, embedded, and re-indexed in real time without manual re-runs. ## Core Features & Use Cases - Daemon Lifecycle Management: Start the watcher in foreground or background, check its status, and stop it cleanly with simple commands. - Real-Time File Monitoring: Detects file creation, modification, deletion, and renames using OS-native watchers (FSEvents, inotify, ReadDirectoryChangesW) with configurable debounce. - Boot-Time Automation: Provides launchd (macOS) and systemd (Linux) service configurations so indexing starts automatically. - Use Case: You work across multiple projects and want semantic search to always reflect the latest code. Run one background daemon per project (or a shared workspace), and every save automatically updates the embedding index. ## Quick Start Ask the assistant to start the GrepAI watch daemon in the background for the current project and confirm it is running with a status check.

Frequently Asked Questions about grepai-watch-daemon

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

FAQPage Schema
How do I start the GrepAI watch daemon in the background?▼

Run grepai watch --background from your project root. The daemon starts with a printed PID and writes logs to ~/.grepai/daemon.log. Use grepai watch --status to confirm it is running and grepai watch --stop to shut it down.

How do I make grepai watch start automatically on boot?▼

On macOS, create a launchd plist at ~/Library/LaunchAgents/com.grepai.watch.plist and load it with launchctl. On Linux, create a systemd user service at ~/.config/systemd/user/grepai-watch.service and enable it with systemctl --user enable.

Can I run grepai watch for multiple projects at once?▼

Yes. Start a separate background daemon in each project directory, or create a workspace with grepai workspace create, add multiple project paths, and run grepai watch --workspace to monitor them together.

Why is grepai watch not detecting my file changes?▼

Change detection can fail due to a high debounce_ms value or exhausted inotify limits on Linux. Lower debounce_ms in .grepai/config.yaml and raise fs.inotify.max_user_watches to 65536 to restore real-time monitoring.

What does the grepai watch daemon do when a file changes?▼

On save it re-embeds the changed file's chunks, on creation it indexes new chunks, on deletion it removes entries, and on rename it updates the path while keeping existing vectors. It uses OS-native watchers like FSEvents and inotify.