Error appear after connecting provider #7791

Closed
opened 2026-02-16 18:08:14 -05:00 by yindo · 10 comments
Owner

Originally created by @abbaspuzi on GitHub (Jan 27, 2026).

Originally assigned to: @kommander on GitHub.

Description

This error message appear after successful connected to provider

[12:02:30] [LOG] 'resolveSystemTheme'
[12:02:30] [LOG] '{"type":"home"}'
[12:02:30] [LOG] [
      '#1d1f21', '#cc6666',
      '#b5bd68', '#f0c674',
      '#81a2be', '#b294bb',
      '#8abeb7', '#c5c8c6',
      '#666666', '#d54e53',
      '#b9ca4a', '#e7c547',
      '#7aa6da', '#c397d8',
      '#70c0b1', '#eaeaea'
    ]
[12:05:44] [LOG] 'bootstrapping'
[12:05:44] [LOG] 'bootstrapping'
[12:05:44] [LOG] 'bootstrapping'
[12:05:44] [ERROR] Error: EditBuffer is destroyed
    Error: EditBuffer is destroyed
        at guard (../../node_modules/.bun/@opentui+core@0.1.75+81ecd8642a1892ca/node_modules/@opentui/core/index.js:332:17)
        at getText (../../node_modules/.bun/@opentui+core@0.1.75+81ecd8642a1892ca/node_modules/@opentui/core/index.js:371:10)
        at focus (../../node_modules/.bun/@opentui+core@0.1.75+81ecd8642a1892ca/node_modules/@opentui/core/index.js:6744:32)

Plugins

No response

OpenCode version

1.1.37

Steps to reproduce

  1. Connect provider
  2. Select kimi code
  3. Put API key

Screenshot and/or share link

Image

Operating System

macOS 15.7.3

Terminal

Ghostty

Originally created by @abbaspuzi on GitHub (Jan 27, 2026). Originally assigned to: @kommander on GitHub. ### Description This error message appear after successful connected to provider ``` [12:02:30] [LOG] 'resolveSystemTheme' [12:02:30] [LOG] '{"type":"home"}' [12:02:30] [LOG] [ '#1d1f21', '#cc6666', '#b5bd68', '#f0c674', '#81a2be', '#b294bb', '#8abeb7', '#c5c8c6', '#666666', '#d54e53', '#b9ca4a', '#e7c547', '#7aa6da', '#c397d8', '#70c0b1', '#eaeaea' ] [12:05:44] [LOG] 'bootstrapping' [12:05:44] [LOG] 'bootstrapping' [12:05:44] [LOG] 'bootstrapping' [12:05:44] [ERROR] Error: EditBuffer is destroyed Error: EditBuffer is destroyed at guard (../../node_modules/.bun/@opentui+core@0.1.75+81ecd8642a1892ca/node_modules/@opentui/core/index.js:332:17) at getText (../../node_modules/.bun/@opentui+core@0.1.75+81ecd8642a1892ca/node_modules/@opentui/core/index.js:371:10) at focus (../../node_modules/.bun/@opentui+core@0.1.75+81ecd8642a1892ca/node_modules/@opentui/core/index.js:6744:32) ``` ### Plugins _No response_ ### OpenCode version 1.1.37 ### Steps to reproduce 1. Connect provider 2. Select kimi code 3. Put API key ### Screenshot and/or share link <img width="1912" height="1154" alt="Image" src="https://github.com/user-attachments/assets/50584f68-456a-4e83-a5a6-53933d927310" /> ### Operating System macOS 15.7.3 ### Terminal Ghostty
yindo added the opentuibug labels 2026-02-16 18:08:14 -05:00
yindo closed this issue 2026-02-16 18:08:14 -05:00
Author
Owner

@github-actions[bot] commented on GitHub (Jan 27, 2026):

This issue might be a duplicate of existing issues. Please check:

  • #10807: opentui: fatal: undefined is not an object (evaluating 'local.agent.current().name') - Occurs after /connect and provider setup with Synthetic provider
  • #7918: Crash when local.agent.current() returns undefined during startup/auth - Similar crash pattern during provider authentication

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.

@github-actions[bot] commented on GitHub (Jan 27, 2026): This issue might be a duplicate of existing issues. Please check: - #10807: opentui: fatal: undefined is not an object (evaluating 'local.agent.current().name') - Occurs after /connect and provider setup with Synthetic provider - #7918: Crash when local.agent.current() returns undefined during startup/auth - Similar crash pattern during provider authentication 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.
Author
Owner

@lordcris commented on GitHub (Jan 27, 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

@lordcris commented on GitHub (Jan 27, 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
Author
Owner

@Foovar commented on GitHub (Jan 28, 2026):

I can reproduce this as well.

Environment

  • OS: macOS 26.2 (build 25C56)
  • Terminal: iTerm2
  • OpenCode: v1.1.37

Steps

  1. Connect provider
  2. Select any provider
  3. Enter API key

Result
After the provider connects successfully, the app intermittently crashes with:
Error: EditBuffer is destroyed (during bootstrapping → focus).

@Foovar commented on GitHub (Jan 28, 2026): I can reproduce this as well. **Environment** * OS: macOS 26.2 (build 25C56) * Terminal: iTerm2 * OpenCode: v1.1.37 **Steps** 1. Connect provider 2. Select any provider 3. Enter API key **Result** After the provider connects successfully, the app intermittently crashes with: `Error: EditBuffer is destroyed` (during bootstrapping → focus).
Author
Owner

@tx-anin commented on GitHub (Jan 28, 2026):

Image
@tx-anin commented on GitHub (Jan 28, 2026): <img width="1147" height="519" alt="Image" src="https://github.com/user-attachments/assets/6730212f-7d7e-426b-9398-991efb6b524b" />
Author
Owner

@unfazed2049 commented on GitHub (Jan 28, 2026):

the same problem

@unfazed2049 commented on GitHub (Jan 28, 2026): the same problem
Author
Owner

@cravenceiling commented on GitHub (Jan 28, 2026):

Downgrading to v.1.1.36 fix this issue for the moment.

opencode upgrade 1.1.36
@cravenceiling commented on GitHub (Jan 28, 2026): Downgrading to `v.1.1.36` fix this issue for the moment. ```bash opencode upgrade 1.1.36 ```
Author
Owner

@huanyang1120 commented on GitHub (Jan 28, 2026):

same issue in opencode 1.1.39

@huanyang1120 commented on GitHub (Jan 28, 2026): same issue in opencode 1.1.39
Author
Owner

@buxiua commented on GitHub (Jan 28, 2026):

same issue in opencode 1.1.40

@buxiua commented on GitHub (Jan 28, 2026): same issue in opencode 1.1.40
Author
Owner

@kommander commented on GitHub (Jan 29, 2026):

Should be fixed in v1.1.42

@kommander commented on GitHub (Jan 29, 2026): Should be fixed in v1.1.42
Author
Owner

@okbrown commented on GitHub (Jan 29, 2026):

Same issue on v1.1.42 😢

@okbrown commented on GitHub (Jan 29, 2026): Same issue on v1.1.42 😢
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: anomalyco/opencode#7791