Skip to content

refactor(cli): inline question-tool client gating#9735

Open
kilo-code-bot[bot] wants to merge 2 commits intomainfrom
mark/inline-question-gating
Open

refactor(cli): inline question-tool client gating#9735
kilo-code-bot[bot] wants to merge 2 commits intomainfrom
mark/inline-question-gating

Conversation

@kilo-code-bot
Copy link
Copy Markdown
Contributor

@kilo-code-bot kilo-code-bot Bot commented Apr 30, 2026

Summary

🚨 DO NOT MERGE BEFORE THE OPENCODE v1.14.29 MERGE 🚨

Inlines the question-tool client gating back into packages/opencode/src/tool/registry.ts instead of going through KiloToolRegistry.question(). Extracting that one-liner into a helper reshaped the surrounding upstream line, which was making the opencode rebase harder than it needed to be. Inlining keeps the only real Kilo delta (adding "vscode" to the allowed clients) as a single-line kilocode_change patch over the upstream code — much easier to carry across merges.

Also drops the now-unused KiloToolRegistry.question() export.

Moves the `questionEnabled` check back inline in `tool/registry.ts`
instead of delegating to `KiloToolRegistry.question()`. The extracted
helper changed the shape of the upstream line, making the shared file
harder to rebase during opencode merges. Inlining keeps the diff local
to that one line (just adding "vscode" to the allowed clients) so
future merges conflict less.
@kilo-code-bot
Copy link
Copy Markdown
Contributor Author

kilo-code-bot Bot commented Apr 30, 2026

Code Review Summary

Status: No Issues Found | Recommendation: Merge

Files Reviewed (2 files)
  • packages/opencode/src/kilocode/tool/registry.ts
  • packages/opencode/src/tool/registry.ts

Reviewed by gpt-5.5-2026-04-23 · 134,137 tokens

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.

1 participant