Replace before/after content fields with unified patch field across
the diff pipeline. WorktreeDiff now generates patch strings via
createTwoFilesPatch, and all consumers (summary stripping, size
checks, content hashing, TUI sync, ingest queue) operate on the
patch field instead of before/after.
Consolidate model variant into the model object, removing the
separate variant field from MessageV2.User, PlanFollowup inject,
and resolveCodeModel interfaces.
Additional changes:
- Add session-diff module export to kilo-ui package
- Remove batch tool (batch.ts deleted)
- Fix WebSocket proxy to convert Uint8Array to ArrayBuffer
- Switch VscodeSessionTurn from useDiffComponent to useFileComponent
- Update SnapshotFileDiff type references in vscode extension
Align test fixtures with the agent naming convention change
where the "build" agent identifier was replaced by "code"
across all prompt and session interactions.
Resolve merge conflicts across e2e tests, UI components, and core
packages. Clean up conflict markers in test specs by adopting the
upstream `project` fixture pattern over the legacy `withProject`
approach. Alphabetically sort package.json dependencies, apply
consistent code formatting across i18n files, flag declarations,
and TSX components. Update internal API calls to use current
signatures (Permission.defaultLayer, MessageV2.parts, Git.run).
Key changes:
- Remove Windows-specific test.skip guards and conflict markers
- Replace deprecated `git` util import with `Git.run` in worktree-family
- Drop unused SDK type import from share-next
- Add lib entries to kilo-gateway and kilo-telemetry tsconfigs
- Regenerate models-snapshot.js and SDK types with reordered events
- Fix SDK openapi.json code sample to reference @kilocode/sdk
- Add onCleanup import to popover component
Rename agent identity from "OpenCode" to "Kilo" in the kimi system
prompt and delete the large models-api.json test fixture file that is
no longer needed.
* fix: pass resourceName to Azure provider from env or config
The azure custom loader was returning empty options, causing the
@ai-sdk/azure SDK to fail with 'Azure OpenAI resource name setting is
missing' when AZURE_RESOURCE_NAME is set in the environment.
Read resourceName from provider config options, AZURE_RESOURCE_NAME, or
AZURE_OPENAI_RESOURCE_NAME env vars (in that order of precedence) and
pass it explicitly to the SDK options, consistent with how
azure-cognitive-services handles its resource name.
Fixes#8273
* fix: also support baseURL for azure provider to avoid resourceName requirement
Users with a full endpoint URL (e.g. https://resource.openai.azure.com/openai/v1)
can now set baseURL in provider options or AZURE_OPENAI_ENDPOINT env var.
Per @ai-sdk/azure docs, baseURL takes precedence over resourceName and makes
it optional, fixing the 'resource name setting is missing' error for both
configuration styles.
* fix: add xhigh reasoning effort to Azure provider for GPT-5.4+
Azure variant logic was missing xhigh even though @ai-sdk/openai adds it
for models with release_date >= 2025-12-04. Azure GPT-5.4 now exposes
the same xhigh effort level as OpenAI/Kilo Gateway.
* fix(cli): annotate Azure reasoning changes
---------
Co-authored-by: marius-kilocode <marius@kilocode.ai>
Marius