feat(kiloclaw): show volume usage on user instance tab#2391
Open
evanjacobson wants to merge 7 commits intomainfrom
Open
feat(kiloclaw): show volume usage on user instance tab#2391evanjacobson wants to merge 7 commits intomainfrom
evanjacobson wants to merge 7 commits intomainfrom
Conversation
- migrate disk usage logic to shared module and API for reuse by UI/admin - replace kiloclaw-controller-telemetry hooks with queryDiskUsage - update InstanceTab to display Volume Usage with a HardDrive icon - remove deprecated hooks.ts and add API route for disk usage - update types to AnalyticsEngineResponse<ControllerTelemetryRow> where needed
![kilo-code-bot[bot]](https://avatars.githubusercontent.com/in/2193792?s=60&v=4){kind=small}
Contributor
Code Review SummaryStatus: No Issues Found | Recommendation: Merge Files Reviewed (1 file)
Reviewed by gpt-5.4-20260305 · 1,011,271 tokens |
Co-authored-by: kilo-code-bot[bot] <240665456+kilo-code-bot[bot]@users.noreply.github.com>
The disk usage query key was shared across all org/personal contexts, causing React Query to briefly show stale volume usage data when switching between personal and org claws. Include organizationId in the query key so each context gets its own cache entry. Also exports and tests the pure utility functions in InstanceTab.
Co-authored-by: kilo-code-bot[bot] <240665456+kilo-code-bot[bot]@users.noreply.github.com>
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
1 participant
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.
Summary
Users had no way to see how much disk space their KiloClaw instance was using. This surfaces it directly in the user-facing Instance tab so users can monitor their own disk consumption without needing support. It also modifies the UI to support the extra field.
Details
- Extracts the Analytics Engine disk-usage query into a shared `@/lib/kiloclaw/disk-usage` module, reused by both the admin endpoint and a new user-scoped `/api/kiloclaw/disk-usage` route. - Redesigns the Instance tab from a flat five-column grid into card-based panels (State/Uptime, Volume Usage with progress bar, Lifecycle stats). - The progress bar uses color thresholds (green → amber at 75% → red at 90%). - The new API route follows the same auth + instance-registry lookup pattern as other user-scoped KiloClaw endpoints. The admin telemetry route is simplified to delegate to the shared module.
Visual Changes
Adding a 6th column would make the UI too condensed. A small refactor was done to enable a cleaner UI.
