-
Notifications
You must be signed in to change notification settings - Fork 2.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
"detailed Report" doesn't work. #807
Comments
Sup @elchananvol For the detailed report, have a look at prompts.py & chase the relevant function up the stack For the multi_agents feature, try running it via Docker, like so: Add a .env file to the root folder with these values: OPENAI_API_KEY= Then restart docker with: docker compose up --build Visit localhost:3000 - both detailed report & multi agents report are available for you there May the force be with you 🙏 |
I'm not sure what you mean. Are you saying that "detailed_report" isn't developed yet, or has a different flow than the other report types? |
@ElishaKay I am getting the exact same result regardless of whether I give I am using it in the following way:
But when I use the frontend version, I get different results of course - a 3 page document with the summary report (which is "research report" from the API) option, and a 11 page document with the detailed report option. Is this not the correct way to use the |
Sup @elchananvol & @PrashantSaikia, I'm working on giving the community access to an AI Dev Team who will hopefully be more competent than myself to answer these types of questions. If you'd like their answer, please feel free to clone the branch and set your Github access token as an env variable. The AI dev team will be able to take as input:
And provide a meaningful response base on the branch files. On 1 foot: The backend research flows were refactored several times as we were learning how to best tame the awesome power of the LLM. For viewing the logic triggered by the frontend, look at the backend/websocket_manager.py file & follow the functions down the chain. In general, the multi_agents flow proved to be a favorite therefore it got higher priority - for long reports, you can go with that. For why the pip package is triggering the same flow for different inputs, the AI dev team will investigate when they're put to work 🤠 |
@elchananvol detailed report should now work. You can check it out via CLI here: https://docs.gptr.dev/docs/gpt-researcher/getting-started/cli or here: https://docs.gptr.dev/docs/examples/detailed_report |
@assafelovic, I'm currently using
|
I'm running the following:
Btw, the same issue occurs with 'multi_agents,' even though I see the beginning of its implementation in websocket_manager.py
The text was updated successfully, but these errors were encountered: