[eshurakov]

What

Force KILO_EXPERIMENTAL_BACKGROUND_SUBAGENTS=false in every cloud agent session environment (SessionService.getSaferEnvVars), so the Kilo CLI runs Task subagents in the foreground.

Why

Background subagents let the root session emit session.idle before its work is published. cloud-agent-next treats a root session.idle as successful completion, so a run can be marked completed while nothing was actually done. This was observed as code reviews completing with no review posted, because the agent never reached the publication step.

Running subagents in the foreground keeps the root turn blocked on each task call, so it cannot go idle mid-flow.

Notes

• Set in the system-managed env block, so it applies to all cloud sessions and cannot be overridden by a profile. It also covers Bitbucket reviews, which discard user-provided env vars.
• Trade-off: subagent work is serialized instead of running in parallel, which lengthens some runs.

Verification

• pnpm exec vitest run src/session-service.test.ts — 150 passed; the new case asserts the value is false by default and still false when a profile sets true.
• pnpm run typecheck (root tsgo --noEmit + wrapper typecheck) — pass.
• oxfmt --check on both changed files — clean.

[kilo-code-bot]

Code Review Summary

Status: No Issues Found | Recommendation: Merge

Executive Summary

Reviewed the two-file change that forces KILO_EXPERIMENTAL_BACKGROUND_SUBAGENTS=false for all cloud session environments; the value is placed in the reserved env block, so it correctly overrides profile/user env and is covered by a new test.

Files Reviewed (2 files)

• services/cloud-agent-next/src/session-service.ts
• services/cloud-agent-next/src/session-service.test.ts

---

_{Reviewed by deepseek-v4.1-flash · Input: 0 · Output: 0 · Cached: 0}

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