Fix issue with large error msgs

[tomsmith8]

Cap excessive error message size in Agent logs

Issue:
Agent updates are currently producing extremely large error messages, particularly in cases such as login failures or ontology mismatches. These logs include full serialized JSON responses and internal states, resulting in:

• Bloated and unreadable log output (see screenshot).
• Poor developer experience when debugging.
• Potential UI performance issues due to oversized log payloads.

Screenshot Example:

Proposed Solution:

• Introduce a character or payload size cap for error logs shown in the Agent update panel.
• Display a truncated version of long logs by default, with an optional “View full details” toggle or expandable section.
• Ensure critical information remains visible (e.g., top-level error message, query input, tool name).

---

Acceptance Criteria:

• Logs exceeding the defined cap are trimmed with an ellipsis and/or "Show more" control.
• Key debugging data is preserved in the initial view.
• Log display no longer causes horizontal scroll or layout issues in the UI.
• Performance remains stable regardless of error log size.

---

[Ekep-Obasi]

@tomsmith8 please assign me

[aliraza556]

@tomsmith8 Please assign me

[evilfps]

I can take this one.

Plan is to cap long Agent error logs in the UI, keep the useful first part visible, and add a simple show more option so the layout doesnt break on huge payloads.

I am a student and this bounty would help me, so I will keep the patch small and easy to review.

[evilfps]

Opened PR #1577 for this: #1577

It caps long log entries in the UI, keeps full details behind a toggle, and leaves copy-to-clipboard using the full log output. I did not run local tests, kept it scoped to the log viewer.

[sureshchouksey8]

Opened PR #1579 for this: #1579

This version specifically addresses the performance issue from the closed attempt: the collapsed log row does not build the full pretty JSON string before truncating. It slices event.raw directly for the preview, preserves top-level debugging fields, and only builds full JSON when the user expands a row or copies logs.

[chfr19820610-cell]

Subject: Bounty Application – Fix issue with large error msgs (#1444)

Hi, I’d like to take on this task. I have strong experience with TypeScript and React frontend development, including handling large JSON payloads and optimizing log output. I can implement a clean cap on error message size while preserving essential debugging info. I expect to complete this within 2–3 days after being assigned.