You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When writing long files in Kimi CLI v1.30, the UI refresh progressively slows down during write operations, lagging minutes to tens of minutes behind actual disk completion. The file content is already fully written to disk (verified by opening in external editors), but the CLI UI continues to slowly refresh, creating severe workflow disruption.
To Reproduce
Steps to reproduce the behavior:
Run Kimi CLI v1.30 on Ubuntu 24.04
Request generation of a file ~800 lines (code or documentation)
Observe the UI write progress indicator
During the "slow refresh" phase, open the target file in an external editor (e.g., VS Code, vim, cat)
Observe: File is complete on disk while CLI UI continues to lag for minutes to tens of minutes
Expected behavior
UI should reflect write progress in near real-time, with seconds of delay at most—not minutes.
Actual behavior
Metric
Value
File size tested
~800 lines
UI lag duration
Several minutes to tens of minutes
Disk write status
Complete (verified externally)
Occurrence frequency
High / consistent
Affected modes
Both ACP and Web mode
Affected file types
Code and documentation
Environment
Kimi CLI: 1.30
OS: Ubuntu 24.04
Modes affected: ACP, Web
Severity
High — This makes long file operations practically unusable, as users cannot reliably determine when the operation is actually complete.
Additional context
This is clearly a UI rendering/buffering bottleneck, not a disk I/O issue
The delay scales with file length (shorter files less affected)
No visible error messages or crashes—just extreme UI slowness
Describe the bug
When writing long files in Kimi CLI v1.30, the UI refresh progressively slows down during write operations, lagging minutes to tens of minutes behind actual disk completion. The file content is already fully written to disk (verified by opening in external editors), but the CLI UI continues to slowly refresh, creating severe workflow disruption.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
UI should reflect write progress in near real-time, with seconds of delay at most—not minutes.
Actual behavior
Environment
Kimi CLI: 1.30
OS: Ubuntu 24.04
Modes affected: ACP, Web
Severity
High — This makes long file operations practically unusable, as users cannot reliably determine when the operation is actually complete.
Additional context
Screencast.from.2026-04-08.11-38-38.webm