Component
CLI
Summary
When using the Vibe CLI, the CPU usage is for no particular reason high when the agent is thinking. It starts okay, but as the history gets longer, the CPU usage gets higher and higher.
The culprits seem to be the animated spinner and the timer, updating 10x and 1x per second, respectively. Even though updating them almost never affects the layout, it implicitly triggers relayout all the time.
Per CONTRIBUTING.md, you do not accept code contributions at the moment. But, here's a quick fix if it helps anyone:
Branch: https://github.com/ikicic/mistral-vibe/tree/reduce_relayouts
Diff: v2.19.0...ikicic:mistral-vibe:reduce_relayouts
Possibly related to #222.
Reproduction steps
Use the CLI and monitor the CPU usage with top.
Versions / environment
mistral-vibe 2.19.0
Logs & screenshots
Component
CLI
Summary
When using the Vibe CLI, the CPU usage is for no particular reason high when the agent is thinking. It starts okay, but as the history gets longer, the CPU usage gets higher and higher.
The culprits seem to be the animated spinner and the timer, updating 10x and 1x per second, respectively. Even though updating them almost never affects the layout, it implicitly triggers relayout all the time.
Per
CONTRIBUTING.md, you do not accept code contributions at the moment. But, here's a quick fix if it helps anyone:Branch: https://github.com/ikicic/mistral-vibe/tree/reduce_relayouts
Diff: v2.19.0...ikicic:mistral-vibe:reduce_relayouts
Possibly related to #222.
Reproduction steps
Use the CLI and monitor the CPU usage with
top.Versions / environment
mistral-vibe 2.19.0
Logs & screenshots