CTO Per-Tab Override
Token optimization where you want it, full output where you don't. Tab by tab.
Questions this answers
- Can I enable token tracking for just one terminal tab?
- How to disable CTO for a specific AI session?
- Per-tab token optimization settings in terminal
- Control token monitoring per terminal tab
How it works
CTO Per-Tab Override gives you three modes for each tab: default (follows the global CTO setting), force on (always active regardless of global setting), and force off (always inactive regardless of global setting). You set the override through the MCP server or the tab context menu.
This is useful when you want CTO active globally but need to exclude a tab running a tool that produces noisy API traffic, or conversely when CTO is off globally but you want to profile one specific session without affecting others.
Why it matters
Global on/off is too coarse for multi-tab workflows. You want CTO active on the tab where Claude Code is burning through tokens, but disabled on the tab where you are debugging output formatting. Per-tab override gives you that control without affecting other sessions.
Frequently asked questions
What are the three override modes?
Default follows the global CTO setting. Force On enables CTO on the tab regardless of the global setting. Force Off disables CTO on the tab regardless of the global setting.
Can I set the override programmatically?
Yes. The MCP server exposes a tab_set_cto endpoint that accepts the tab ID and override value. This makes it easy to script CTO control into your workflow.