Add config options to cap max number of open tabs #1804

Activity

1. holny commented on Sep 7, 2026

   

   holny

   on Sep 7, 2026

   Contributor

   More actions

   Taking this. Proposed shape:

   • New global option --max-tabs <n> (plus AGENT_BROWSER_MAX_TABS env), 0/unset = unlimited, applies per daemon session like the other launch options.
   • Enforced daemon-side so both CLI and MCP surfaces are covered: tab new and any action that would create an additional tab fail with a clear error stating the current count, the cap, and pointing at tab close / close to free a slot.
   • Deliberately no automatic tab killing: silently closing the agent's pages would be worse than a refusal, so the cap refuses instead.

   PR to follow.

   🚀React with 🚀1Reacted by Wei
2. holny

   added a commit that references this issue on Sep 7, 2026

   feat: add --max-tabs to cap open tabs per session

   ...

   This issue will close once commit 78fbb9b is merged into the 'main' branch.

   78fbb9b
3. Railly

   added

   feature

   area:tabsArea: tabsArea: tabs

   on Nov 3, 2026
4. vercel-labs

   locked and limited conversation to collaborators on Nov 3, 2026
5. Railly

   converted this issue into a discussion #2370 on Nov 3, 2026