github/node-DeepResearch
1
0
Fork 0
mirror of https://github.com/jina-ai/node-DeepResearch.git synced 2025-12-26 06:28:56 +08:00
Code Issues Packages Projects Releases Wiki Activity

fix: gen obj retry

Browse Source
This commit is contained in:
Han Xiao 2025-03-20 09:38:46 +08:00
parent b1d038faa9
commit d73fc84e40
2 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
jina-ai/config.json
View File

@ -39,7 +39,7 @@
"maxTokens": 8000 "maxTokens": 8000
}, },
"tools": { "tools": {
"coder": { "maxTokens": 2000 , "model": "gemini-2.0-flash-lite" }, "coder": { "maxTokens": 2000, "model": "gemini-2.0-flash-lite" },
"searchGrounding": { }, "searchGrounding": { },
"dedup": { }, "dedup": { },
"evaluator": {"maxTokens": 2000 }, "evaluator": {"maxTokens": 2000 },

4
src/tools/evaluator.ts
View File

@ -12,13 +12,13 @@ function getRejectAllAnswersPrompt(question: string, answer: AnswerAction, allKn
return { return {
system: ` system: `
You are a ruthless and picky answer evaluator trained to REJECT answers. You can't stand any dubious or lazy answers. You are a ruthless and picky answer evaluator trained to REJECT answers. You can't stand any shallow answers.
User shows you a question-answer pair, your job is to find ANY weakness in the presented answer. User shows you a question-answer pair, your job is to find ANY weakness in the presented answer.
Identity EVERY missing detail. Identity EVERY missing detail.
First, argue AGAINST the answer with the strongest possible case. First, argue AGAINST the answer with the strongest possible case.
Then, argue FOR the answer. Then, argue FOR the answer.
Only after considering both perspectives, synthesize a final improvement plan starts with "For get a pass, you must...". Only after considering both perspectives, synthesize a final improvement plan starts with "For get a pass, you must...".
Markdown or JSON formatting issue is not your concern and should never be mentioned in your feedback or the reason for rejection. Markdown or JSON formatting issue is never your concern and should never be mentioned in your feedback or the reason for rejection.
You always endorse answers in most readable natural language format. You always endorse answers in most readable natural language format.
If multiple sections have very similar structure, suggest another presentation format like a table to make the content more readable. If multiple sections have very similar structure, suggest another presentation format like a table to make the content more readable.