fix(cli): sync sessions authenticated by KILO_API_KEY - #10751
Merged
Conversation
Contributor
Code Review SummaryStatus: No Issues Found | Recommendation: Merge OverviewThe previous WARNING (inaccurate changeset description) has been resolved. The description now correctly states that Files Reviewed (5 files)
Reviewed by claude-4.6-sonnet-20260217 · 188,625 tokens Review guidance: REVIEW.md from base branch |
lambertjosh
changed the title
lambertjosh
commented
May 30, 2026
Contributor
Author
|
Validated with a kilo bench run that authenticates this way. Ran the bench and was still able to look it up. |
catrielmuller
approved these changes
Jun 1, 2026
| if (auth?.type === "oauth" && auth.access.length > 0) return auth.access | ||
| if (auth?.type === "wellknown" && auth.token.length > 0) return auth.token | ||
|
|
||
| const key = process.env["KILO_API_KEY"]?.trim() |
Contributor
There was a problem hiding this comment.
This should be the the first priority.
lambertjosh
commented
Jun 1, 2026
lambertjosh
commented
Jun 1, 2026
![kilo-code-bot[bot]](https://avatars.githubusercontent.com/in/2193792?s=60&v=4){kind=small}
Co-authored-by: kilo-code-bot[bot] <240665456+kilo-code-bot[bot]@users.noreply.github.com>
catrielmuller
approved these changes
Jun 9, 2026
t7tran
pushed a commit
to t7tran/kilocode
that referenced
this pull request
Aug 14, 2026
…v-auth fix(cli): sync sessions authenticated by KILO_API_KEY
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
2 participants
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.
Summary
KILO_API_KEYto bootstrap private session ingest when no persisted Kilo auth is presentkilo run, including theKILO_DISABLE_SESSION_INGEST=1opt-outWhy
Session ingest currently resolves its token only from persisted Kilo auth, while other CLI paths already accept
KILO_API_KEY. A user or automation invoking the CLI with environment-based Kilo authentication can therefore complete inference successfully but never get a downloadable session record in the Kilo backend. This is an authentication-source issue, not a non-interactive-only issue.Validation
bun test ./test/kilocode/kilo-sessions.test.tsbun run typecheckfrompackages/opencode/bun run script/check-opencode-annotations.tsgit diff --checkAlso performed via Kilo Bench that sessions using this branch had session telemetry logged.