feat(mobile): show remote instance model catalogs - #5146
Conversation
Code Review SummaryStatus: No Issues Found | Recommendation: Merge Executive SummaryIncremental review of the Files Reviewed (8 files, incremental since 07d23cd)
Notes (non-blocking, not flagged as findings):
Previous Review Summaries (2 snapshots, latest commit 07d23cd)Current summary above is authoritative. Previous snapshots are kept for context only. Previous review (commit 07d23cd)Status: No Issues Found | Recommendation: Merge Executive SummaryIncremental review of the mode-threading refactor and seed-script cleanup: the Files Reviewed (12 files, incremental since a989d07)
Notes (non-blocking, not flagged as findings):
Previous review (commit a989d07)Status: No Issues Found | Recommendation: Merge Executive SummaryReviewed the remote instance model catalog feature across the SDK and mobile app: the sessionless Files Reviewed (19 files)
Notes (non-blocking, not flagged as findings):
Reviewed by kimi-k3 · Input: 145.4K · Output: 17.9K · Cached: 856.7K Review guidance: REVIEW.md from base branch |
Users can select a remote CLI instance and see that instance’s providers and models before starting a session. The app keeps the Kilo Gateway fallback when the instance cannot provide a catalog.
Product managers get provider-aware new-session and continue-session flows for remote CLI instances. Switching instances removes stale selections, and Cloud Agent behavior stays unchanged.
Maintainers get a strict sessionless SDK catalog request, per-instance React Query state, validated model selections, and the existing picker projection reused for gateway fallback and CLI catalogs. This cloud PR depends on PR #5138, which must merge first. The kilocode PR #13014 is the remaining runtime dependency: until it ships, instances reject the sessionless request and the designed Kilo Gateway fallback remains visible. A pre-existing issue can pass an opaque
remote-model-Nvalue when continuing a CLI-catalog session into Cloud Agent; this remains out of scope.E2E: bot-e2e — latest-head verification passed R1 and S1–S6. R1 proves the first catalog option keeps its offered variant. S1 proves the sessionless catalog and provider group. S2 proves a non-Kilo prompt through the local
e2e-local/stub-model; the transcript showsE2E stub provider answered., the in-session picker shows providere2e-local, and the stub log recordsmodel=stub-model. S3 proves Kilo Gateway compatibility and Cloud Agent loading isolation. S4 proves instance switching removes the stale model. S5 proves Continue in a new session. S6 proves the old-CLI gateway fallback without a blocking error.Visual Changes:
Human steps: