Files
kilocode/.changeset
Alex Alecu c529142d72 feat(i18n): translate plan_exit follow-up options in the VS Code sidebar
Add optional `labelKey`/`descriptionKey` to Question.Option and `questionKey`/`headerKey` to Question.Info, annotated with `kilocode_change` markers. Populate these keys from the plan follow-up so the "Ready to implement?" question, "Start new session", and "Continue here" buttons render in the sidebar language while the canonical English labels remain on the reply wire (unchanged server-side matching).
2026-04-20 16:15:06 +03:00
..

Changesets

This directory contains changeset files used to track changes for the next release.

Adding a changeset

When making a user-facing change, run:

bunx changeset add

Or manually create a file .changeset/<slug>.md:

---
"kilo-code": minor
---

Short description of the change for the changelog.

Use patch for bug fixes, minor for new features, major for breaking changes.

Changeset files are consumed at release time when the publish.yml workflow runs, generating changelog entries for the GitHub release notes.