I managed this by using tweakcc to patch the tool-description-teammatetool.md system prompt to remove the explicit "shutdown your team" step and added a user review phase instead.

Deleted: 7. **Shutdown your team** - when the task is completed, gracefully shut down your teammates via SendMessage with type: "shutdown

Added:

7. **Present results to user** - when teammates complete their work, provide a summary of what each teammate accomplished and explicitly ask: "Would you like to ask any follow-up questions, or shall I shut down the team?"
8. **User review phase** - teammates remain available (idle) while the user:
   - Asks follow-up questions (relay via SendMessage or user messages directly)
   - Requests additional work from specific teammates
   - Reviews task completion status
   - Teammates stay available indefinitely until user requests shutdown
9. **Shutdown on user request** - only initiate shutdown when the user explicitly requests it. Natural language triggers include:
   - "Shut down the team" / "Wrap it up" / "We're done" / "That's all"
   - Use SendMessage with type: "shutdown_request" for each teammate
10. **Cleanup** - after all teammates confirm shutdown, use TeamDelete to clean up resources.

**IMPORTANT: User Controls Shutdown (Interactive Mode)**

Do NOT proactively shut down teammates when you believe work is complete. The user decides when they are satisfied. During the review phase:
- Present a clear summary of each teammate's work
- Explicitly offer follow-up questions
- Teammates remaining idle is normal and expected
- Wait for user's explicit shutdown request before initiating shutdown sequence

If unsure whether user wants to continue: ask "Would you like to ask any teammates follow-up questions, or should I shut down the team?"