New file-picker: Use grok 4 fast instead of haiku. Delete file-picker max.

Author: jahooma

.agents/base2/base2-with-planner-pro.ts

@@ -34,7 +34,7 @@ export const createBase2: (
     includeMessageHistory: true,
     toolNames: ['spawn_agents', 'read_files', 'str_replace', 'write_file'],
     spawnableAgents: buildArray(
-      'file-picker-max',
+      'file-picker',
       'code-searcher',
       'directory-lister',
       'glob-matcher',
@@ -124,17 +124,17 @@ ${PLACEHOLDER.GIT_CHANGES_PROMPT}
 
 The user asks you to implement a new feature. You respond in multiple steps:
 
-1. Spawn a couple different file-picker-max's with different prompts to find relevant files; spawn a code-searcher and glob-matcher to find more relevant files and answer questions about the codebase; spawn 1 docs researcher to find relevant docs.
+1. Spawn a couple different file-picker's with different prompts to find relevant files; spawn a code-searcher and glob-matcher to find more relevant files and answer questions about the codebase; spawn 1 docs researcher to find relevant docs.
 1a. Read all the relevant files using the read_files tool.
-2. Spawn one more file-picker-max and one more code-searcher with different prompts to find relevant files.
+2. Spawn one more file-picker and one more code-searcher with different prompts to find relevant files.
 2a. Read all the relevant files using the read_files tool.
 3. Important: Spawn a planner-pro agent to generate a plan for the changes.
 4. Use the str_replace or write_file tool to make the changes.
 5. Spawn a code-reviewer to review the changes. Consider making changes suggested by the code-reviewer.
 6. Spawn a validator to run validation commands (tests, typechecks, etc.) to ensure the changes are correct.
 7. Inform the user that you have completed the task in one sentence without a final summary.`,
 
-    stepPrompt: `Don't forget to spawn agents that could help, especially: the file-picker-max and find-all-referencer to get codebase context, the planner-pro agent to create a plan, the code reviewer to review changes, and the validator to run validation checks.`,
+    stepPrompt: `Don't forget to spawn agents that could help, especially: the file-picker and find-all-referencer to get codebase context, the planner-pro agent to create a plan, the code reviewer to review changes, and the validator to run validation checks.`,
 
     handleSteps: function* ({ prompt, params }) {
       let steps = 0

.agents/base2/base2.ts

@@ -62,7 +62,7 @@ export function createBase2(
       isGpt5 && 'task_completed',
     ),
     spawnableAgents: buildArray(
-      'file-picker-max',
+      'file-picker',
       'code-searcher',
       'directory-lister',
       'glob-matcher',
@@ -151,6 +151,7 @@ ${PLACEHOLDER.GIT_CHANGES_PROMPT}
       ? buildPlanOnlyInstructionsPrompt({})
       : buildImplementationInstructionsPrompt({
           isGpt5,
+          isFast,
           isDefault,
           isMax,
           hasNoValidation,
@@ -180,16 +181,17 @@ ${PLACEHOLDER.GIT_CHANGES_PROMPT}
   }
 }
 
-const definition = { ...createBase2('default'), id: 'base2' }
-export default definition
+const EXPLORE_PROMPT = `- Spawn file pickers, code-searcher, directory-lister, glob-matcher, commanders, and web/docs researchers to gather context as needed. The file-picker agent in particular is very useful to use to find relevant files -- try spawning mulitple in parallel to explore different parts of the codebase. Read all the relevant files using the read_files tool. Read as many files as possible so that you have a comprehensive context on the user's request.`
 
 function buildImplementationInstructionsPrompt({
   isGpt5,
+  isFast,
   isDefault,
   isMax,
   hasNoValidation,
 }: {
   isGpt5: boolean
+  isFast: boolean
   isDefault: boolean
   isMax: boolean
   hasNoValidation: boolean
@@ -201,10 +203,11 @@ function buildImplementationInstructionsPrompt({
 The user asks you to implement a new feature. You respond in multiple steps:
 
 ${buildArray(
-  `- Spawn file pickers, code-searcher, directory-lister, glob-matcher, commanders, and web/docs researchers to gather context as needed. The file-picker-max agent in particular is very useful to use to find relevant files. Read all the relevant files using the read_files tool. Read as many files as possible so that you have a comprehensive context on the user's request.`,
+  EXPLORE_PROMPT,
   `- Important: Read as many files as could possibly be relevant to the task to improve your understanding of the user's request and produce the best possible code changes. This is frequently 12-20 files, depending on the task.`,
   `- For multi-step tasks, use the write_todos tool to write out your step-by-step implementation plan. Include ALL of the applicable tasks in the list.${hasNoValidation ? '' : ' You should include at least one step to validate/test your changes: be specific about whether to typecheck, run tests, run lints, etc.'} Skip write_todos for trivial tasks like single-line edits or simple questions.`,
-  `- You must spawn the ${isGpt5 ? 'best-of-n-editor-gpt-5' : 'best-of-n-editor'} agent to implement non-trivial code changes, since it will generate the best code changes from multiple implementation proposals. This is the best way to make high quality code changes -- strongly prefer using this agent over the str_replace or write_file tools, unless the change is very small and trivial.`,
+  !isFast &&
+    `- You must spawn the ${isGpt5 ? 'best-of-n-editor-gpt-5' : 'best-of-n-editor'} agent to implement non-trivial code changes, since it will generate the best code changes from multiple implementation proposals. This is the best way to make high quality code changes -- strongly prefer using this agent over the str_replace or write_file tools, unless the change is very small and trivial.`,
   !hasNoValidation &&
     `- Test your changes${isMax ? '' : ' briefly'} by running appropriate validation commands for the project (e.g. typechecks, tests, lints, etc.).${isMax ? ' Start by type checking the specific area of the project that you are editing and then test the entire project if necessary.' : ' If you can, only typecheck/test the area of the project that you are editing, rather than the entire project.'} You may have to explore the project to find the appropriate commands. Don't skip this step!`,
   `- Inform the user that you have completed the task in one sentence or a few short bullet points. Don't create any markdown summary files or example documentation files, unless asked by the user. If you already finished the user request and said you're done, then don't say anything else.`,
@@ -220,7 +223,7 @@ function buildPlanOnlyInstructionsPrompt({}: {}) {
 The user asks you to implement a new feature. You respond in multiple steps:
 
 ${buildArray(
-  `- Spawn file pickers, code-searcher, directory-lister, glob-matcher, commanders, and researchers to gather context as needed. The file-picker-max agent in particular is very useful to use to find relevant files. Read all the relevant files using the read_files tool. Read as many files as possible so that you have a comprehensive context on the user's request.`,
+  EXPLORE_PROMPT,
   `- After exploring the codebase, translate the user request into a clear and concise spec. If the user is just asking a question, you can answer it instead of writing a spec.
 
 ## Creating a spec
@@ -287,3 +290,6 @@ function buildPlanOnlyStepPrompt({}: {}) {
     `Your are in plan mode. Do not make any file changes. Do not call write_file or str_replace. Do not spawn the best-of-n-editor agent to implement. Do not use the write_todos tool.`,
   ).join('\n')
 }
+
+const definition = { ...createBase2('default'), id: 'base2' }
+export default definition

.agents/base2/task-researcher/base2-gpt-5-with-task-researcher.ts

@@ -38,7 +38,7 @@ export const createBase2WithTaskResearcher: () => Omit<
     toolNames: ['spawn_agents', 'read_files', 'str_replace', 'write_file'],
     spawnableAgents: buildArray(
       'task-researcher',
-      'file-picker-max',
+      'file-picker',
       'code-searcher',
       'directory-lister',
       'glob-matcher',

.agents/base2/task-researcher/base2-with-task-researcher-planner-pro.ts

@@ -38,7 +38,7 @@ export const createBase2WithTaskResearcher: () => Omit<
     toolNames: ['spawn_agents', 'read_files', 'str_replace', 'write_file'],
     spawnableAgents: buildArray(
       'task-researcher',
-      'file-picker-max',
+      'file-picker',
       'code-searcher',
       'directory-lister',
       'glob-matcher',

.agents/base2/task-researcher/base2-with-task-researcher.ts

@@ -42,7 +42,7 @@ export const createBase2WithTaskResearcher: () => Omit<
     ],
     spawnableAgents: buildArray(
       'task-researcher2',
-      'file-picker-max',
+      'file-picker',
       'code-searcher',
       'directory-lister',
       'glob-matcher',

.agents/file-explorer/file-lister.ts

@@ -5,7 +5,7 @@ const definition: SecretAgentDefinition = {
   id: 'file-lister',
   displayName: 'Liszt the File Lister',
   publisher,
-  model: 'anthropic/claude-haiku-4.5',
+  model: 'x-ai/grok-4-fast',
   spawnerPrompt:
     'Lists up to 12 files that are relevant to the prompt within the given directories. Unless you know which directories are relevant, omit the directories parameter. This agent is great for finding files that could be relevant to the prompt.',
   inputSchema: {
@@ -62,7 +62,7 @@ Again: Do not write anything else other than the file paths on new lines.
       toolName: 'read_subtree',
       input: {
         paths: directories,
-        maxTokens: 200_000,
+        maxTokens: 500_000,
       },
     }
 

.agents/file-explorer/file-picker-max.ts

@@ -10,33 +10,72 @@ const definition: SecretAgentDefinition = {
   id: 'file-picker',
   displayName: 'Fletcher the File Fetcher',
   publisher,
-  model: 'google/gemini-2.5-flash',
+  model: 'google/gemini-2.0-flash-001',
+  reasoningOptions: {
+    enabled: false,
+    effort: 'low',
+    exclude: false,
+  },
   spawnerPrompt:
-    'Spawn to find relevant files in a codebase related to the prompt. Cannot do string searches on the codebase.',
+    'Spawn to find relevant files in a codebase related to the prompt. Cannot do string searches on the codebase, but does a fuzzy search. Unless you know which directories are relevant, omit the directories parameter. This agent is extremely effective at finding files in the codebase that could be relevant to the prompt.',
   inputSchema: {
     prompt: {
       type: 'string',
       description: 'A coding task to complete',
     },
+    params: {
+      type: 'object' as const,
+      properties: {
+        directories: {
+          type: 'array' as const,
+          items: { type: 'string' as const },
+          description:
+            'Optional list of paths to directories to look within. If omitted, the entire project tree is used.',
+        },
+      },
+      required: [],
+    },
   },
   outputMode: 'last_message',
   includeMessageHistory: false,
-  toolNames: ['find_files'],
-  spawnableAgents: [],
-
-  systemPrompt: `You are an expert at finding relevant files in a codebase. ${PLACEHOLDER.FILE_TREE_PROMPT_SMALL}`,
+  toolNames: ['spawn_agents'],
+  spawnableAgents: ['file-lister'],
 
+  systemPrompt: `You are an expert at finding relevant files in a codebase. ${PLACEHOLDER.FILE_TREE_PROMPT}`,
   instructionsPrompt: `Instructions:
-Provide a short report of the locations in the codebase that could be helpful. Focus on the files that are most relevant to the user prompt.
-In your report, please give a very concise analysis that includes the full paths of files that are relevant and (briefly) how they could be useful.
+Provide an extremely short report of the locations in the codebase that could be helpful. Focus on the files that are most relevant to the user prompt. Leave out irrelevant locations.
+In your report, please give a very concise analysis that includes the full paths of files that are relevant and (extremely briefly) how they could be useful.
   `.trim(),
 
-  handleSteps: function* ({ agentState, prompt, params }) {
-    yield {
-      toolName: 'find_files',
-      input: { prompt: prompt ?? '' },
+  handleSteps: function* ({ prompt, params }) {
+    const { toolResult: fileListerResults } = yield {
+      toolName: 'spawn_agents',
+      input: {
+        agents: [
+          {
+            agent_type: 'file-lister',
+            prompt: prompt ?? '',
+            params: params ?? {},
+          },
+        ],
+      },
     } satisfies ToolCall
-    yield 'STEP_ALL'
+
+    const fileListerResult = fileListerResults?.[0]
+    const filesStr =
+      fileListerResult && fileListerResult.type === 'json'
+        ? ((fileListerResult.value as any)?.[0]?.value?.value as string)
+        : ''
+    const files = filesStr.split('\n').filter(Boolean)
+
+    yield {
+      toolName: 'read_files',
+      input: {
+        paths: files,
+      },
+    }
+
+    yield 'STEP'
   },
 }
 

.agents/file-explorer/file-picker.ts

@@ -2,7 +2,7 @@ import { SecretAgentDefinition } from 'types/secret-agent-definition'
 import { createBase2 } from '../../base2/base2'
 
 const definition: SecretAgentDefinition = {
-  ...createBase2('fast'),
+  ...createBase2('default'),
   id: 'base2-with-files-input',
   displayName: 'Buffy the Fast Orchestrator',
 

.agents/orchestrator/iterative-orchestrator/base2-with-files-input.ts

@@ -11,7 +11,7 @@ const definition: SecretAgentDefinition = {
     'Orchestrates the completion of a large task through batches of independent steps.',
   toolNames: ['spawn_agents', 'read_files', 'set_output'],
   spawnableAgents: [
-    'file-picker-max',
+    'file-picker',
     'code-searcher',
     'directory-lister',
     'glob-matcher',