Repository navigation
Conversation
Code Review SummaryStatus: No Issues Found | Recommendation: Merge Executive SummaryThe incremental change guards the pre-send target check on stored-backend load state, letting the registry validate a not-yet-loaded custom target instead of falsely reporting it deleted; the registry path ( Files Reviewed (4 files)
Previous Review Summaries (5 snapshots, latest commit b69cb54)Current summary above is authoritative. Previous snapshots are kept for context only. Previous review (commit b69cb54)Status: No Issues Found | Recommendation: Merge Executive SummaryThe incremental commit b69cb54 only extends the case-guard allowlist with three backend files whose bare Files Reviewed (1 file)
Previous review (commit a510d83)Status: No Issues Found | Recommendation: Merge Executive SummaryThe incremental commit a510d83 makes Retry re-enter the chat before retrying, so a chat whose open failed now does recover; Files Reviewed (3 files)
Previous review (commit 5ef970d)Status: 1 Issue Found | Recommendation: Address before merge Executive SummaryAll seven findings from the previous review are resolved by Overview
Issue Details (click to expand)SUGGESTION
Files Reviewed (21 files)
Fix these issues in Kilo Cloud Previous review (commit e4a6c42)Status: 7 Issues Found | Recommendation: Address before merge Executive SummaryBackend target staleness and credential retention dominate the remaining findings: a queued question can be silently dropped when its custom backend is deleted, sign-out does not durably delete backend credentials, and the chat list can start on a stale backend. Overview
Issue Details (click to expand)WARNING
SUGGESTION
Fix these issues in Kilo Cloud Previous review (commit 1f91900)Status: 7 Issues Found | Recommendation: Address before merge Overview
Issue Details (click to expand)WARNING
SUGGESTION
Files Reviewed (67 non-locale files + 88 catalogs)
Reviewed by deepseek-v4.1-flash · Input: 88.6K · Output: 7K · Cached: 539.4K Review guidance: REVIEW.md from base branch |
… igor/quick-chat-backends # Conflicts: # apps/mobile/README.md # apps/mobile/src/i18n/permission-prompt-locales.test.ts # apps/mobile/src/i18n/permission-prompt-locales.ts
… igor/quick-chat-backends # Conflicts: # apps/mobile/src/components/chat/chat-screen.tsx
… igor/quick-chat-backends
… igor/quick-chat-backends
main landed the Quick Chat stack as squash merges (#7322-#7342), so the branch's stack history conflicted on 141 files. Resolve by keeping main's integrated content for the stack files, and reapplying this branch's own change on top: - turns.ts keeps main's image support and question shapes, drops the model input, and exports askedMessageId. - turns.test.ts drops the model input and uses Question[] waiting. Verified: turns.test.ts (11) and chat-screen.mounted.test.tsx (14) pass.
main landed the Quick Chat stack as squash merges (#7322-#7342). Resolve the 141-file conflict by keeping main's integrated content and reapplying this branch's mode-chip change on top: - chat-toolbar.tsx keeps main's per-chip disabled dimming and gains the optional modeControl (modeSelector is null without it). - chat-composer.tsx takes modeControl and keeps main's image picker import. - chat-composer.test.ts drops the mode props (no leftover imports). - session-detail-content.test.ts reads customOptions through modeControl. Verified: chat-composer, chat-composer-attachment-send, chat-toolbar, session-detail-content, new-session-configure-form, chat-toolbar-model-name, chat-composer-send-once, chat-screen mounted, and oxlint on the changed files.



Changelog for users
max_completion_tokensor legacymax_tokensfor Chat Completions endpoints.Changelog for maintainers
@kilocode/harness-sdk/plugins/remote-modelentry. The SDK continues to own history, compaction, and tools.Verification
Stack