What shipped, and when.
Changes to Cluebase itself.
The dashboard, the widget, alerting and billing.
The widget gets a face, and better answers
- The widget now introduces itself. It shows an assistant name and says plainly that it is an AI, so nobody is left wondering whether a person is typing.
- Header colour and assistant name are yours to set in the widget editor, alongside the colours that were already there.
- The first message is shorter and asks one question. When the error is clear enough to name, it asks you to confirm what you were doing, which takes a word to answer.
- Suggestions for what to try while you wait are now built from what actually failed and what the person said they were doing, instead of a generic list that fitted any error on any site.
- The assistant no longer tells people it does not know what happened. It says less when it knows less, rather than narrating the gap.
Cluebase is live
- Public launch. Sign up, create a project, and drop its publishable key into your app.
- The rescue widget explains an error to the person who hit it, in plain language, while it is happening.
- Errors, incidents and analysis for your team, with alerts over email, Slack and Telegram.
- Widget editor, team access, usage and billing all live in the dashboard.
cluebase-next and cluebase-react.
Published to npm. Anything listed here reaches your app only once you install it.
- 1.0.1
A redesigned widget, and quiet on dropped connections
- A visitor losing wifi no longer starts conversations. Failed requests are only reported when they come from your own origins, aborted and page-navigation requests are ignored, and a burst of failures collapses into one report instead of one per request.
- trackedOrigins on CluebaseProvider, for when your API lives on a different subdomain to your app. Same-origin requests are tracked by default, so most apps need nothing.
- The widget has been rebuilt: a branded header carrying the assistant name, a larger panel, and support links moved up next to the name.
- The widget now opens in light mode by default, and follows the host page when it is set to match.
- Without CLUEBASE_SECRET_KEY, register and onRequestError returned silently: the build passed, the hooks ran, and nothing was ever reported or heartbeated. They now log a one-time warning on the server so a half-finished setup says so instead of looking healthy.
- 1.0.0
cluebase-next and cluebase-react reach 1.0.0
- Both packages are now on 1.0.0. From here the version number tells you what an update will do: nothing breaks unless the first number changes.
- No changes to the public API. The same imports, the same props, the same provider setup.
- Update with npm install cluebase-next@latest or npm install cluebase-react@latest.