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
Both issues show crashes during provider connection/authentication flows with similar error patterns in the OpenTUI component. The "EditBuffer is destroyed" error combined with the timeline (bootstrapping → focus → error) suggests a TUI state management issue during provider setup.
Feel free to ignore if your case involves different steps or specific Kimi provider configuration.
Activity
github-actions commentedon Jan 28, 2026
This issue might be a duplicate of existing issues. Please check:
Both issues show crashes during provider connection/authentication flows with similar error patterns in the OpenTUI component. The "EditBuffer is destroyed" error combined with the timeline (bootstrapping → focus → error) suggests a TUI state management issue during provider setup.
Feel free to ignore if your case involves different steps or specific Kimi provider configuration.
lordcris commentedon Jan 28, 2026
i have this issues too.
I am on
Distributor ID: Linuxmint
Description: Linux Mint 22.3
Release: 22.3
Codename: zena
on the normal terminal it works, on ghostty i see this error
Foovar commentedon Jan 28, 2026
I can reproduce this as well.
Environment
Steps
Result
After the provider connects successfully, the app intermittently crashes with:
Error: EditBuffer is destroyed(during bootstrapping → focus).tx-anin commentedon Jan 28, 2026
[-]Random error appear after connecting provider[/-][+]Error appear after connecting provider[/+]unfazed2049 commentedon Jan 28, 2026
the same problem
cravenceiling commentedon Jan 28, 2026
Downgrading to
v.1.1.36fix this issue for the moment.huanyang1120 commentedon Jan 29, 2026
same issue in opencode 1.1.39
buxiua commentedon Jan 29, 2026
same issue in opencode 1.1.40
kommander commentedon Jan 29, 2026
Should be fixed in v1.1.42
okbrown commentedon Jan 29, 2026
Same issue on v1.1.42 😢