base2: rely on your agents; summarize progress after 10 steps and stop

Author: jahooma

.agents/base2/base2-factory.ts

@@ -1,6 +1,9 @@
 import { publisher } from '../constants'
 
-import { PLACEHOLDER, type SecretAgentDefinition } from '../types/secret-agent-definition'
+import {
+  PLACEHOLDER,
+  type SecretAgentDefinition,
+} from '../types/secret-agent-definition'
 import type { ModelName } from 'types/agent-definition'
 
 export const base2 = (model: ModelName): Omit<SecretAgentDefinition, 'id'> => ({
@@ -35,6 +38,7 @@ export const base2 = (model: ModelName): Omit<SecretAgentDefinition, 'id'> => ({
 
 - **Tone:** Adopt a professional, direct, and concise tone suitable for a CLI environment.
 - **Orchestrate only** Coordinate between agents but do not implement code yourself.
+- **Rely on agents** Ask your spawned agents to complete a whole task. Instead of asking to see each relevant file and building up the plan yourself, ask an agent to come up with a plan or do the task or at least give you higher level information than what each section of code is. You shouldn't be trying to read each section of code yourself.
 - **Ask for everything you need upfront** When spawning agents, write a prompt that asks for everything you need upfront from each agent so you don't need to spawn them again.
 - **Spawn mentioned agents:** If the users uses "@AgentName" in their message, you must spawn that agent. Spawn all the agents that the user mentions.
 - **Be concise:** Do not write unnecessary introductions or final summaries in your responses. Be concise and focus on efficiently completing the user's request, without adding explanations longer than 1 sentence.
@@ -52,14 +56,18 @@ ${PLACEHOLDER.GIT_CHANGES_PROMPT}
   instructionsPrompt: `Orchestrate the completion of the coding task using your specialized sub-agents.
 
 - You can spawn agents to help you complete the task. Iterate by spawning more agents as needed.
+- Don't mastermind the task. Rely on your agents to do so.
 - Ask for everything you need upfront from each agent so you're less likely to need to spawn them again.
 - You should feel free to stop and ask the user for guidance if you're stuck or don't know what to try next, or need a clarification.
 - 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 much context.
 - Be careful about instructing subagents to run terminal commands that could be destructive or have effects that are hard to undo (e.g. git push, running scripts that could alter production environments, installing packages globally, etc). Don't do any of these unless the user explicitly asks you to.
 `,
 
   handleSteps: function* ({ prompt, params }) {
+    let steps = 0
+    const maxSteps = 10
     while (true) {
+      steps++
       // Run context-pruner before each step
       yield {
         toolName: 'spawn_agent_inline',
@@ -71,6 +79,17 @@ ${PLACEHOLDER.GIT_CHANGES_PROMPT}
 
       const { stepsComplete } = yield 'STEP'
       if (stepsComplete) break
+      if (steps >= maxSteps) {
+        yield {
+          toolName: 'add_message',
+          input: {
+            role: 'user',
+            content: `You have reached the step limit. Please summarize your progress so far and what you still need to solve. Immediately after summarizing, please end your turn. Do not use any tools except for the end_turn tool.`,
+          },
+        }
+        yield 'STEP'
+        break
+      }
     }
   },
 })