You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: src/open_deep_research/prompts.py
+14Lines changed: 14 additions & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -222,6 +222,14 @@
222
222
{research_brief}
223
223
</Research Brief>
224
224
225
+
For more context, here is all of the messages so far. Focus on the research brief above, but consider these messages as well for more context.
226
+
<Messages>
227
+
{messages}
228
+
</Messages>
229
+
CRITICAL: Make sure the answer is written in the same language as the human messages!
230
+
For example, if the user's messages are in English, then MAKE SURE you write your response in English. If the user's messages are in Chinese, then MAKE SURE you write your entire response in Chinese.
231
+
This is critical. The user will only understand the answer if it is written in the same language as their input message.
232
+
225
233
Today's date is {date}.
226
234
227
235
Here are the findings from the research that you conducted:
@@ -270,6 +278,12 @@
270
278
- Use ## for section title (Markdown format) for each section of the report
271
279
- Do NOT ever refer to yourself as the writer of the report. This should be a professional report without any self-referential language.
272
280
- Do not say what you are doing in the report. Just write the report without any commentary from yourself.
281
+
- Each section should be as long as necessary to deeply answer the question with the information you have gathered. It is expected that sections will be fairly long and verbose. You are writing a deep research report, and users will expect a thorough answer.
282
+
- Use bullet points to list out information when appropriate, but by default, write in paragraph form.
283
+
284
+
REMEMBER:
285
+
The brief and research may be in English, but you need to translate this information to the right language when writing the final answer.
286
+
Make sure the final answer report is in the SAME language as the human messages in the message history.
273
287
274
288
Format the report in clear markdown with proper structure and include source references where appropriate.
0 commit comments