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
{{ message }}
Repository navigation
opentui: fatal: undefined is not an object (evaluating 'local.agent.current().name') #10954
TypeError: undefined is not an object (evaluating 'local.agent.current().name')
at <anonymous> (src/cli/cmd/tui/component/prompt/index.tsx:850:75)
at <anonymous> (../../node_modules/.bun/@[email protected]+897ebc1644d3edd0/node_modules/@opentui/solid/index.js:149:62)
at runComputation (../../node_modules/.bun/[email protected]/node_modules/solid-js/dist/dev.js:742:22)
at updateComputation (../../node_modules/.bun/[email protected]/node_modules/solid-js/dist/dev.js:724:3)
at runTop (../../node_modules/.bun/[email protected]/node_modules/solid-js/dist/dev.js:833:7)
at runUserEffects (../../node_modules/.bun/[email protected]/node_modules/solid-js/dist/dev.js:928:18)
at runUpdates (../../node_modules/.bun/[email protected]/node_modules/solid-js/dist/dev.js:849:17)
at completeUpdates (../../node_modules/.bun/[email protected]/node_modules/solid-js/dist/dev.js:900:17)
at runUpdates (../../node_modules/.bun/[email protected]/node_modules/solid-js/dist/dev.js:850:5)
at <anonymous> (src/cli/cmd/tui/context/sync.tsx:262:11)
at processTicksAndRejections (native:7:39)...
클로드코드랑 제미나이 커넥션 연결하려고 하니까 이런 에러가 뜨는데 왜 이러는걸까요?ㅠ
Plugins
No response
OpenCode version
1.1.38
Steps to reproduce
/connect 입력
연결한 api 선택
클로드코드 : 인증 url 접속해서 토큰값 붙여넣고 엔터 / 제미나이 : 인증 url 새탭 자동으로 뜨면 승인 클릭
Both of these issues report the exact same error message that occurs during the connection process. #7918 appears to be the primary tracking issue for this bug with more details and development context.
Feel free to ignore if none of these address your specific case.
Activity
github-actions commentedon Jan 28, 2026
This issue might be a duplicate of existing issues. Please check:
Both of these issues report the exact same error message that occurs during the connection process. #7918 appears to be the primary tracking issue for this bug with more details and development context.
Feel free to ignore if none of these address your specific case.
github-actions commentedon Mar 30, 2026
To stay organized issues are automatically closed after 90 days of no activity. If the issue is still relevant please open a new one.