Research · What changed, and what people are saying, before you decide. · a tool
The open-source project gpt-researcher, by assafelovic
“An autonomous agent that conducts deep research on any data using any LLM providers” — the project's own words, on GitHub
Paste this into the AI that runs on your computer. It does the install, checks it works, and tells you what to type first. If anything fails, paste the error back to it.
Install gpt-researcher (https://github.com/assafelovic/gpt-researcher) on this computer and get it working for me. I am not a developer; explain each step in one line as you go and never skip one. You are Claude Code, running on my machine. 1. Check what this machine already has (git, Python or Node as the project needs, Docker if the README says so). Tell me anything missing and install it, asking me before anything that needs my password. 2. Clone https://github.com/assafelovic/gpt-researcher into ~/tools/gpt-researcher and follow the README's install exactly. 3. Configure it. If it needs an API key or a login, stop and ask me for it; never guess one and never store it anywhere except where the README says. Tool-specific notes: Set two environment variables before anything else — `OPENAI_API_KEY` and `TAVILY_API_KEY` — it will not run without both. Install with `pip install gpt-researcher`, or clone the repo and run `docker compose up --build` (note: no dash — the older `docker-compose` command fails on newer setups). Smoke-test with a short script that creates a `GPTResearcher(query=...)`, calls `conduct_research()`, then `write_report()` — or run the bundled web app and visit `http://localhost:8000`. If you want it to read your own files too, set `DOC_PATH` to that folder before you ask your question. Budget a few minutes per question — it is actually reading multiple pages before it writes, not returning instantly. 4. Run the smallest test the README gives, and show me the output. 5. When it works, tell me what to type first, in one line, for this job: Ask it one real question. If anything fails, show me the exact error and fix it before going on.
Install gpt-researcher (https://github.com/assafelovic/gpt-researcher) on this computer and get it working for me. I am not a developer; explain each step in one line as you go and never skip one. You are Kimi, running on my machine. 1. Check what this machine already has (git, Python or Node as the project needs, Docker if the README says so). Tell me anything missing and install it, asking me before anything that needs my password. 2. Clone https://github.com/assafelovic/gpt-researcher into ~/tools/gpt-researcher and follow the README's install exactly. 3. Configure it. If it needs an API key or a login, stop and ask me for it; never guess one and never store it anywhere except where the README says. Tool-specific notes: Set two environment variables before anything else — `OPENAI_API_KEY` and `TAVILY_API_KEY` — it will not run without both. Install with `pip install gpt-researcher`, or clone the repo and run `docker compose up --build` (note: no dash — the older `docker-compose` command fails on newer setups). Smoke-test with a short script that creates a `GPTResearcher(query=...)`, calls `conduct_research()`, then `write_report()` — or run the bundled web app and visit `http://localhost:8000`. If you want it to read your own files too, set `DOC_PATH` to that folder before you ask your question. Budget a few minutes per question — it is actually reading multiple pages before it writes, not returning instantly. 4. Run the smallest test the README gives, and show me the output. 5. When it works, tell me what to type first, in one line, for this job: Ask it one real question. If anything fails, show me the exact error and fix it before going on.
Install gpt-researcher (https://github.com/assafelovic/gpt-researcher) on this computer and get it working for me. I am not a developer; explain each step in one line as you go and never skip one. You are Gemini CLI, running on my machine. 1. Check what this machine already has (git, Python or Node as the project needs, Docker if the README says so). Tell me anything missing and install it, asking me before anything that needs my password. 2. Clone https://github.com/assafelovic/gpt-researcher into ~/tools/gpt-researcher and follow the README's install exactly. 3. Configure it. If it needs an API key or a login, stop and ask me for it; never guess one and never store it anywhere except where the README says. Tool-specific notes: Set two environment variables before anything else — `OPENAI_API_KEY` and `TAVILY_API_KEY` — it will not run without both. Install with `pip install gpt-researcher`, or clone the repo and run `docker compose up --build` (note: no dash — the older `docker-compose` command fails on newer setups). Smoke-test with a short script that creates a `GPTResearcher(query=...)`, calls `conduct_research()`, then `write_report()` — or run the bundled web app and visit `http://localhost:8000`. If you want it to read your own files too, set `DOC_PATH` to that folder before you ask your question. Budget a few minutes per question — it is actually reading multiple pages before it writes, not returning instantly. 4. Run the smallest test the README gives, and show me the output. 5. When it works, tell me what to type first, in one line, for this job: Ask it one real question. If anything fails, show me the exact error and fix it before going on.
Install gpt-researcher (https://github.com/assafelovic/gpt-researcher) on this computer and get it working for me. I am not a developer; explain each step in one line as you go and never skip one. You are Codex, running on my machine. 1. Check what this machine already has (git, Python or Node as the project needs, Docker if the README says so). Tell me anything missing and install it, asking me before anything that needs my password. 2. Clone https://github.com/assafelovic/gpt-researcher into ~/tools/gpt-researcher and follow the README's install exactly. 3. Configure it. If it needs an API key or a login, stop and ask me for it; never guess one and never store it anywhere except where the README says. Tool-specific notes: Set two environment variables before anything else — `OPENAI_API_KEY` and `TAVILY_API_KEY` — it will not run without both. Install with `pip install gpt-researcher`, or clone the repo and run `docker compose up --build` (note: no dash — the older `docker-compose` command fails on newer setups). Smoke-test with a short script that creates a `GPTResearcher(query=...)`, calls `conduct_research()`, then `write_report()` — or run the bundled web app and visit `http://localhost:8000`. If you want it to read your own files too, set `DOC_PATH` to that folder before you ask your question. Budget a few minutes per question — it is actually reading multiple pages before it writes, not returning instantly. 4. Run the smallest test the README gives, and show me the output. 5. When it works, tell me what to type first, in one line, for this job: Ask it one real question. If anything fails, show me the exact error and fix it before going on.
Give it a specific question you'd actually want answered — not a topic — and check the report cites a source for every claim you'd want to challenge.
Open two or three of the links it cites and confirm they actually say what the report claims, since it aggregates sources rather than verifying every sentence in them.
Set its local-documents folder to a set of your own files and ask a similar question, so you can see it blend your material with the open web rather than only the web.
assafelovic/gpt-researcher on GitHub, under the Apache-2.0 licence. 29,365 stars, checked 9 September 2026. Last change 23 August 2026. We did not write it; we checked it, and wrote this page so you can use it.
Once a week, what changed with your competitors and in your niche. One page, every line sourced.
Give it a web address, or a list of them, and it hands back clean, plain-text versions of those pages — headings and paragraphs stripped of surrounding code — so your AI can read them.
Give it a web address and it hands back the page as clean data — plain-text markdown, or JSON shaped the way you ask for — so your AI can read it without wading through a page's raw code.
Ask it about a person, a company, or a topic and it goes looking across Reddit, X, YouTube, TikTok, Hacker News and a handful of other platforms for what people have actually said in the last 30 days — ranked by real engagement, not by what a search engine's editors chose to surface.
If you're launching or growing a brand across Asia and the West, a call is where we work out whether it's a fit.