LLM Client call error

[aneeshjain5]

Type: Bug

Internal server error: Tool error: LLM Client call error: Event stream error: Transport error: error decoding response body.

We'd appreciate it if you could report this session using the feedback tool above - this is on us. Please try again.

Aide version: Aide 1.96.4 (4e858de632a2bb7407167560cbe824397e95fa4a, 2025-01-31T18:48:20.686Z)
OS version: Windows_NT x64 10.0.19045
Modes:

System Info

Item	Value
CPUs	Intel(R) Core(TM) i5-4200U CPU @ 1.60GHz (4 x 2295)
GPU Status	2d_canvas: enabled canvas_oop_rasterization: enabled_on direct_rendering_display_compositor: disabled_off_ok gpu_compositing: enabled multiple_raster_threads: enabled_on opengl: enabled_on rasterization: enabled raw_draw: disabled_off_ok skia_graphite: disabled_off video_decode: enabled video_encode: unavailable_off vulkan: disabled_off webgl: enabled webgl2: enabled webgpu: enabled webnn: disabled_off
Load (avg)	undefined
Memory (System)	5.88GB (0.64GB free)
Process Argv
Screen Reader	no
VM	0%

Extensions (10)

Extension	Author (truncated)	Version
pdf-viewer	ada	1.1.2
path-intellisense	chr	2.8.0
vscode-eslint	dba	3.0.10
prettier-vscode	esb	11.0.0
path-autocomplete	ion	1.25.0
blockman	leo	1.7.8
material-icon-theme	PKi	5.19.0
JavaScriptSnippets	xab	1.8.0
five-server	yan	0.3.2
markdown-all-in-one	yzh	3.6.2

[theskcd]

ACK, on it!

[theskcd]

I'll analyze the MCTS data and create a concise PR message based on the changes made.

🐛 Fixed: Improved error handling for LLM client response issues

• Added: Specific error handling for "Transport error: error decoding response body" with user-friendly message
• Enhanced: User experience by providing clear reporting instructions and explaining that it's a system issue

The fix targets a specific error case in the AideAgentSessionProvider while ensuring variations of the error message are properly caught. Ready for review!