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') #8405
TypeError: undefined is not an object (evaluating 'local.agent.current().name')
at <anonymous> (src/cli/cmd/tui/component/prompt/index.tsx:840:75)
at <anonymous> (../../node_modules/.bun/@opentui+solid@0.1.72+897ebc1644d3edd0/node_modules/@opentui/solid/index.js:148:62)
at runComputation (../../node_modules/.bun/solid-js@1.9.10/node_modules/solid-js/dist/dev.js:742:22)
at updateComputation (../../node_modules/.bun/solid-js@1.9.10/node_modules/solid-js/dist/dev.js:724:3)
at runTop (../../node_modules/.bun/solid-js@1.9.10/node_modules/solid-js/dist/dev.js:833:7)
at runUserEffects (../../node_modules/.bun/solid-js@1.9.10/node_modules/solid-js/dist/dev.js:928:18)
at runUpdates (../../node_modules/.bun/solid-js@1.9.10/node_modules/solid-js/dist/dev.js:849:17)
at completeUpdates (../../node_modules/.bun/solid-js@1.9.10/node_modules/solid-js/dist/dev.js:900:17)
at runUpdates (../../node_modules/.bun/solid-js@1.9.10/node_modules/solid-js/dist/dev.js:850:5)
at setStore (../../node_modules/.bun/solid-js@1.9.10/node_modules/solid-js/store/dist/dev.js:221:5)
at processTicksAndRejections (native:7:39)...
Both have the exact same error message, same file location (src/cli/cmd/tui/component/prompt/index.tsx:840:75), and identical stack traces. Feel free to ignore if this addresses your specific case, otherwise this appears to be the same underlying bug across multiple reports.
Activity
github-actions commentedon Jan 14, 2026
This issue might be a duplicate of existing issues. Please check:
Both have the exact same error message, same file location (src/cli/cmd/tui/component/prompt/index.tsx:840:75), and identical stack traces. Feel free to ignore if this addresses your specific case, otherwise this appears to be the same underlying bug across multiple reports.