You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 1918681
Browse filesBrowse the repository at this point in the historyBrowse files
test(cursor): prove the wire-budget consequence behind the search flag
#1832 flips `supports_search_tool` for Cursor on the reasoning that deferred
discovery keeps the MCP catalog out of `exec.description`, and that inlining it
can push the advertised catalog past Cursor's 120KB serialized limit. The
catalog-projection tests assert the flag; nothing asserted the consequence.
These measure it on the real serializer. A deferred catalog stays inside
`CURSOR_TOOL_BYTES_LIMIT` and keeps both `exec` and `wait`; the same two tools
exceed the cap once the nested catalog is inlined into `exec.description`.
The second test pins #1830's actual symptom -- a child whose advertised catalog
contains no Responses execution tool at all. Whatever else the budget drops,
`exec` and `wait` must be what survives, and the trimmed result must fit.
Note on scope: the flag lives in routed catalog metadata consumed by the Codex
client, so it is not serialized into a Cursor turn request. Asserting it inside
a protobuf test would prove nothing, which is why the two concerns stay in two
files.
0 commit comments