Documentation 2026-02-21 18:03 UTC to 2026-02-23 21:13 UTC

291httpOnly cookies. Report any issues with severity ratings."291httpOnly cookies. Report any issues with severity ratings."

292```292```

293 293 

294### Choose an appropriate team size

295 

296There's no hard limit on the number of teammates, but practical constraints apply:

297 

298* **Token costs scale linearly**: each teammate has its own context window and consumes tokens independently. See [agent team token costs](/en/costs#agent-team-token-costs) for details.

299* **Coordination overhead increases**: more teammates means more communication, task coordination, and potential for conflicts

300* **Diminishing returns**: beyond a certain point, additional teammates don't speed up work proportionally

301 

302Start with 3-5 teammates for most workflows. This balances parallel work with manageable coordination. The examples in this guide use 3-5 teammates because that range works well across different task types.

303 

304Having 5-6 [tasks](/en/agent-teams#architecture) per teammate keeps everyone productive without excessive context switching. If you have 15 independent tasks, 3 teammates is a good starting point.

305 

306Scale up only when the work genuinely benefits from having teammates work simultaneously. Three focused teammates often outperform five scattered ones.

307 

294### Size tasks appropriately308### Size tasks appropriately

295 309 

296* **Too small**: coordination overhead exceeds the benefit310* **Too small**: coordination overhead exceeds the benefit

42 42 

43### Notification setup43### Notification setup

44 44 

45Never miss when Claude completes a task with proper notification configuration:45When Claude finishes working and is waiting for your input, it fires a notification event. You can surface this event as a desktop notification through your terminal or run custom logic with [notification hooks](/en/hooks#notification).

46 46 

47#### iTerm 2 system notifications47#### Terminal notifications

48 48 

49For iTerm 2 alerts when tasks complete:49Kitty and Ghostty support desktop notifications without additional configuration. iTerm 2 requires setup:

50 50 

511. Open iTerm 2 Preferences511. Open iTerm 2 Settings → Profiles → Terminal

522. Navigate to Profiles → Terminal522. Enable "Notification Center Alerts"

533. Enable "Silence bell" and Filter Alerts → "Send escape sequence-generated alerts"533. Click "Filter Alerts" and check "Send escape sequence-generated alerts"

544. Set your preferred notification delay

55 54 

56Note that these notifications are specific to iTerm 2 and not available in the default macOS Terminal.55If notifications aren't appearing, verify that your terminal app has notification permissions in your OS settings.

57 56 

58#### Custom notification hooks57Other terminals, including the default macOS Terminal, do not support native notifications. Use [notification hooks](/en/hooks#notification) instead.

59 58 

60For advanced notification handling, you can create [notification hooks](/en/hooks#notification) to run your own logic.59#### Notification hooks

60 

61To add custom behavior when notifications fire, such as playing a sound or sending a message, configure a [notification hook](/en/hooks#notification). Hooks run alongside terminal notifications, not as a replacement.

61 62 

62### Handling large inputs63### Handling large inputs

63 64