fix(app): reserve chat request slots during MCP discovery - #53050

Thanks for your contribution!

This PR doesn't have a linked issue. All PRs must reference an existing issue.

Please:

1. Open an issue describing the bug/feature (if one doesn't exist)
2. Add Fixes #<number> or Closes #<number> to this PR description

See CONTRIBUTING.md for details.

The following comment was made by an LLM, it may be inaccurate:

Issue: #53049 (also linked with Closes #53049 in the description).

For the required v2 target, the default-branch PR-standards workflow's closingIssuesReferences-only check can produce a false needs:issue label. The existing v2 workflow already includes the PR-body fallback. Evidence and the request to bring that fallback to dev: #53040 (comment).

Rebased onto v2 at f72a103a4b94fb9a467294877bf6243dd99c6bdc; current head is f5c8aa3c07d432c9758b45bf30930e141061e2be. git range-diff confirms the patches are unchanged.

All 12 request-queue tests passed. Native pre-push bun run check also passed (36 typecheck tasks).

The upstream test, check and nix-eval runs on this head are action_required, rather than failed tests. Could a maintainer approve the fork workflow runs? Test run.

Rebased onto current v2 at 8eb2ebd96cb2e25f9607f753e892a533628b8d46. New head: a4586ade8a0c9e00a0b05196cc8c63983f601fd3.

Resolved the upstream formatting/rename/import conflicts while retaining the fix's behavior. All 12 request-queue tests passed. The native pre-push bun run check also passed all 36 tasks. GitHub reports this head as conflict-free.

The full upstream test/check result is not established on this head yet; only the local checks above are confirmed.

Rebased onto v2 at 216c31174. Current head: 6f57a9e9ea10eb15a689ff68702a003be8f0be21.

All 12 request-queue tests passed. The patch is unchanged according to git range-diff.

The native pre-push bun run check passed on this head. Full upstream CI remains subject to maintainer approval for fork workflow runs; it is not claimed green. Could a maintainer approve the test, check, and nix-eval workflows?

Rebased onto current v2 at 7d179e83f42a9bb6377b6f34d8d4fcbf04707621 (package version 2.0.26). New head: 624d11ca2c0a88c327ab4c1297ab52351b63d0a2.

The patch is unchanged according to git range-diff. All 12 request-queue tests passed. The native pre-push bun run check passed all 36 tasks and the lease-protected push completed successfully. Existing lint warnings remain.

The description still references Closes #53049. Full upstream CI is not claimed green; fork workflows may require maintainer approval.

Base clarification: release commit 9b4ec5714d481559990db0a816d5dec19541a814 is a sibling of the current development line, not its ancestor; these PRs target and are rebased onto upstream/v2 as requested.

Rebased onto v2 at 4617210822bdbb31e5749751afbfb4584ccedac8; head: df02d846f4148e7976a42bf01a22da118357544f. git range-diff confirms the patch is unchanged.

All 12 request-queue tests and native pre-push bun run check passed (36 typecheck tasks; lint warnings remain). The PR's current dev target is unchanged.

Upstream CI is not green: check, test, and nix-eval on this exact head are action_required and need maintainer approval. PR standards passed.

Rebased onto current dev at 34d8ded0c58dd66808c1d60e081e8c66da12a896, rather than the old v2 alias. Published head: cbfeea9de29b6ffd638ddc18374420c0b8b796b6.

Typed the existing queue diagnostic payload and documented test assertion invariants for the new whole-file GUI lint check. All 12 queue tests and app typecheck passed; scheduling behavior is unchanged. Required lint:changed and the native pre-push gate passed (36/36 typecheck tasks).

The exact-head test, check, and nix-eval workflows are action_required, not green; maintainer approval is still needed. PR standards passed.

Automated PR Cleanup

Thank you for contributing to opencode.

Due to the high volume of PRs from users and AI agents, we periodically close older PRs using automated criteria so maintainers can focus review time on the most active and community-supported contributions.

This PR was closed because it matched the following cleanup criteria:

• The PR was created more than 1 month ago
• The PR had fewer than 2 positive reactions
• Positive reactions are counted as thumbs-up, heart, celebration, or rocket reactions on the PR

PRs created within the last month are not affected by this cleanup.

If you believe this PR was closed incorrectly, or if you are still actively working on it, please leave a comment explaining why it should be reopened. A maintainer can review and reopen it if appropriate.

Thanks again for taking the time to contribute.

This PR is still being maintained. Could a maintainer reopen it after the automated age/reaction cleanup?

I have ported the fix onto 893e8dc43f05e872d4cac603486ce8a7181170fa in 5b32f4d98fd1b1d882a6566ca1084886b2382184. Upstream moved request classification into request-queue-machine.ts; the patch now extends that owner rather than restoring the old queue implementation. /api/command, /api/mcp and their nested routes use the existing slow-request share, while current priorities, concurrency limits and timeouts remain unchanged.

The 22 focused machine/transport tests pass, including dispatching a session read while MCP catalog requests remain held. The native pre-push lint/typecheck gate also passed. This addresses the still-open #53049; it does not claim that every Desktop timeout has been reproduced or fixed.