Tab Limits
A guardrail for enthusiastic AI agents. Maximum tabs, minimum chaos.
Questions this answers
- How do I prevent AI agents from creating too many terminal tabs?
- Can MCP tools create unlimited tabs?
- What happens if an AI agent opens dozens of terminal tabs?
- How to limit AI agent resource usage in the terminal?
How it works
Chau7's settings include a configurable tab limit that applies exclusively to MCP-created tabs. When an agent calls tab_create, Chau7 checks the current count of MCP-spawned tabs against the limit. If the limit is reached, the tool returns an error message explaining the constraint rather than silently failing or creating the tab anyway.
The limit only affects tabs created through the MCP server. Tabs you create manually through the UI are never counted against the limit and are never blocked. This means you always retain full control of your terminal while the guardrail applies only to automated agent behavior.
Why it matters
AI agents operating in loops can create tabs faster than you can notice. A coding agent that retries a failing test might open ten tabs in ten seconds. Tab limits set a ceiling on MCP-created tabs so runaway automation stays contained. It is a five-second setting that prevents a very bad afternoon.
Frequently asked questions
What is the default tab limit?
The default limit is set conservatively to prevent runaway behavior while still allowing agents to work with multiple tabs for parallel tasks. You can adjust it in Chau7's settings to match your workflow.
Does the limit count tabs that have been closed?
No. The limit counts currently open MCP-created tabs. Once an agent closes a tab, that slot is freed for a new one. This encourages agents to clean up after themselves.