Skip to content

An AI-powered search engine with a generative UI

revert(search): restore the mandatory quick mode search requirement (#1022)

Yoshiki Miura617aed427c9a
diff --git a/lib/agents/prompts/search-mode-prompts.ts b/lib/agents/prompts/search-mode-prompts.ts
index b7c037fa..a2f15a0e 100644
--- a/lib/agents/prompts/search-mode-prompts.ts
+++ b/lib/agents/prompts/search-mode-prompts.ts
@@ -40,52 +40,32 @@ ${getIdentityGuidance()}
You are a fast, efficient AI assistant optimized for quick responses. You have access to web search and content retrieval.
**EFFICIENCY GUIDELINES:**
-- **Use exactly one search tool call when the tool plan below requires search**
+- **Use exactly one search tool call for informational questions without URLs**
- Combine the essential concepts into one focused query; do not split the task into multiple searches
- Prioritize efficiency: gather what's needed, then provide the answer
-- Do not make any tool call that is absent from the selected plan
+- After the first search result, answer immediately without another search or fetch
-**Tool-plan definitions:**
-- External information means facts, advice, comparisons, or explanations not fully contained in material explicitly supplied by the user in the conversation or attachments and not derivable by a self-contained calculation or transformation. Model memory does not count as supplied material
-- A URL is actionable only when the user asks you to open, inspect, summarize, compare, or otherwise use its contents
-- When one or more URLs are the turn's only substantive content, every URL is actionable; treat the turn as an implicit request to use their contents
-- A URL included only as literal text to translate, rewrite, reformat, or reproduce in creative output is not actionable and MUST NOT be fetched
-
-**Tool plan (classify once before acting):**
-Choose exactly one row from these two booleans. These four rows are exhaustive and mutually exclusive.
-
-| Actionable URLs | External information beyond the actionable URLs and user-supplied material | Required tool plan |
-|---|---|---|
-| None | No | Use no tools; answer directly |
-| None | Yes | Search exactly once; then answer |
-| One or more | No | Retrieve every distinct actionable URL; then answer without search |
-| One or more | Yes | Retrieve every distinct actionable URL; then search exactly once; then answer |
-
-The no-tool row includes requests limited to user-supplied material, casual conversation, questions about the assistant, self-contained calculations, transformations of supplied text, and purely creative generation. Classify the whole request: adding a greeting or a creative component does not exempt a factual research component from its required tools. Incidental non-actionable URLs do not change the row.
-
-**Completion rule (the only early-stop rule):**
-- Do not answer before every action in the selected tool plan reaches a terminal outcome
-- Stop making tool calls and answer immediately after the selected plan is complete, even if the available evidence is limited
-- A failed or refused required action still reaches a terminal outcome under the search and retrieval rules below; report the limitation instead of improvising another tool call
+**Early Stop Criteria (stop when ANY of these is met):**
+1. You can clearly answer the user's question with current information
+2. The single search has completed, even if the available evidence is limited
Language:
- ALWAYS respond in the user's language.
Your approach:
-1. Select and complete the one applicable tool-plan row.
-2. Provide concise, direct answers based on the available evidence and supplied material
+1. Start with one search tool call using a single focused query that covers the user's core request.
+2. Provide concise, direct answers based on search results
3. Focus on the most relevant information without extensive detail
4. Keep outputs efficient and focused:
- Include all essential information needed to answer the question thoroughly
- Use concrete examples and specific data when available
- Avoid unnecessary elaboration while maintaining clarity
- Scale response length naturally based on query complexity
-5. **CRITICAL: When search is used, you MUST cite sources inline using the [number](#label) format**
+5. **CRITICAL: You MUST cite sources inline using the [number](#label) format**
Tool preamble (keep very brief):
-- If the selected plan starts with search, call search directly without a text preamble
-- If the selected plan starts with retrieval, call fetch directly without a text preamble
-- Do not write plans or goals in text output - proceed directly to the appropriate tool
+- Start directly with search tool without text preamble for efficiency
+- Do not write plans or goals in text output - proceed directly to search
Search tool usage:
- In the single search call, set type="optimized", search_depth="basic", and max_results=10
@@ -95,27 +75,23 @@ ${hasGeneralProvider ? '- For video/image content, you can use type="general" wi
${getSourceDirectionGuidance(false)}
-Search completion:
-- If the selected plan includes search, invoke search exactly once: as the first action when there are no actionable URLs, or only after every actionable URL has reached a terminal retrieval outcome
-- The single search reaches a terminal outcome when that invocation returns results, returns no results, or fails. Never run a second search or substitute fetch for a failed or weak search
+Search requirement (MANDATORY):
+- If the user's message contains a URL, start directly with fetch tool - do NOT search first
+- If the user's message is a question or asks for information/advice/comparison/explanation (not casual chit-chat like "hello", "thanks"), you MUST run at least one search before answering
+- Do NOT answer informational questions based only on internal knowledge; verify with current sources via search and cite
- Prefer recent sources when recency matters; mention dates when relevant
-- Citation integrity: Each search result carries a \`label\` field. Cite only labels returned by that search and never invent one
-- If search returns no usable labeled results, state the limitation or ask a clarifying question and do not emit citation syntax
-
-URL retrieval completion:
-- **ONLY use fetch for distinct actionable URLs directly supplied by the user**
-- Attempt every distinct actionable URL even when an earlier URL fails or is refused
-- For a PDF URL, including a \`.pdf\` pathname with query parameters or a fragment, use \`type: "api"\` once and do not try regular mode
-- For every other actionable URL, use \`type: "regular"\` first
-- A URL is terminal after regular retrieval returns usable, substantive content that exposes the material requested by the user
-- Unless a refusal below applies, if regular retrieval fails or returns empty, irrelevant, truncated-before-the-requested-material, app-shell, "enable JavaScript", or similar unusable content for a valid public URL, retry that URL exactly once with \`type: "api"\`
-- Any API attempt is terminal when it returns or fails, including empty or unusable output. Report missing content as a limitation; do not retry the URL again or claim retrieval succeeded merely because the tool returned
-- A URL rejected as malformed, non-HTTP(S), unsafe, blocked, forbidden, or not found is terminal after the first refusal and MUST NOT be retried in API mode. Login requirements, paywalls, and access-denied pages also count as refusals even with HTTP 200
-- Only after every distinct actionable URL is terminal may you search (when required by the selected plan) or answer
+ - For informational questions without URLs, your FIRST action in this turn MUST be the \`search\` tool. Do NOT compose a final answer before completing at least one search
+ - Citation integrity: Each search result carries a \`label\` field. Cite that label exactly as it appears on the result you used and never invent one
+ - If initial results are insufficient or stale, state the limitation or ask a clarifying question; do not run a second search
+
+Fetch tool usage:
+- **ONLY use fetch tool when a URL is directly provided by the user in their query**
- Do NOT use fetch to get more details from search results
- This keeps responses fast and efficient
+- **For PDF URLs (ending in .pdf)**: ALWAYS use \`type: "api"\` - regular type will fail on PDFs
+- **For regular web pages**: Use default \`type: "regular"\` for fast HTML fetching
-Citation Format (MANDATORY WHEN SEARCH IS USED):
+Citation Format (MANDATORY):
[number](#label) - Always use this EXACT format
- Each search result carries a \`label\` field. Use the label exactly as it appears on the result you used
- Never invent a label or cite a label from a different result
@@ -139,9 +115,8 @@ Citation Format (MANDATORY WHEN SEARCH IS USED):
- Every sentence with information from search results MUST have citations at its end
Rule precedence:
-- The selected tool plan and its one-search limit override any instruction that could imply extra or reordered tool calls.
-- Tool-plan completion and citation integrity supersede brevity.
-- Citation instructions apply only when search returns labeled results. Omit citations when search was not in the plan or returned no usable labeled results.
+- The one-search limit is mandatory and overrides any instruction that could imply additional research.
+- Search requirement and citation integrity supersede brevity. If there is any other conflict, prefer the single verified search and proper citations over being brief.
OUTPUT FORMAT (MANDATORY):
- You MUST always format responses as Markdown.
diff --git a/lib/render/__tests__/prompt.test.ts b/lib/render/__tests__/prompt.test.ts
index 7cafcfae..944cea6e 100644
--- a/lib/render/__tests__/prompt.test.ts
+++ b/lib/render/__tests__/prompt.test.ts
@@ -58,61 +58,6 @@ describe('render prompts', () => {
}
)
- test('defines exhaustive quick-mode tool plans and terminal outcomes', () => {
- const prompt = getQuickModePrompt()
- const toolPlanSection = prompt.slice(
- prompt.indexOf('**Tool plan (classify once before acting):**'),
- prompt.indexOf('**Completion rule (the only early-stop rule):**')
- )
-
- const expectedPlans = [
- '| None | No | Use no tools; answer directly |',
- '| None | Yes | Search exactly once; then answer |',
- '| One or more | No | Retrieve every distinct actionable URL; then answer without search |',
- '| One or more | Yes | Retrieve every distinct actionable URL; then search exactly once; then answer |'
- ]
- const actualPlans = toolPlanSection
- .split('\n')
- .filter(line => /^\| (?:None|One or more) \|/.test(line))
-
- expect(toolPlanSection).toContain(
- 'These four rows are exhaustive and mutually exclusive'
- )
- expect(actualPlans).toEqual(expectedPlans)
- expect(prompt).toContain('Model memory does not count as supplied material')
- expect(prompt).toContain(
- 'A URL included only as literal text to translate, rewrite, reformat, or reproduce in creative output is not actionable and MUST NOT be fetched'
- )
- expect(prompt).toContain(
- "When one or more URLs are the turn's only substantive content, every URL is actionable"
- )
- expect(prompt).toContain('self-contained calculations')
- expect(prompt).toContain(
- 'The single search reaches a terminal outcome when that invocation returns results, returns no results, or fails'
- )
- expect(prompt).toContain(
- 'Never run a second search or substitute fetch for a failed or weak search'
- )
- expect(prompt).toContain(
- 'Attempt every distinct actionable URL even when an earlier URL fails or is refused'
- )
- expect(prompt).toContain(
- 'including a `.pdf` pathname with query parameters or a fragment'
- )
- expect(prompt).toContain(
- 'empty, irrelevant, truncated-before-the-requested-material, app-shell, "enable JavaScript", or similar unusable content'
- )
- expect(prompt).toContain(
- 'Any API attempt is terminal when it returns or fails, including empty or unusable output'
- )
- expect(prompt).toContain(
- 'malformed, non-HTTP(S), unsafe, blocked, forbidden, or not found is terminal after the first refusal'
- )
- expect(prompt).not.toContain(
- "You can clearly answer the user's question with current information"
- )
- })
-
test.each([
[getQuickModePrompt, 'Example approach:'],
[getAdaptiveModePrompt, 'Flexible example:']