sync to main - #1
Merged
Merged
Conversation
Add a pre_release checkbox to the publish workflow that passes --pre-release to vsce package, vsce publish, and ovsx publish. This enables publishing to the VS Code Marketplace pre-release channel without requiring a separate versioning scheme. Closes #8156
…AQ page Move the 'Migrating Your Workspace' content from dashboard.md to faq/general.md where it better fits as a frequently asked question. The FAQ version is expanded with a clear what-migrates/what-doesn't breakdown, workspace memory/context note, and step-by-step integration reconfiguration instructions.
Render the worktree branch dropdowns inline so the dialog focus trap can keep the filter input keyboard-accessible. Autofocus the search field on open and disable placement flipping so filtering does not make the popup jump.
Keep nested popovers from dismissing their parent dialog when users press Escape. This preserves the branch picker close behavior in the new worktree flow without closing the whole modal.
Add a dedicated 'Token Limits' subsection to the custom models page explaining the limit object fields, resolution order, and the behavioral consequences of leaving them unset (compaction disabled, output fallback to 32k, no usage tracking). Also expands the troubleshooting section with compaction-specific guidance.
…n scenarios Rewrite the migration section to explicitly cover three use cases: - Migrating from another OpenClaw provider to KiloClaw - Moving between KiloClaw instances (individual to org or vice versa) - Leaving KiloClaw for another OpenClaw provider Clarify that the process is the same for all three, and distinguish what migrates via backup/restore (workspace files, memory, context) from what needs manual reconfiguration (integrations).
Updated migration instructions for OpenClaw to clarify workspace migration process and reconfiguration of integrations.
…erit caller edit restrictions
…estrictions to sub-agents
Co-authored-by: Joshua Lambert <25085430+lambertjosh@users.noreply.github.com>
…edundant git processes (#8400)
docs(kilo-docs): document limit.context and limit.output model settings
docs(kilo-docs): add workspace migration section to KiloClaw FAQ
…ion status text When plan mode delegates to a subagent the child session can block on a permission or question before the UI starts tracking it, leaving the parent stuck on 'Delegating work' with no visible prompt. - Auto-adopt child sessions in KiloProvider.handleEvent as soon as the task tool part reveals metadata.sessionId — eliminates the race where the child emits a prompt before the webview renderer calls syncSession - Add fetchAndSendPendingQuestions mirroring the existing permission recovery; call both after handleSyncSession so missed prompts are recovered for child sessions - Extend questionCtx with trackedSessionIds + sessionDirectories needed for the recovery path - Improve statusText: when delegating and the session family has pending permissions/questions, show 'Subagent waiting for permission' or 'Subagent waiting for response' instead of generic 'Delegating work' - Add i18n keys for the two new status strings across all 19 locales
fix: stabilize worktree branch selector popovers
Updated the 'whats-new.md' file to reflect upcoming features and improvements regarding the context progress graph and agent management.
Improve FAQ on areas where questions have been asked.
When the agent switched modes automatically (e.g. plan → code via plan follow-up), the VS Code mode picker stayed stuck on the previous value. The root cause was that agentSelections was only written on explicit user picker actions, not updated from incoming message events. - Add resolveSessionAgent() helper that derives the active agent from the latest valid user message, ignoring assistant messages and unknown agent names - Wire handleMessagesLoaded() to reconcile agentSelections from history so the picker is correct when reopening or switching sessions - Wire handleMessageCreated() to update agentSelections whenever a user message arrives with a changed agent field (covers live plan→code, shell commands, command execution, and synthetic mode-switch messages) - Add mode?: string to QuestionOption so the VS Code webview preserves the same question option metadata the backend and shared app already support - Wire QuestionDock.pick() to call session.selectAgent() immediately when a predefined single-choice option carries a mode field, giving instant feedback before the next user message arrives
kilo-maintainer
Bot
force-pushed
the
main
branch
from
April 6, 2026 16:10
05569ee to
fc014b1
Compare
* fix(vscode): scope cycleAgentMode keybinding to Kilo Code panels cmd+. and cmd+shift+. for cycleAgentMode were globally active, overriding VS Code's built-in Quick Fix menu. Add when clauses so the keybindings only activate when a Kilo Code view is focused (sidebar, Agent Manager, or open-in-tab panel). * fix(vscode): fix cycleAgentMode when clause and tab panel dispatch Replace unreliable focusedView with sideBarFocus + custom sidebarVisible context key for sidebar detection. Also dispatch cycleAgentMode actions to active tab panels, which were previously missed. --------- Co-authored-by: kiloconnect[bot] <240665456+kiloconnect[bot]@users.noreply.github.com> Co-authored-by: marius-kilocode <marius@kilocode.ai>
…and-custom-params docs(kilo-docs): add model cost and custom model FAQ entries to whats-new page
docs(kilo-docs): fix custom models page headings and tab order
fix(core): make follow-up execution aware of the saved plan file
kilo-maintainer
Bot
force-pushed
the
main
branch
from
April 7, 2026 16:19
4170b58 to
5650850
Compare
Port snapshot optimizations from upstream OpenCode to reduce git process spawning and prevent concurrent corruption: - Per-gitdir mutex lock (upstream #17878, v1.3.0): serializes concurrent snapshot operations to prevent race conditions - Incremental git add (upstream #17878, v1.3.0): replaces naive `git add .` with diff-files + ls-files + size filtering, skipping files >2MB - Batched revert (upstream #20564, v1.3.14): groups up to 100 files per git checkout call with path-conflict detection, falling back to single-file revert on failure Benchmarks (200 files): - revert: 2,851ms → 191ms (15x faster, 8x fewer git processes) - concurrent track: 2/5 succeed → 5/5 succeed (corruption fixed)
…8524) * feat(agent-manager): add GitHub PR status badge to worktree sidebar Recovered from PR #8515 which was lost when kilo-maintainer[bot] force-pushed release v7.1.23 on a stale base. Co-authored-by: LLRHook <131478441+LLRHook@users.noreply.github.com> * chore: update kilo-vscode visual regression baselines --------- Co-authored-by: LLRHook <131478441+LLRHook@users.noreply.github.com> Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
kilo-maintainer
Bot
force-pushed
the
main
branch
from
April 7, 2026 19:11
dbd7b80 to
760f246
Compare
… items (#8529) Display the git branch name beneath the worktree label when it differs from the display name. Aligns the local card branch style to match (10px, --text-weaker).
feat(vscode): exponential backoff retry with cancel button for rate limiting
feat(cli): re-apply kilocode_change annotation CI check (lost in force push)
Add a go-to-file icon button next to each instruction file entry in the Agent Behaviour > Rules subtab, allowing users to open the file directly in the editor. Uses the established go-to-file icon pattern consistent with DiffPanel and PromptInput components.
Piggyback on the existing `git worktree list --porcelain` call in probeWorktreePresence to detect branch changes (e.g. after checking out a PR branch). Zero additional git calls — the branch info was already returned but discarded.
The pencil icon more clearly conveys "edit this file" compared to the go-to-file icon.
feat(vscode): add open-in-editor icon to instruction files in Rules tab
Recover PR #7981 (force-pushed by publish workflow on April 1, 2026). When the suggested model name exceeds 30 characters (after stripping sub-provider prefix), fall back to the generic "Try Model" label to prevent an oversized notification button. Adds tryModelGeneric i18n key for the fallback label across all 18 locales. See #8558
fix(i18n): clarify built-in mode banner to avoid read-only confusion
fix(vscode): fall back to generic "Try Model" for long model names
Varuu-0
pushed a commit
that referenced
this pull request
Apr 9, 2026
…03464193194226 chore: Update MoonIcon to match standard crescent outline
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
13 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're 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're 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's useful.