Rekhu Assistant finishes long requests, and tells your users what to do when it cannot

Users ask big things of an assistant: "export the attendance of these 67 children, one file each". An answer like that can reach the length one answer may have. Until now, the assistant then stopped halfway, and because the half-written answer stayed in the conversation, every next message in that chat failed with "The assistant is not available right now".

Rekhu Assistant 0.9.4 for Laravel, 0.6.3 for Node.js and 1.0.5 for Odoo handle this the way it should go.

Long requests carry on

• An answer cut off at its length runs none of its half-written actions. The assistant is told what happened and goes on in smaller steps, in the same turn.
• When the steps of one answer run out, the user reads where it stopped and how to go on: say "continue", or ask for a few at a time.
• One answer may now be 16,000 tokens long instead of 4,000, so most of these requests no longer reach the limit at all. You can still set it lower in the package's settings.

Conversations that broke heal themselves

A conversation stored with an action that never got its result is sent to the model without that action. A chat that broke before the update works again after it, without the user starting over.

Messages your users understand

"Not available" told your users nothing. Now they read what a failure means for them and what to do, in English, Arabic or Dutch:

• Try again in a minute: the model is very busy.
• Let the administrator of this app know: the assistant is paused, at its monthly limit, or its plan needs attention.
• Start a new chat: the conversation could not go on.

The technical reason still goes to your log, for you, never to the user.

Updating

• Laravel: composer update rekhu/assistant-laravel
• Node.js: npm install @rekhu/assistant-node@latest
• Odoo: update Rekhu Assistant from its branch for your Odoo version, then upgrade the module under Apps.

Read more on the Rekhu Assistant page.