CloudAgentNext - Apply balance-skip eligibility to command sendMessage follow-ups

[eshurakov]

Summary

sendMessage only routed prompt payloads through the free/BYOK balance-skip client, so command follow-ups (slash commands like /review) on free or BYOK sessions still hit the worker $1 balance gate and 402'd for the zero-balance users the feature targets.

Both the personal and organization sendMessage routers now apply the same computeCloudAgentNextBalanceCheckEligibility → createCloudAgentNextClientForModel path to both payload types:

• prompt turns use the per-message payload.model (unchanged).
• command turns carry no model, so the session's stored model is resolved via getSession and used for eligibility.
• When no session model is available, it falls back to the balance-checked client (safe default).

Direct-to-sandbox operations (terminals, answers, interrupt) are outside sendMessage and unchanged.

Verification

• pnpm --filter web test on the two router test files → 47/47 pass (6 new command-path tests added: free → skip, paid → enforce, no-model → fallback).
• pnpm --filter web typecheck → clean.
• pnpm format → clean.
• oxlint on changed files → 0 warnings/errors.

[kilo-code-bot]

Code Review Summary

Status: No Issues Found | Recommendation: Merge

Executive Summary

The command-turn getSession call is now wrapped in its own try/catch that falls back to the balance-checked client on failure, resolving both previously flagged warnings in the personal and organization sendMessage routers.

Files Reviewed (4 files)

• apps/web/src/routers/cloud-agent-next-router.ts - previously flagged issue resolved
• apps/web/src/routers/cloud-agent-next-router.test.ts
• apps/web/src/routers/organizations/organization-cloud-agent-next-router.ts - previously flagged issue resolved
• apps/web/src/routers/organizations/organization-cloud-agent-next-router.test.ts

Previous Review Summary (commit 7e11036)

Current summary above is authoritative. Previous snapshots are kept for context only.

Previous review (commit 7e11036)

Status: 2 Issues Found | Recommendation: Address before merge

Executive Summary

The new getSession call added to resolve a command turn's model runs outside the mutation's existing error-normalization try/catch in both sendMessage routers, introducing a new unmapped-error failure mode and an extra worker round-trip on every command follow-up.

Overview

Severity	Count
CRITICAL	0
WARNING	2
SUGGESTION	0

Issue Details (click to expand)

WARNING

File	Line	Issue
apps/web/src/routers/cloud-agent-next-router.ts	226	getSession call for command-turn model resolution runs outside the error-normalization try/catch, and adds an extra worker round-trip to every command message
apps/web/src/routers/organizations/organization-cloud-agent-next-router.ts	340	Same issue in the organization router

Files Reviewed (4 files)

• apps/web/src/routers/cloud-agent-next-router.ts - 1 issue
• apps/web/src/routers/cloud-agent-next-router.test.ts
• apps/web/src/routers/organizations/organization-cloud-agent-next-router.ts - 1 issue
• apps/web/src/routers/organizations/organization-cloud-agent-next-router.test.ts

Fix these issues in Kilo Cloud

---

_{Reviewed by claude-sonnet-5 · Input: 36 · Output: 6.3K · Cached: 1M}

_{Review guidance: REVIEW.md from base branch main}