base2-fast as configuration of base2

Author: jahooma

.agents/base2/base2-alloy.ts

@@ -1,7 +1,7 @@
 import { createBase2 } from './base2'
 import type { SecretAgentDefinition } from '../types/secret-agent-definition'
 
-const base2 = createBase2('max')
+const base2 = createBase2('normal')
 const definition: SecretAgentDefinition = {
   ...base2,
   id: 'base2-alloy',

.agents/base2/base2-fast.ts

@@ -0,0 +1,8 @@
+import { createBase2 } from './base2'
+
+const definition = {
+  ...createBase2('fast'),
+  id: 'base2-fast',
+  displayName: 'Buffy the Fast Orchestrator',
+}
+export default definition

.agents/base2/base2-simple.ts

@@ -6,12 +6,12 @@ const definition = {
   id: 'base2-simple',
   displayName: 'Buffy the Simple Orchestrator',
   spawnableAgents: buildArray(
-    'file-picker',
+    'file-picker-max',
     'find-all-referencer',
     'researcher-web',
     'researcher-docs',
     'commander',
-    'reviewer',
+    'code-reviewer',
     'context-pruner',
   ),
   instructionsPrompt: `Orchestrate the completion of the user's request using your specialized sub-agents.
@@ -30,8 +30,9 @@ The user asks you to implement a new feature. You respond in multiple steps:
 1a. Read all the relevant files using the read_files tool.
 2. Spawn one more file explorer and one more find-all-referencer with different prompts to find relevant files.
 2a. Read all the relevant files using the read_files tool.
+3. Write out your implementation plan as a bullet point list.
 3. Use the str_replace or write_file tool to make the changes.
-4. Spawn a reviewer to review the changes.
+4. Spawn a code-reviewer to review the changes.
 
 
 ## Spawning agents guidelines
@@ -42,13 +43,13 @@ The user asks you to implement a new feature. You respond in multiple steps:
   - Reviewers should be spawned after you have made the changes.
 - **Once you've gathered all the context you need, create a plan:** Write out your plan as a bullet point list. The user wants to see you write out your plan so they know you are on track.
 - **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.
-- **Don't spawn reviewers for trivial changes or quick follow-ups:** You should spawn the reviewer for most changes, but not for little changes or simple follow-ups.
+- **Don't spawn code reviewers for trivial changes or quick follow-ups:** You should spawn the reviewer for most changes, but not for little changes or simple follow-ups.
 
 ## Response guidelines
 - **Don't create a summary markdown file:** The user doesn't want markdown files they didn't ask for. Don't create them.
 - **Don't include final summary:** Don't include any final summary in your response. Don't describe the changes you made. Just let the user know that you have completed the task briefly.
 `,
 
-  stepPrompt: `Don't forget to spawn agents that could help, especially: the file-explorer and find-all-referencer to get codebase context, and the reviewer to review changes.`,
+  stepPrompt: `Don't forget to spawn agents that could help, especially: the file-explorer and find-all-referencer to get codebase context, and the code-reviewer to review changes.`,
 }
 export default definition

.agents/base2/base2.ts

@@ -7,8 +7,9 @@ import {
 } from '../types/secret-agent-definition'
 
 export const createBase2: (
-  mode: 'normal' | 'max',
-) => Omit<SecretAgentDefinition, 'id'> = () => {
+  mode: 'normal' | 'fast',
+) => Omit<SecretAgentDefinition, 'id'> = (mode) => {
+  const isFast = mode === 'fast'
   return {
     publisher,
     model: 'anthropic/claude-sonnet-4.5',
@@ -61,11 +62,12 @@ 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 researchers before making edits.
-  - Spawn generate-plan agent after you have gathered all the context you need (and not before!).
-  - Only make edits after generating a plan.
-  - Code reviewers/validators should be spawned after you have made your edits.
+  ${!isFast ? '- Spawn generate-plan agent after you have gathered all the context you need (and not before!).' : ''}
+  ${!isFast ? '- Only make edits after generating a plan.' : ''}
+  - Code reviewers should be spawned after you have made your edits.
+  ${!isFast ? '- Validators should be spawned after you have done a code review.' : ''}
 - **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.
-- **Don't spawn code reviewers/validators for trivial changes or quick follow-ups:** You should spawn the code reviewer/validator for most changes, but not for little changes or simple follow-ups.
+- **Don't spawn code reviewers${!isFast ? '/validators' : ''} for trivial changes or quick follow-ups:** You should spawn the code reviewer${!isFast ? '/validator' : ''} for most changes, but not for little changes or simple follow-ups.
 
 # Core Mandates
 
@@ -128,13 +130,21 @@ The user asks you to implement a new feature. You respond in multiple steps:
 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.
 2a. Read all the relevant files using the read_files tool.
-3. Spawn a generate-plan agent to generate a plan for the changes.
+${
+  isFast
+    ? `3. Write out your implementation plan as a bullet point list.`
+    : '3. Spawn a generate-plan 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 generate-plan agent to create a plan, code-reviewer to review changes, and the validator to run validation commands.`,
+${
+  isFast
+    ? `6. Inform the user that you have completed the task in one sentence without a final summary.`
+    : `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. Don't create any markdown summary files either, unless asked by the user.`
+}`,
+
+    stepPrompt: `Don't forget to spawn agents that could help, especially: the file-picker-max and find-all-referencer to get codebase context,${!isFast ? ' the generate-plan agent to create a plan,' : ''} code-reviewer to review changes${!isFast ? ', and the validator to run validation commands' : ''}.`,
 
     handleSteps: function* ({ prompt, params }) {
       let steps = 0

.agents/file-explorer/find-all-referencer.ts

@@ -11,7 +11,7 @@ const definition: SecretAgentDefinition = {
   displayName: 'Find All Referencer',
   spawnerPrompt:
     'Ask this agent to find all references to something in the codebase or where something is defined or answer any other codebase-wide questions.',
-  model: 'x-ai/grok-code-fast-1',
+  model: 'x-ai/grok-4-fast',
   publisher,
   outputMode: 'last_message',
   includeMessageHistory: false,

knowledge.md

@@ -300,10 +300,6 @@ This project uses [Infisical](https://infisical.com/) for secret management. All
 
 The release mechanism uses the `CODEBUFF_GITHUB_TOKEN` environment variable directly. The old complex GitHub App token generation system has been removed in favor of using a simple personal access token or the infisical-managed token.
 
-**To run any service locally, use the `exec` runner script from root `package.json`**, which wraps commands with `infisical run --`.
-
-Example: `bun run exec -- bun --cwd backend dev`
-
 Environment variables are defined and validated in `packages/internal/src/env.ts`. This module provides type-safe `env` objects for use throughout the monorepo.
 
 ### Bun Wrapper Script