Repository navigation
fix(cloud-agent-next): run review sessions with platform config only - #8545
Conversation
Code Reviewer sessions now start the Kilo server with project-level configuration and skill discovery disabled, on both the legacy and control-plane runtimes. Platform rules and skills under the session HOME are unaffected. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Code Review SummaryStatus: No Issues Found | Recommendation: Merge Reviewed the new Assumptions: Files Reviewed (5 files)
Reviewed by deepseek-flash-latest · Input: 87K · Output: 17.5K · Cached: 2.9M Review guidance: REVIEW.md from base branch |
Summary
Code Reviewer sessions now start the Kilo server with
KILO_DISABLE_PROJECT_CONFIG=1andKILO_DISABLE_EXTERNAL_SKILLS=1, so a review runs with the configuration, rules and skills the platform provides rather than whatever project-level config the reviewed checkout carries. Repository review guidance keeps coming fromREVIEW.mdon the base branch, which is fetched separately.src/shared/kilo-server-env.ts: one helper,kiloServerEnvForOrigin, returns the flags forcreatedOnPlatform === 'code-review'and nothing for other origins.agent_*): applied inSessionService.buildRuntimeEnvalongside the other reserved Kilo variables, so profile env cannot override it.workspace_*): applied inbuildWorktreeKiloEnvironment, which now readscreatedOnPlatformfrom the route spec it already receives.Other session origins are unchanged.
Verification
Visual Changes
N/A
Reviewer Notes
The flags are set after profile and inherited env in both planes, matching how
KILO_EXPERIMENTAL_BACKGROUND_SUBAGENTSis pinned today.🤖 Generated with Claude Code