deep-researchlisted

# deep-research Drives **chatgpt.com** or **grok.com** through the real UI under a logged-in browser and captures the report. Topic-agnostic: the prompt is the only input. Every run lands in a `Deep research` project on the site so it never clutters chat history. Two ways to run it. Both produce the same intake file. | | A. Runner script `run.mjs` | B. Claude in Chrome | |---|---|---| | Needs | Node, system Chrome, one cookie export per site | Claude Code with the extension, logged-in Chrome | | Secrets | cookie file, seeded once, never read by an agent | none | | Unattended | yes, blocks and saves | no, the agent polls the tab | | Task | Read | |---|---| | First-time setup, cookies, `--check` | `recipes/setup-cookies.md` | | ChatGPT specifics: effort ladder, Chat vs Work, project | `recipes/chatgpt.md` | | Grok specifics: Expert vs Heavy, project, what X search sees | `recipes/grok.md` | | Run interactively with no setup | `recipes/claude-in-chrome.md` | | Runner internals: anti-detection, done rule, exit codes, probe | `recipes/runner-internals.md` | | Built-in research recipes: prompt template, output contract, verify step | `recipes/research/*.md` | | Your own recipes: author once, run on demand, tune over versions | below | ## Your own recipes A built-in recipe is a method. Your own recipe is that method with the blanks filled for one recurring question: "run the SPCX recipe". They live in `~/.deep-research/recipes/<name>.md`, outside the repo, so they survive skil