sync to main#1
Open
darkogj wants to merge 4222 commits into
Open
Conversation
fix(vscode): declare Pierre worker dependency for builds
…d-process-port-scans fix(cli): limit background process port scans
# Conflicts: # packages/kilo-jetbrains/backend/src/main/kotlin/ai/kilocode/backend/app/KiloBackendAppService.kt
feat(cli): show running spinner in subagent footer
…toggle fix(cli): toggle export dialog checkboxes on mouse click
fix(tui): handle newlines in DialogAlert messages
feat(cli): add profile command
…leading-dash-positional
…1.14.42 # Conflicts: # bun.lock # packages/opencode/src/cli/cmd/run.ts # packages/opencode/src/cli/cmd/tui/context/tui-config.tsx # packages/opencode/src/cli/cmd/tui/thread.ts # packages/opencode/src/cli/cmd/tui/ui/dialog-alert.tsx # packages/opencode/src/kilocode/server/httpapi/instance.ts # packages/opencode/src/kilocode/server/instance.ts # packages/opencode/src/server/routes/global.ts # packages/opencode/src/server/routes/instance/index.ts # packages/opencode/src/server/routes/ui.ts # packages/opencode/test/kilocode/global-config-refresh.test.ts # packages/opencode/test/kilocode/server/httpapi-public.test.ts
…sitional fix(cli): preserve --raw atoms verbatim in run handler (#9622)
test(jetbrains): stabilize backend SSE tests
Co-authored-by: kilo-code-bot[bot] <240665456+kilo-code-bot[bot]@users.noreply.github.com>
* Add Atomic Chat as a first-class local provider. Ship the atomic-chat plugin with auto-discovery on localhost:1337, register the provider in models.dev fixtures, and document setup for VS Code and CLI. * Remove dead code Removed atomicChat provider mapping from legacy migration. * Update Atomic Chat provider icon to theme-colored vector. Replace the embedded raster icon with a currentColor SVG symbol so it matches provider icon styling and inherits UI color consistently. * Allow optional API key for local Atomic Chat and LM Studio providers. Load the atomic-chat plugin despite named constant exports, register local-server auth in the plugin, and let CLI and VS Code connect with an empty key on localhost. * Gate Atomic Chat discovery behind explicit opt-in * Update packages/plugin-atomic-chat/src/utils/should-probe-atomic-chat.ts * Remove dead branch in atomic-chat model ref probe. Drop the modelID check (never equals provider key) and the duplicate providerID branch. * Fix PR CI: register atomic chat plugin and complete i18n. Restore atomic-chat in default-plugins after main merge, add missing sidebar locale keys, and annotate shared upstream diffs. * Format i18n locale files and ProviderConnectDialog with Prettier. * Address PR review: docs order, narrow annotations, plugin fixes. Reorder local-models providers per maintainer feedback; use inline kilocode_change markers in dialog-provider. Share ModelStatusCache, fix config discovery abort/timeout, throw on fetch failure, and resolve bot review warnings. * Align dialog-provider with upstream keymap bindings after rebase. Restore useBindings instead of useKeyboard so shared-file diff stays minimal and passes annotation checks. * Update packages/kilo-vscode/webview-ui/src/components/settings/ProviderConnectDialog.tsx * Deduplicate Atomic Chat /v1/models fetch on config discovery. Use a single shared models endpoint request in enhanceConfig instead of separate health and discovery calls. * Fix kilo-code-bot review: import provider key and log cache errors. Export ATOMIC_CHAT_PROVIDER_KEY from local-providers for the webview, log cache warm failures, and throw on network errors in fetchModelsEndpoint. * fix(plugin-atomic-chat): harden discovery and reduce chat toasts Reuse auto-detect model list to avoid duplicate /v1/models calls, wire AbortSignal into fetch, replace silent catches with logging, and only surface validation errors in chat.params. * fix(plugin-atomic-chat): refresh model cache on chat validation retries Bypass the 15s model list cache after the first failed attempt so retryWithBackoff can observe newly loaded models. * Update packages/plugin-atomic-chat/src/utils/index.ts * fix(plugin-atomic-chat): repair categorizeError not_found branch Restore return statement and map "not loaded" validation errors to not_found after bot commit broke the if block. --------- Co-authored-by: Cursor <cursoragent@cursor.com> Co-authored-by: kilo-code-bot[bot] <240665456+kilo-code-bot[bot]@users.noreply.github.com>
Co-authored-by: kilo-code-bot[bot] <240665456+kilo-code-bot[bot]@users.noreply.github.com>
fix(jetbrains): render multi-release change notes
…disclosure icon Aligns the VSCode extension and kilo-ui with the JetBrains plugin, which replaced the brain-circuit icon with the book-open-check icon for the 'may be used for training data' indicator in the model picker.
release(jetbrains): v7.0.1-rc.7
…icon fix(vscode): replace brain-circuit with book-open-check for training disclosure
docs(kilo-docs): update JetBrains EAP guidance
docs(cli): refresh npm package README
fix(cli): isolate release target builds
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
15 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.
Hey! Darko from Kilo here 👋
Saw you forked Kilo, really appreciate for building on top of us.
We are putting together a short Kilo Show segment on why people contribute to open source, and would love to include real perspectives from folks like you.
If you are open to it, would you be up for sharing a quick thought or two on what motivates you (or would motivate you) to contribute to open source?
Also opened a small PR to sync your fork with main in case that is useful.