feat(agentStudio): surface service errors deep thread

[pipeline1987]

Summary

Surfaces conversation and transport errors end-to-end in the InstantSearch chat stack (ai-lite → connector → widgets → UI), so failures from the assistant thread are visible in the chat UI instead of failing silently or only in logs.

How

• ai-lite (abstract-chat, transport, stream parser, utils)

  • Stronger error handling for requests and streaming (including normalized error text where relevant).
  • Ensures error objects are cloned when updating state so React/connectors don’t skip re-renders when only the error message or reference semantics would look “unchanged”.

• connectChat + chat widget

  • Wires error-related state through the connector render state so vanilla and React consumers get the same behavior.

• UI (instantsearch-ui-components)

  • Chat surfaces errors in the message list and header where appropriate (Chat, ChatMessages, ChatMessageError, ChatHeader, layouts, icons).
  • Shared chat utilities and types updated to support error display and behavior.

• Styling (instantsearch.css)

  • Styles for the error message/header treatment (including theme/reset hooks as needed).

• React (react-instantsearch)

  • useConnector + dequal adjustments so connector updates (including errors) propagate reliably to components.

• Tests

  • Coverage across ai-lite, connector, UI utils, and chat components; common widget tests updated where translations/options changed.

• Example

  • Small tweak in examples/react/e-commerce/App.tsx aligned with the new behavior.

Result

• thread depth

• max iterations

• max tokens

[codacy-production]

Up to standards ✅

🟢 Issues 0 issues

Results:
0 new issues

View in Codacy

🟢 Metrics 107 complexity · 52 duplication

Metric	Results
Complexity	107
Duplication	52

View in Codacy

_{TIP This summary will be updated as you push new changes. Give us feedback}

[pkg-pr-new]

More templates

• example-instantsearch-getting-started
• example-react-instantsearch-getting-started
• example-react-instantsearch-next-app-dir-example
• example-react-instantsearch-next-routing-example
• example-vue-instantsearch-getting-started

algoliasearch-helper

npm i https://pkg.pr.new/algolia/instantsearch/algoliasearch-helper@6983

instantsearch-ui-components

npm i https://pkg.pr.new/algolia/instantsearch/instantsearch-ui-components@6983

instantsearch.css

npm i https://pkg.pr.new/algolia/instantsearch/instantsearch.css@6983

instantsearch.js

npm i https://pkg.pr.new/algolia/instantsearch/instantsearch.js@6983

react-instantsearch

npm i https://pkg.pr.new/algolia/instantsearch/react-instantsearch@6983

react-instantsearch-core

npm i https://pkg.pr.new/algolia/instantsearch/react-instantsearch-core@6983

react-instantsearch-nextjs

npm i https://pkg.pr.new/algolia/instantsearch/react-instantsearch-nextjs@6983

react-instantsearch-router-nextjs

npm i https://pkg.pr.new/algolia/instantsearch/react-instantsearch-router-nextjs@6983

vue-instantsearch

npm i https://pkg.pr.new/algolia/instantsearch/vue-instantsearch@6983

commit: 59f37b8

[Haroenv]

could you split this up please?

[Haroenv]

is there some way to implement this without the deep changes in useConnector? as I believe there's no other widgets with id, normally if widgets change attributes (similar to id?) they just get deleted and re-added

[pipeline1987]

could you split this up please?

fs, I've split this in two pieces

#6991
#6992