Prefer spawn agents tool to spawn agent inline

Author: jahooma

.agents/prompts/base-prompts.ts

@@ -232,7 +232,7 @@ export const baseAgentUserInputPrompt = (model: Model) => {
 
       "If there are multiple ways the user's request could be interpreted that would lead to very different outcomes, ask at least one clarifying question that will help you understand what they are really asking for, and then use the end_turn tool.",
 
-      'Use the spawn_agents tool to spawn agents to help you complete the user request. You can spawn as many agents as you want.',
+      'Use the spawn_agents tool (and not spawn_agent_inline!) to spawn agents to help you complete the user request. You can spawn as many agents as you want.',
 
       'It is a good idea to spawn a file explorer agent first to explore the codebase from different perspectives. Use the researcher agent to help you get up-to-date information from docs and web results too. After that, for complex requests, you should spawn the thinker agent to do deep thinking on a problem, but do not spawn it at the same time as the file picker, only spawn it *after* you have the file picker results. Finally, you must spawn the reviewer agent to review your code changes.',
       "Important: you *must* read as many files with the read_files tool as possible from the results of the file picker agents. Don't be afraid to read 20 files. The more files you read, the better context you have on the codebase and the better your response will be.",

backend/src/tools/definitions/tool/spawn-agent-inline.ts

@@ -10,6 +10,8 @@ Spawn a single agent that runs within the current message history.
 The spawned agent sees all previous messages and any messages it adds 
 are preserved when control returns to you.
 
+You should prefer to use the spawn_agents tool unless instructed otherwise. This tool is only for special cases.
+
 This is useful for:
 - Delegating specific tasks while maintaining context
 - Having specialized agents process information inline