exo-explore/exo · error · ValueError
{error_message}
Error message
{error_message} What it means
Error "{error_message}" thrown in exo-explore/exo.
Source
Thrown at src/exo/api/adapters/responses.py:445
for tool in chunk.tool_calls:
function_call_items.append(
ResponseFunctionCallItem(
id=tool.id,
call_id=tool.id,
name=tool.name,
arguments=tool.arguments,
)
)
continue
if chunk.is_thinking:
thinking_parts.append(chunk.text)
continue
accumulated_text += chunk.text
if error_message is not None:
raise ValueError(error_message)
# Create usage from usage data if available
usage = _build_response_usage(last_usage) if last_usage is not None else None
output: list[ResponseItem] = []
if thinking_parts:
output.append(
ResponseReasoningItem(
id=reasoning_id,
summary=[ResponseReasoningSummaryText(text="".join(thinking_parts))],
)
)
output.append(
ResponseMessageItem(
id=item_id,
content=[ResponseOutputText(text=accumulated_text)],
status="completed",
)View on GitHub (pinned to 21a54c5ea0)
When it happens
Trigger: Thrown at src/exo/api/adapters/responses.py:445 when the library encounters an invalid state.
Common situations: See trigger scenarios.
AI-assisted analysis of exo-explore/exo@21a54c5ea0 (2026-08-26).
Data as JSON: /api/errors/7e7d25b25a37abad.
Report an issue: GitHub.