MoonshotAI / MoonshotAI/kimi-code
Replace floating warning/error toasts with a collapsible error collection panel in the web UI
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 7.5k
- Forks
- 1.2k
- Avg merge
- 11h 53m
- Merged PRs (30d)
- 350
Description
Problem
The web UI currently displays warnings and errors as individual floating toasts
that auto-dismiss after 6-12 seconds. When multiple errors occur (e.g. during a
network interruption or provider error), they stack up and each one demands the
user's attention before disappearing. There is no way to review past errors
after they auto-dismiss, and no way to clear all errors at once.
Proposed solution
Replace the floating toast system with a collapsible error collection panel:
- A compact badge in the bottom-right corner showing the error count
- Clicking the badge expands a panel listing all errors with expandable diagnostics
- "Clear all" button to dismiss all errors
- "Refresh page" button for connection-related issues
- No auto-dismiss timers — the user controls when to clear
Why this fits Kimi Code
The existing toast system is noisy during error bursts and provides no way
to review past messages. A collection panel is the approach the TUI already
uses for warnings, and this brings the web UI in line with that pattern.
Scope
apps/kimi-web/src/components/WarningToasts.vue— complete rewriteapps/kimi-web/src/i18n/locales/*/warnings.ts— new i18n keys
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with apps/kimi-web/src/components/WarningToasts.vue to understand the current toast flow, then inspect the warning locale files under apps/kimi-web/src/i18n/locales/*/warnings.ts. Done means the web UI has a collapsible error-count panel with expandable diagnostics, Clear all and connection-related Refresh page actions, translated across the affected locale files, and no auto-dismiss timers.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- frontend, internationalization, web-dev
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 64/100