Describe Your Changes

This PR lets the frontend control the inference engine directly. It helps manage logic before UX constraints, making the user experience smoother without waiting for events later on.

Currently:
Event-Driven:

graph TD;
    A[Chat Shell] -->|broadcast events| B[Extensions];
    B -->|broadcast events| A;

Pros:

• Easily adaptable to different frameworks and languages.
• Components communicate through events, enabling easier maintenance and updates.
• Extensions can own their logic controllers, allowing for customization.

Cons:

• Managing event subscriptions across components can be challenging.
• Introducing events may complicate state management.
• Handling events in frontend applications can add complexity.
• App lacks awareness of available inference engines, potentially resulting in timeouts.
• Inability to implement pre-processing UX constraints until extension broadcasts event messages.
• Can't be directly used by other extensions or tools

Updated:
Direct Request (Engine Provider):

graph TD;
    A[Inference Extensions] --> |register engines| CoreSDK
    C[Chat Shell] -->|imports|CoreSDK
    Extensions -->|imports|CoreSDK
    CoreSDK --> |uses| Engines;
    Engines -->|inference| Outputs;

Pros:

• Frontend has direct control over the logic flow.
• Avoids overhead of event handling.
• Simpler to scale in smaller systems.
• App now possesses knowledge of all installed inference engines.
• Easy to add UX constraints before inference.
• Able to be imported and used from other extensions/tools

Cons:

• May restrict extension of functionalities.
• Components are tightly coupled, reducing adaptability.
• May pose challenges as system complexity grows.

The core package has been restructured to accommodate compatibility with both browser and Node.js environments. It now includes two main directories:

• browser: Contains modules optimized for web browsers, with the main entry point defined in browser/index.ts.
• node: Houses modules tailored for Node.js, with the main entry point defined in node/index.ts.

Fixes Issues

• epic: Refactor Inference Engines #2451

Self Checklist

• Refactor sendMessageRequest to use MessageRequestBuilder refactor: introduce message request builder #2481
• Refactor assistant's tools to register the tool instead of intercepting message requests

graph TD;
    A[Chat Shell] -->|broadcast events| B[Assistant Extension];
    B -->|broadcast events| C[Inference Extension] -->|broadcast events| A;

->

graph TD;
    AssistantExtension --> |registers Tools| CoreSDK;
    App --> |imports| CoreSDK;
    Extension --> |imports| CoreSDK;
    CoreSDK --> |uses| Tools;
    Tools --> |inference|Engines