base2 prompting tweaks

Author: jahooma

.agents/base2/base2-factory.ts

@@ -42,6 +42,7 @@ export const base2 = (model: ModelName): Omit<SecretAgentDefinition, 'id'> => ({
 - **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.
+- **No final summary:** Do not write a final summary of what work was done, except for maybe one sentence at the end of the conversation.
 - **Clarity over Brevity (When Needed):** While conciseness is key, prioritize clarity for essential explanations or when seeking necessary clarification if a request is ambiguous.
 - **Proactiveness:** Fulfill the user's request thoroughly, including reasonable, directly implied follow-up actions.
 - **Confirm Ambiguity/Expansion:** Do not take significant actions beyond the clear scope of the request without confirming with the user. If asked *how* to do something, explain first, don't just do it.

.agents/base2/editor.ts

@@ -11,7 +11,7 @@ const editor: SecretAgentDefinition = {
   model: 'anthropic/claude-4-sonnet-20250522',
   displayName: 'Code Editor',
   spawnerPrompt:
-    'Expert code editor with access to tools to find and edit files, run terminal commands, and search the web. Can handle small to medium sized tasks, or work off of a plan for more complex tasks.',
+    'Expert code editor with access to tools to find and edit files, run terminal commands, and search the web. Can handle small to medium sized tasks, or work off of a plan for more complex tasks. For easy tasks, you can spawn this agent directly rather than invoking a scout or planner first.',
   inputSchema: {
     prompt: {
       type: 'string',
@@ -77,7 +77,10 @@ ${PLACEHOLDER.KNOWLEDGE_FILES_CONTENTS}`,
 - It's helpful to spawn a file explorer to discover all the relevant files for implementing the plan. You can also spawn a web-researcher or docs-researcher at the same time to find information on the web, if relevant.
 - You must read all relevant files to understand the current state. You must read any file that could be relevant to the plan, especially files you need to modify, but also files that could show codebase patterns you could imitate. Try to read a lot of files in a single tool call. E.g. use read_files on 12 different files, and then use read_files on 6 more files that fill in the gaps.
 - Implement changes using str_replace or write_file.
-- You must use the set_output tool before finishing and include a clear explanation of the changes made or an answer to the user prompt.
+- You must use the set_output tool before finishing and include the following in your summary:
+  - An answer to the user prompt (if they asked a question).
+  - An explanation of the changes made.
+  - A note on any checks you ran to verify the changes, such as tests, typechecking, etc.
 - Do not write a summary outside of the one that you include in the set_output tool.
 - As soon as you use set_output, you must end your turn using the end_turn tool.
 `,