rename best-of-n-orchestrator to best-of-n-editor

Author: jahooma

.agents/base2/base2.ts

@@ -62,7 +62,7 @@ export function createBase2(
       'researcher-web',
       'researcher-docs',
       'commander',
-      isGpt5 ? 'best-of-n-orchestrator-gpt-5' : 'best-of-n-orchestrator',
+      isGpt5 ? 'best-of-n-editor-gpt-5' : 'best-of-n-editor',
       'context-pruner',
     ),
 
@@ -81,7 +81,7 @@ Continue to spawn layers of agents until have completed the user's request or re
 - **Sequence agents properly:** Keep in mind dependencies when spawning different agents. Don't spawn agents in parallel that depend on each other. Be conservative sequencing agents so they can build on each other's insights:
   - Spawn file pickers, code-searcher, directory-lister, glob-matcher, commanders, and web/docs researchers before making edits.
   ${buildArray(
-    `- Spawn a ${isGpt5 ? 'best-of-n-orchestrator-gpt-5' : 'best-of-n-orchestrator'} agent to implement the changes after you have gathered all the context you need (and not before!).`,
+    `- Spawn a ${isGpt5 ? 'best-of-n-editor-gpt-5' : 'best-of-n-editor'} agent to implement the changes after you have gathered all the context you need (and not before!).`,
   ).join('\n  ')}
 - **Spawn with the correct prompt and/or params:** Each agent has a schema for the input it expects. The prompt is an optional string, and the params is a json object. Note that some agents don't take any input prompt or params.
 - **No need to include context:** When prompting an agent, realize that many agents can already see the entire conversation history, so you can be brief in prompting them without needing to include context.
@@ -193,7 +193,7 @@ ${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.`,
   `- 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.`,
   `- Use the write_todos tool to write out your step-by-step implementation plan.${hasNoValidation ? '' : ' You should include at least one step to validate/test your changes: be specific about whether to typecheck, run tests, run lints, etc.'}`,
-  `- You must spawn the ${isGpt5 ? 'best-of-n-orchestrator-gpt-5' : 'best-of-n-orchestrator'} 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.`,
+  `- 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${isFast ? ' briefly' : ''} by running appropriate validation commands for the project (e.g. typechecks, tests, lints, etc.). 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.`,
@@ -258,7 +258,7 @@ function buildImplementationStepPrompt({
   return buildArray(
     isMax &&
       `Keep working until the user's request is completely satisfied${!hasNoValidation ? ' and validated' : ''}. `,
-    `You must spawn the ${isGpt5 ? 'best-of-n-orchestrator-gpt-5' : 'best-of-n-orchestrator'} agent to implement any code changes. Don't forget to do this! `,
+    `You must spawn the ${isGpt5 ? 'best-of-n-editor-gpt-5' : 'best-of-n-editor'} agent to implement any code changes. Don't forget to do this! `,
     `After completing the user request, summarize your changes in a sentence or a few short bullet points. Do not create any summary markdown files or example documentation files, unless asked by the user. If you already summarized your changes, then end turn and don't say anything else.`,
     isGpt5 &&
       `IMPORTANT: if you are completely done with the user's request, you must call the task_completed tool to end your turn.`,
@@ -267,6 +267,6 @@ function buildImplementationStepPrompt({
 
 function buildPlanOnlyStepPrompt({}: {}) {
   return buildArray(
-    `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-orchestrator agent to implement. Do not use the write_todos tool.`,
+    `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')
 }

.agents/base2/best-of-n/best-of-n-editor-gpt-5.ts

@@ -0,0 +1,7 @@
+import { createBestOfNEditor } from './best-of-n-editor'
+
+const definition = {
+  ...createBestOfNEditor('gpt-5'),
+  id: 'best-of-n-editor-gpt-5',
+}
+export default definition

.agents/base2/best-of-n/best-of-n-orchestrator.ts renamed to .agents/base2/best-of-n/best-of-n-editor.ts

@@ -5,9 +5,9 @@ import type {
   AgentStepContext,
   StepText,
   ToolCall,
-} from 'types/agent-definition'
+} from '../../types/agent-definition'
 
-export function createBestOfNOrchestrator(
+export function createBestOfNEditor(
   model: 'sonnet' | 'gpt-5',
 ): Omit<SecretAgentDefinition, 'id'> {
   const isGpt5 = model === 'gpt-5'
@@ -16,10 +16,10 @@ export function createBestOfNOrchestrator(
     publisher,
     model: isGpt5 ? 'openai/gpt-5' : 'anthropic/claude-sonnet-4.5',
     displayName: isGpt5
-      ? 'Best-of-N GPT-5 Implementation Orchestrator'
-      : 'Best-of-N Fast Implementation Orchestrator',
+      ? 'Best-of-N GPT-5 Implementation Editor'
+      : 'Best-of-N Fast Implementation Editor',
     spawnerPrompt:
-      'Orchestrates multiple implementor agents to generate implementation proposals, selects the best one, and applies the changes. Do not specify an input prompt for this agent; it reads the context from the message history.',
+      'Edits code by orchestrating multiple implementor agents to generate implementation proposals, selects the best one, and applies the changes. Do not specify an input prompt for this agent; it reads the context from the message history.',
 
     includeMessageHistory: true,
     inheritParentSystemPrompt: true,
@@ -310,7 +310,7 @@ function* handleStepsGpt5({
 }
 
 const definition = {
-  ...createBestOfNOrchestrator('sonnet'),
-  id: 'best-of-n-orchestrator',
+  ...createBestOfNEditor('sonnet'),
+  id: 'best-of-n-editor',
 }
 export default definition

.agents/base2/best-of-n/best-of-n-orchestrator-gpt-5.ts

@@ -18,7 +18,7 @@ const definition: SecretAgentDefinition = {
     'researcher-web',
     'researcher-docs',
     'commander',
-    'best-of-n-orchestrator',
+    'best-of-n-editor-gpt-5',
     'context-pruner',
   ),
 
@@ -32,7 +32,7 @@ The user asks you to implement a new feature. You respond in multiple steps:
 
 - Gather context on the user's request by spawning agents and reading files.
 - Use the write_todos tool to write out your step-by-step implementation plan.
-- Use the best-of-n-orchestrator tool to implement the changes. This is the best way to make high quality code changes -- strongly prefer using this agent over the str_replace or write_file tool.
+- Use the best-of-n-editor-gpt-5 tool to implement the changes. This is the best way to make high quality code changes -- strongly prefer using this agent over the str_replace or write_file tool.
 - For smaller fixes, use the str_replace or write_file tool to make the changes.
 - Test your changes by running appropriate validation commands for the project (e.g. typechecks, tests, lints, etc.). You may have to explore the project to find the appropriate commands.`,