Skip to content

sync to main - #1

Open
darkogj wants to merge 6250 commits into
gratex:mainfrom
Kilo-Org:main
Open

sync to main#1
darkogj wants to merge 6250 commits into
gratex:mainfrom
Kilo-Org:main

Conversation

@darkogj

@darkogj darkogj commented May 21, 2026

Copy link
Copy Markdown

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.

kirillk and others added 30 commits July 27, 2026 11:11
fix(jetbrains): split bundled publish Gradle tasks
…rkflow

Passing the JETBRAINS_CERTIFICATE_CHAIN / JETBRAINS_PRIVATE_KEY multiline
secret content directly as certificateChain/privateKey Gradle properties
gets mishandled by the zip-signer CLI when signPlugin and
verifyPluginSignature run as separate Gradle invocations (#12567), causing
verifyPluginSignature to fail with 'Invalid argument: ***' as the masked
multiline content is split into extra CLI args.

Mirror script/build-version.sh: write the certificate chain and private
key to temp files under $RUNNER_TEMP and wire
certificateChainFile/privateKeyFile (file-based) into the intellij
signing extension instead of certificateChain/privateKey (raw content).

Co-authored-by: kiloconnect[bot] <240665456+kiloconnect[bot]@users.noreply.github.com>
Co-authored-by: kiloconnect[bot] <240665456+kiloconnect[bot]@users.noreply.github.com>
…-signing-file-vars

fix(jetbrains): use file-based signing secrets for bundled publish workflow
…e-reviews

docs: note that bot-generated PRs are ignored by default in Code Reviews
feat(jetbrains): support queued prompts
…-raw-secrets

fix(jetbrains): avoid writing release signing secrets
Cloud now supports NVIDIA as a direct BYOK provider. Documents the
`nvidia-byok` key ID, the required model prefix, tool-calling
requirement, and NVIDIA's Developer Program endpoint restrictions.
…-files-rc

fix(jetbrains): use file signing inputs for bundled publish
…-setting

# Conflicts:
#	packages/opencode/test/tool/registry.test.ts
…can (#12585)

* fix(cli): enforce permissions on shell commands the parser fails to scan

* fix(cli): fail closed on error chunks without command names, move pwsh execution test to kilo file
…ings

CI:
- Render the config console's active overlay target from its new object
  shape instead of passing it to JSX.
- Make the config overlay `expected` revision optional in the schema,
  writer, and handler so clients without a binding write unconditionally
  instead of receiving a 400, and add the missing PUT /indexing/consent
  exerciser scenario. Regenerate the SDK for the schema change.
- The multi-project Storybook story called useLanguage() outside its
  provider and rendered nothing; it now uses the story translator.
- Scope indexing test select locators by row title, since the tab gained a
  project selector that shifted positional lookups.

Review findings:
- Gate worktree creation, promotion, and multi-version creation on the
  target project's state: waitForStateReady only tracked the active
  project, so those handlers could mutate a background project's state
  before it loaded.
- Re-check trust and enablement for every project-stamped message instead
  of resolving contexts through the unchecked map lookup.
- Register projects through resolveProjectRoot so a folder inside a linked
  worktree cannot duplicate an existing project, and fix that helper to
  issue valid rev-parse commands.
- Validate the persisted activeTarget shape before applying it.
- Stop throwing from workspace/session directory resolution: it runs
  eagerly per webview message, where a throw dropped the message.
- Evict superseded config bindings per scope and directory.
- Guard the multi-project rename against the blur that Escape triggers.
- Unregister routes when disabling secondary projects.
- Replace the section message substring test with an explicit type set.
- Match an open session tab in the project search's current item and scope
  selection acks by project id.
- Filter untrusted projects out of indexing consent, and restore config
  scope switching plus project-scoped indexing writes that the consent
  rework had removed.
- Round-trip the sessions-collapsed mutation so multi-project bodies, which
  render purely from pushed state, reflect the toggle.
lambertjosh and others added 30 commits July 30, 2026 10:40
The RunScriptManager keys entries by worktreeId and the webview sends
"local" for whichever project's local context is selected, so in
multi-project mode two projects' local runs collided in one entry: a
second project's Run button stopped the first project's script, and the
state payload spread every project's run statuses into the active
project's push, rendering foreign local rows as running.

The provider now namespaces the local key as <projectId>:local at the
message boundary (ambient project scope, no webview protocol change),
RunController treats the qualified suffix as a local run (repo root cwd,
"local" branch label), each project's state payload is filtered to its
own worktrees plus its un-namespaced local key, and runStatus emissions
are routed with a projectId stamp so background-project statuses land in
their own webview store. ScriptTerminalManager keys inherit the same
qualification, and its view mapping already namespaces run terminals to
the matching project bucket.
feat(vscode): multi-project Agent Manager
…inal

feat(agent-manager): run setup scripts in panel terminal
fix: surface provider error details from Responses API stream failures
* fix(docs-sync): calibrate triage/edit prompts against over-documentation

* fix(docs-sync): intercept revert PRs and annotate reverted digest entries

* fix(docs-sync): harden revert trailer parsing and surface unannotated reverts

* fix(docs-sync): report per-target unannotated reverts, excluding by-design cancellations

* fix(docs-sync): surface revert chains in the step summary without resolving them

* test(docs-sync): fix depth-3 chain fixture and split mixed chain signals correctly
The setup-terminal gate introduced in #12703 changed the detail-stack
predicate from !contextEmpty() && !history() to !history && selection
!== null. An unassigned session has selection === null but a live
session showing, so contextEmpty() is false there. The new gate
dropped that case, blanking the content pane, leaving readOnly() dead
code, and unmounting every live xterm on selection.

showTerminalStack now takes contextEmpty and returns !history &&
(selection !== null || !contextEmpty), restoring the pre-#12703
semantics while keeping the provisioning worktree (empty context with a
side Setup tab) rendering the stack.

Adds a showTerminalStack regression suite covering the unassigned,
history, selected-context, provisioning, and empty cases.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.