Teknium 6e46f99e7e fix(tui): surface backend error as visible text when final_response is empty (#21245) ...

When the provider rejects a request (e.g. invalid model slug like
'--provider nous --model kimi-k2.6' where the valid slug is
'moonshotai/kimi-k2.6'), run_conversation() returns
{failed: True, error: <detail>, final_response: None}. The TUI gateway
and one-shot CLI mode both dropped the error on the floor and emitted
an empty turn, so the user saw a blank response with no indication
that anything went wrong.

Mirror the interactive CLI's existing pattern (cli.py:9832): when
final_response is empty AND (failed|partial) is set AND error is
populated, surface 'Error: <detail>' as the visible text. Leaves
the None-with-no-error path and the '(empty)' sentinel path
untouched — an empty successful turn still renders empty, and
existing sentinel handlers keep owning their lane.

Reported by @counterposition in PR #20873; taking a minimal fix
rather than the broader structured-failure refactor proposed there.

2026-05-07 05:53:19 -07:00

..

__init__.py

feat: new tui based on ink

2026-04-02 19:07:53 -05:00

entry.py

fix(tui_gateway): guard sys.path against local package shadowing (#15989)

2026-05-04 12:42:43 -07:00

event_publisher.py

chore: address copilot comments

2026-04-24 12:51:04 -04:00

render.py

tui: inherit Python-side rendering via gateway bridge

2026-04-05 18:50:41 -05:00

server.py

fix(tui): surface backend error as visible text when final_response is empty (#21245)

2026-05-07 05:53:19 -07:00

slash_worker.py

feat: personality

2026-04-08 00:15:15 -04:00

transport.py

fix(tui-gateway): harden stdio transport against half-closed pipes + SIGTERM races (#17118)

2026-04-28 17:54:06 -05:00

ws.py

feat(web): add /api/pty WebSocket bridge to embed TUI in dashboard

2026-04-24 10:51:49 -04:00