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
When LiteLLM or a custom function fails, Agent.generate_response() returns strings such as [Error: ...] or [Timeout Error: ...]. cli.py prints these as normal agent dialogue (colored name + content).
Users cannot distinguish a failed inference from in-character speech, and there is no in-session guidance (retry turn, skip agent, check model/API key, increase timeout).
Proposed Solution
Detect error/timeout prefixes in the session loop (small helper, e.g. is_inference_failure(content)).
Render a distinct Rich panel (not agent voice): model id, failure type, and hints (Ollama down, wrong tag, API key, raise defaults.timeout in settings).
Raise exceptions and crash the session — rejected; too brittle for long multi-agent runs.
Log errors only to stderr — rejected; misses the primary UX surface (terminal).
Priority
High 🔴
Additional Context
Works with timeouts already on main and with future #8 retries (retry in agent, clear UI in CLI). Not a duplicate of #23 (Skillware/tools). Consider doing after or in parallel with preflight (#2 above).
Problem Statement
When LiteLLM or a custom function fails,
Agent.generate_response()returns strings such as[Error: ...]or[Timeout Error: ...].cli.pyprints these as normal agent dialogue (colored name + content).Users cannot distinguish a failed inference from in-character speech, and there is no in-session guidance (retry turn, skip agent, check model/API key, increase timeout).
Proposed Solution
is_inference_failure(content)).defaults.timeoutin settings).Session.generate_next_turnor agent responses.Alternatives Considered
retry_countinagent.py— rejected; users still see opaque error text as dialogue if all retries fail.Priority
High 🔴
Additional Context
Works with timeouts already on
mainand with future #8 retries (retry in agent, clear UI in CLI). Not a duplicate of #23 (Skillware/tools). Consider doing after or in parallel with preflight (#2 above).