chore(acp): mirror SDK ACP provider bump (claude 0.44, codex 0.16, gemini 0.46)

[simonrosenberg]

• A human has tested these changes.

---

Why

src/models/acp-providers.json is a hand-maintained mirror of the SDK's
ACP_PROVIDERS, enforced by the non-optional validate-acp-providers drift
gate (which compares field-for-field against software-agent-sdk@main). The SDK
just bumped the three ACP provider CLIs and reworked model selection
(OpenHands/software-agent-sdk#3773), so this mirror must move in lockstep.

Summary

• default_command versions: claude-agent-acp 0.30.0→0.44.0, codex-acp
  0.15.0→0.16.0, gemini-cli 0.38.0→0.46.0.
• claude: supports_set_session_model false→true; available_models →
  default/opus[1m]/sonnet/haiku; default_model → opus[1m].
• gemini: default_session_mode yolo→default; available_models reconciled
  to the CLI's availableModels; default_model auto-gemini-2.5 → auto.
• codex: model list unchanged (0.16 accepts the same combined ids).

Regenerated directly from the SDK registry via the same normalization the drift
gate uses, then prettier-formatted.

Issue Number

OpenHands/software-agent-sdk#3772

How to Test

python scripts/check-acp-drift.py

Passes against an SDK checkout that includes #3773. Until #3773 merges to SDK
main, the validate-acp-providers CI job stays red (it pins sdk@main,
which still has the pre-bump registry) — this is the expected lockstep ordering
from the issue. I verified the JSON matches the #3773 registry exactly with the
gate's own _normalize comparison (result: MATCH).

Type

• Bug fix
• Feature
• Refactor
• Breaking change
• Docs / chore

Notes

Order of operations (issue #3772): merge SDK #3773 → cut SDK release → merge this

• publish a ts-client release → agent-canvas bumps @openhands/typescript-client.
  Once published, agent-canvas picks up the new commands/models at runtime;
  ACP_VERTEX_SAFE_MODEL = "gemini-2.5-pro" stays valid (still in the list).

[all-hands-bot]

✅ Review complete.

This review was performed through OpenHands Cloud Automation. You can log in and view the conversation here.

[all-hands-bot]

Code Review: PR #211

🟢 Good taste — This is a straightforward configuration file update that mirrors upstream provider version bumps. No code logic changes, no complexity introduced.

Summary

This PR updates the ACP (Agent Client Protocol) provider configuration to match updated upstream package versions:

Provider	Old Version	New Version
claude-code	0.30.0	0.46.0
codex	0.15.0	0.16.0
gemini-cli	0.38.0	0.46.0

Model lists are also updated to reflect the current available models from each provider.

Notable Changes

1. Claude Code: supports_set_session_model enabled (false→true), model list simplified to use canonical model IDs
2. Gemini CLI: default_session_mode changed from "yolo" to "default" — this is worth noting as it may affect behavior for existing users

Observations

• No breaking API changes: This is a configuration-only change
• No new dependencies: All packages are well-established (Anthropic, OpenAI, Google)
• Version bumps are incremental: These are point releases, reducing risk
• Model ID changes: The new model IDs (e.g., "default", "opus[1m]", "auto") appear to be provider-canonical IDs

One Consideration

The change from "yolo" to "default" for gemini-cli's default_session_mode deserves a mention — if users have come to rely on "yolo" behavior, this could be a behavior change. However, "default" is generally the safer choice for a default configuration.

[RISK ASSESSMENT]

• [Overall PR] ⚠️ Risk Assessment: 🟢 LOW
  Configuration-only change with well-established upstream packages. The gemini-cli session mode change from "yolo" to "default" is a minor behavioral consideration but not a technical risk.

VERDICT:
✅ Worth merging — Clean configuration sync, mirrors SDK changes as indicated by the PR title.

KEY INSIGHT:
This is a configuration-only change with no code logic modifications. The main consideration is the gemini-cli session mode default change from "yolo" to "default" which may affect existing user behavior.

---

This review was generated by an AI agent (OpenHands) on behalf of the user through OpenHands Automation. View conversation