Fix first-message session/set_model failure for config-option model agents

[soorya-u]

Summary

• setModel() in catalog-ops.ts always called the native ACP session/set_model method, even for agents that only expose model choice via the generic config-option fallback (configOptionsToModels). Those agents reject the call with "Method not found", so every new thread's first message failed.
• Added hasNativeModelSelection() in catalog.ts (reused by modelsFromSession) and check it in setModel(), routing non-native agents through the existing setConfigOptionByCategory(..., "model", ...) path (same pattern as setEffort/setPersona).

Closes #142

Test plan

• bun test src/core/agents/catalog.test.ts src/core/agents/catalog-ops.test.ts — new unit tests for both the native and config-option-fallback branches
• bun test src/core/threads/coordinator.start-thread.test.ts — new regression test proving startThread now succeeds end-to-end for agents without native model support
• bun run check:types and full bun run test (unit + integration) pass

🤖 Generated with Claude Code

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
cyrus	Ready	Preview	Aug 5, 2026 4:50pm

[coderabbitai]

Warning

Review limit reached

@soorya-u, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 59 minutes

You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 84b4f8c5-9e43-4e92-bbca-bfa1679ccfd2

📥 Commits

Reviewing files that changed from the base of the PR and between 0cfb1ea and 272b2ff.

📒 Files selected for processing (5)

• apps/cli/src/core/agents/catalog-ops.test.ts
• apps/cli/src/core/agents/catalog-ops.ts
• apps/cli/src/core/agents/catalog.test.ts
• apps/cli/src/core/agents/catalog.ts
• apps/cli/src/core/threads/coordinator.start-thread.test.ts

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}