dograh-hq

Audit Dograh `AGENTS.md` files for drift against the live repo and for bad scope boundaries between parent and child docs. Use when the user asks to review existing AGENTS files, identify stale guidance, decide whether a subtree needs its own `AGENTS.md`, or update the `AGENTS.md` hierarchy under the repo root, `api/`, or `ui/`.

Review a Dograh pull request, branch diff, or pasted patch for repo-specific security and correctness risks that are not obvious from generic FastAPI, Next.js, or Python conventions. Use when the user asks to review a PR, audit a diff, check whether changes are safe to merge, review their own changes, or asks what to look for in a Dograh PR. Focus on tenant isolation, route auth, webhook signing and org derivation, DB layering, worker-sync, migrations, generated SDK usage, and test hazards.

Recurring failure points in this Reddit/LinkedIn discovery repo. Read before writing or reviewing code in backend/* or frontend/* — these are mistakes the codebase has actually been bitten by.

Build voice AI agents, trigger outbound calls, handle inbound calls, run bulk campaigns, and process call results via webhooks using the Dograh REST API

Set up, run, develop, and troubleshoot the Dograh voice-AI platform on any OS (macOS, Linux, Windows/WSL). Use whenever the user wants to install, deploy, run, or contribute to Dograh — or when a Dograh stack is broken: the UI won't load, the API health check (/api/v1/health) is failing, containers are unhealthy/restarting, ports conflict, Docker is missing, or a call has no audio (WebRTC/TURN). Covers the deploy paths (local quick, local+TURN, remote HTTPS) and the developer paths (devcontainer, host-managed). It orients first — detects your OS and what's installed, asks deploy-vs-develop — then drives Dograh's own scripts and docs instead of hard-coding steps. Trigger on "set up dograh", "install dograh", "dograh dev setup", "dograh won't start", or "dograh health check failing".