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 9c7e889
Browse filesBrowse the repository at this point in the historyBrowse files
fix(server): keep list_thread_pull_requests unpaged to stay within the agent context budget
Paging inputs (states, cursor, limit) added 233 bytes to the MCP tool list, over main's budget. The thread-read preview cap stays; it costs no model-facing bytes.
Co-Authored-By: Claude Opus 5.5 <[email protected]>
"List PRs linked to a thread, with last known state and stack order (bottom to top). Page with `cursor=nextCursor`. Call only when you need that list. Never as an end-of-work check.",
324
-
parameters: ListThreadPullRequestsInput,
308
+
"List PRs linked to a thread, with last known state and stack order (bottom to top). Call only when you need that list. Never as an end-of-work check.",
309
+
parameters: Schema.Struct({
310
+
environmentId: OrchestratorMcpEnvironmentTarget,
311
+
threadId: Schema.optional(ThreadId.annotate({description: "Thread. Default: this thread."})),
0 commit comments