fix(kiloclaw): restore slash command access - #11798
Merged
Merged
Conversation
imanolmzd-svg
approved these changes
Jun 29, 2026
catrielmuller
enabled auto-merge
June 29, 2026 12:38
Contributor
Code Review SummaryStatus: No Issues Found | Recommendation: Merge Files Reviewed (8 files)
Reviewed by gpt-5.4-20260305 · Input: 116.8K · Output: 12.6K · Cached: 1.6M Review guidance: REVIEW.md from base branch |
catrielmuller
disabled auto-merge
June 29, 2026 12:51
t7tran
pushed a commit
to t7tran/kilocode
that referenced
this pull request
Aug 14, 2026
fix(kiloclaw): restore slash command access
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
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.
Issue
No linked issue. User-reported regression:
/kiloclawno longer opened KiloClaw in the TUI or VS Code extension, while the hosted web chat still worked.Regression introduced on: #10864
Context
The hosted KiloClaw status API now returns numeric timestamp fields. The local CLI backend still decoded those fields as strings, so
/kilo/claw/statusreturned502 Failed to reach KiloClaweven though chat credentials were valid. Both the TUI and VS Code KiloClaw panel gate startup on that local status endpoint.Implementation
Normalize numeric KiloClaw
lastStartedAtandlastStoppedAtvalues to ISO strings at the Kilo Gateway boundary before the CLI HTTP API decodes the status schema. This preserves the existing local SDK/UI contract while accepting the current cloud response shape.Also add
/kiloclawas a VS Code chat-local slash command that opens the existing KiloClaw panel, matching the toolbar command.Screenshots / Video
N/A - no visual changes.
How to Test
Manual/local verification
bun run dev serve --port 0and verified/kilo/claw/statusreturned200with normalized ISOlastStartedAt./kilo/claw/chat-credentialsstill returned200with the token redacted from logs.bun test test/kilocode/server/kilo-gateway-statuses.test.tsfrompackages/opencode/.bun run typecheckfrompackages/opencode/.bun run typecheckfrompackages/kilo-gateway/.bun run typecheckfrompackages/kilo-vscode/.bun run lintfrompackages/kilo-vscode/.bun turbo typechecksuccessfully.Reviewer test steps
/kiloclawand confirm the KiloClaw chat view opens./kiloclawand confirm the KiloClaw panel opens.Blocked checks and substitute verification
Checklist
Get in Touch
GitHub: @catrielmuller