GitHub GHAS Agentic Code Scanning — CAPI 400 model error

[patrickryankenneth]

🏷️ Discussion Type

Bug

💬 Feature/Topic Area

Code quality

Discussion Details

Summary

GitHub Advanced Security agentic code scanning failed before completing the analysis with:

CAPIError: 400 The requested model is not supported

The runner explicitly attempted to create a Copilot SDK session using claude-opus-5[ReasoningEffort=medium].

Details

• Repository: patrickryankenneth/python-wheels-builds
• Pull request: iOS bug report: strange backstack behavior when navigating to a file #4
• Workflow run: https://github.com/patrickryankenneth/python-wheels-builds/actions/runs/36649326994
• Job: https://github.com/patrickryankenneth/python-wheels-builds/actions/runs/36649326994/job/109679552212
• Integration ID: ghas-code-scanning-agentic
• Autofind version: 0.1.142
• Launcher version: 6e6a0f2762a41ff824a86b598ac7bf85cf8fc131, 0.0.59, 1.4.4
• PR commit: 57f8824868813c7aebf452f8730f78cd9327640c
• Request ID: 601B:27EB7A:A53C4B:C67E19:6ABC5477
• Pull Request ID: 4684080495
• Job ID: 214727083-1379118356-d5bf59ec-7c68-4cec-8997-348d83d557a3

Relevant log

Creating copilot-sdk session with model: claude-opus-5[ReasoningEffort=medium] and clientName: github/code-scanning and contextTier: default

Error creating PR review request: SessionModelError: Execution failed: CAPIError: 400 The requested model is not supported. (Request ID: 601B:27EB7A:A53C4B:C67E19:6ABC5477)

Process completed with exit code 1.

The repository was successfully prepared and the PR diff was fetched before the failure. The failure occurred when creating the model session, before the agentic review completed.

Steps to reproduce

1. Enable the GHAS agentic/AI code-scanning feature.
2. Open or update a pull request containing eligible changes.
3. Allow the github-advanced-security scan to run.
4. The scan fails during Copilot SDK session creation with HTTP 400 for claude-opus-5[ReasoningEffort=medium].

Expected behavior

The configured agentic code-scanning service should successfully select and invoke a model supported by the underlying CAPI integration, or gracefully report an unavailable model without failing the analysis job.

Actual behavior

The service requests claude-opus-5[ReasoningEffort=medium], but the CAPI endpoint returns HTTP 400:

The requested model is not supported.

Could you confirm whether this is a model-availability/routing issue affecting the ghas-code-scanning-agentic integration, and whether the request ID above can be traced to the failing backend request?

[github-actions[bot]]

💬 Your Product Feedback Has Been Submitted 🎉

Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users.

Here's what you can expect moving forward ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams. 
  • Due to the high volume of submissions, we may not always be able to provide individual responses.
  • Rest assured, your feedback will help chart our course for product improvements.
• Other users may engage with your post, sharing their own perspectives or experiences. 
• GitHub staff may reach out for further clarification or insight. 
  • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities.

Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐