Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Conversation

@pull
Copy link

@pull pull bot commented Jan 29, 2026

See Commits and Changes for more details.


Created by pull[bot] (v2.0.0-alpha.4)

Can you help keep this open source service alive? 💖 Please sponsor : )

Neonsy and others added 30 commits January 29, 2026 13:19
Adding a new entry for Kimi K2.5 in the changeset.
- Add fetchKilocodeNotificationsCore() for shared API fetching logic
- Add displayNativeNotifications() for showing native VSCode notifications
- Add fetchKilocodeNotificationsOnStartup() for standalone startup fetch
- Refactor fetchKilocodeNotificationsHandler to use shared functions
- Call fetchKilocodeNotificationsOnStartup in extension activation

This ensures notifications are fetched even when the chat panel isn't open.
Updated supportsTemperature to false based on API specs.
- Changed URL path from /chat to /kilocode/chat for consistency
- Added vscode.commands.executeCommand('kilo-code.SidebarProvider.focus')
  before all /kilocode/* actions so users can see the result
- Updated tests to verify focus command is called
Use `${Package.name}.SidebarProvider.focus` instead of hardcoded
'kilo-code.SidebarProvider.focus' for consistency with the rest of
the codebase.
Fix model selection after anonymous usage
The /kilocode/chat URL path was not working correctly because
getVisibleInstance() returns undefined when the extension panel
isn't already open, causing an early return before the sidebar
focus command could execute.

This fix handles the /kilocode/chat path specially by:
1. First focusing the sidebar to open the Kilo Code extension
2. Using getInstance() which waits for the provider to become visible
3. Then performing the chat actions (removeClineFromStack, refreshWorkspace, etc.)

This ensures the extension opens properly before attempting to
interact with the chat interface.
…cation URLs

When displaying native notifications with action URLs that start with vscode://,
the protocol is now replaced with the appropriate protocol for the current IDE
(e.g., cursor://, vscodium://, vscode-insiders://) using vscode.env.uriScheme.

This ensures notification action URLs work correctly in all VS Code-compatible IDEs.
@pull pull bot locked and limited conversation to collaborators Jan 29, 2026
@pull pull bot added the ⤵️ pull label Jan 29, 2026
@pull pull bot merged commit 78364eb into tqa24:main Jan 29, 2026
10 checks passed
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants