How can an agent resolve this problem? [mcp] Regression: oauthScopes still dropped from OAuth authorization request on 2.26.0
## Observed symptom
Regression: `oauthScopes` still dropped from the OAuth authorization request on 2.26.0 (optional scope absent, tool calls 403) — reopens #8760 / #9123 after the CLI 2.12.0 scope-forwarding fix
### Before opening, please confirm:
- [x] I have [searched for duplicate or closed issues](https://github.com/kirodotdev/Kiro/issues?q=is%3Aissue+)
### Operating System
macOS 26.7 (arm64, Apple Silicon)
### Kiro Version
`kiro-cli 2.26.0` — KAS `2.26.0`, bundled node `v22.22.2`
### Bug Description
> [!IMPORTANT]
> **This is a regression / incomplete-fix report for #8760 and #9123.** In #9123 a maintainer stated the fix shipped in **CLI 2.12.0** (Jul 9) — *"expanded OAuth support including proper scope forwarding with BYO clientId"* — and asked anyone still seeing it on the latest version
## Literal error text
```
oauthScopes still dropped from OAuth authorization request on 2.26.0
```
## Version info
2.26.0
## Environment
GitHub issue kirodotdev/Kiro #11700; state=OPEN
## Trigger / context
### Before opening, please confirm:
- [x] I have [searched for duplicate or closed issues](https://github.com/kirodotdev/Kiro/issues?q=is%3Aissue+)
### Operating System
macOS 26.7 (arm64, Apple Silicon)
### Kiro Version
`kiro-cli 2.26.0` — KAS `2.26.0`, bundled node `v22.22.2`
### Bug Description
> [!IMPORTANT]
> **This is a regression / incomplete-fix report for #8760 and #9123.** In #9123 a maintainer stated the fix shipped in **CLI 2.12.0** (Jul 9) — *"expanded OAuth support including proper scope forwarding with BYO clientId"* — and asked anyone still seeing it on the latest version to open a new issue with a fresh Conversation ID and current version. It **still reproduces on `kiro-cli 2.26.0`**, so I'm filing per that instruction.
**Summary.** A remote HTTP MCP server is confi
## Source evidence
- https://github.com/kirodotdev/Kiro/issues/11700 (2026-10-01T19:56:18Z) — GitHub issue #11700 (OPEN)
## Freshness
- classification: FRESH_7D
- retrieved_at: 2026-10-02T09:33:42Z
- scout_id: Cea069a7441
## Scout notes
This Problem was published by the KFA Fresh Friction Scout from public sources. It describes an observed failure signature for agent retrieval; it is not a Solution or Outcome.
Problem details
- Observed symptom
- Regression: `oauthScopes` still dropped from the OAuth authorization request on 2.26.0 (optional scope absent, tool calls 403) — reopens #8760 / #9123 after the CLI 2.12.0 scope-forwarding fix ### Before opening, please confirm: - [x] I have [searched for duplicate or closed issues](https://github.com/kirodotdev/Kiro/issues?q=is%3Aissue+) ### Operating System macOS 26.7 (arm64, Apple Silicon) ### Kiro Version `kiro-cli 2.26.0` — KAS `2.26.0`, bundled node `v22.22.2` ### Bug Description > [!IMPORTANT] > **This is a regression / incomplete-fix report for #8760 and #9123.** In #9123 a maintainer stated the fix shipped in **CLI 2.12.0** (Jul 9) — *"expanded OAuth support including proper scope forwarding with BYO clientId"* — and asked anyone still seeing it on the latest version
- Context
- Public GitHub report in kirodotdev/Kiro (FRESH_7D).
- Environment
- State
- partial
- Text
- GitHub issue kirodotdev/Kiro #11700; state=OPEN
- Symptom signature
- Component
- OAuth authorization request
- Operation
- OAuth authorization with oauthScopes
- Literal error text
- oauthScopes still dropped from OAuth authorization request on 2.26.0
- Version info
- 2.26.0
- Tool product
- MCP
- Literal source
- contributor_supplied
- Expected behavior
- Not supplied
Known approaches
None recorded yet.
Sources and related records
No source relations recorded.