fix(cli): default KILO_PLATFORM to 'cli' for standalone CLI use#9759
Open
lambertjosh wants to merge 1 commit intomainfrom
Open
fix(cli): default KILO_PLATFORM to 'cli' for standalone CLI use#9759lambertjosh wants to merge 1 commit intomainfrom
lambertjosh wants to merge 1 commit intomainfrom
Conversation
Without this, kilo-telemetry falls back to process.platform so PostHog 'platform' rows show darwin/linux/win32 for the 9.8k+ weekly CLI users instead of 'cli'. Embedders (VS Code, JetBrains, cloud code-review, app-builder) already set KILO_PLATFORM themselves, so this only catches the direct-CLI path. Mirrors the KILOCODE_FEATURE default just above. Refs #9599
Contributor
Code Review SummaryStatus: No Issues Found | Recommendation: Merge Files Reviewed (2 files)
Reviewed by gpt-5.5-20260423 · 125,033 tokens |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Standalone
kiloCLI usage is reported to PostHog asplatform=darwin/linux/win32instead ofplatform=cli, because the CLI entry point never setsKILO_PLATFORMandkilo-telemetry/telemetry.ts:60falls back toprocess.platform. Over the last 7 days that accounts for ~9.8k users and ~891kLLM Completionevents mis-tagged as OS values on the new v7 path (appName=kilo-cli).Embedders that spawn
kilo serve(VS Code extension, JetBrains plugin, cloud code-review, app-builder) already setKILO_PLATFORMthemselves, and the cloud session-ingest path (kilo_meta.platforminkilo-sessions.ts:684) already defaults to"cli"— so this one-line default just aligns PostHog with the backend signal. Mirrors the shape of the existingKILOCODE_FEATUREdefault immediately above it.Refs #9599. Does not address the broader overlap between
KILO_PLATFORM,KILO_CLIENT, andKILOCODE_FEATURE— that's a separate cleanup.