fix(tui): handle undefined agent.current() to prevent fatal TypeError #7689
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Fixes the fatal error:
TypeError: undefined is not an object (evaluating 'local.agent.current().name')Root Cause
When the agents list is empty or the stored agent name doesn't match any available agent,
local.agent.current()returnsundefined. The code then crashes when accessing.nameonundefined.Affected locations:
packages/opencode/src/cli/cmd/tui/context/local.tsx- Source of the issuepackages/opencode/src/cli/cmd/tui/component/prompt/index.tsx- 6 consumer locationspackages/opencode/src/cli/cmd/tui/component/dialog-agent.tsx- 1 consumer locationChanges
local.tsxagents()[0].name→agents()[0]?.name ?? ""for safe initialization!fromcurrent()returnagent.current()prompt/index.tsx"build"fallback at all 6 locations:dialog-agent.tsxTesting
The fix adds defensive null checks that gracefully handle edge cases without changing normal behavior when agents are properly loaded.