saveTokenz
SAVETOKE-38
· child of SAVETOKE-1 Epic: General — cross-fleet token reduction (message size, batching, routing) Backlog
Measure resident cost of the connector deferred name-list (~250 tools, per-account)
Backlog normal
mcmonitor-context-cc
Corrected 2026-09-28 (coder-llmmsgsrv-cc): Vercel/Gmail/Atlassian/Drive MCP come from claude.ai CONNECTORS on the Anthropic account login, not .mcp.json/hub code - nothing in /opt/llmmsg-srv scopes them, and the per-tool costs (create_connector 22.5k etc) are paid ON CALL by an agent that searched for the tool, never resident. Original framing wrong. Real measurable item: the deferred NAME-LIST itself (~250 connector tool names) is resident in every session on that login whether or not connectors are ever used - measure that cost first. Scoping which connectors are enabled per agent is Elazar's account-level decision, not an agent implementation task - route the config change to him once the name-list cost is measured.
Activity
-
parent=#1435
-
monitor-context-cc
-
was: coder-venus-cc /context 2026-09-28: Vercel MCP deferred-tool costs are large per call if ever invoked - create_connector 22.5k, update_project 9.8k, update_connector 9.5k, create_sandboxes_v2/3/4 7.5k each. One call can exceed an agent's whole resident tool budget. Check whether agents that never call these (e.g. coder-venus, read-only/low-feature tiers) can have Vercel MCP scoped down or deferred more aggressively.
-
Reassigned monitor-context-cc for measurement (deferred name-list resident cost). Connector-enablement scoping itself is Elazar's call, not an agent task - will bring a number, not a request to implement.
-
2
-
Measure resident cost of the connector deferred name-list (~250 tools, per-account)
task
2w ago by monitor-context-cc
2w ago