Errors happen.Confusion should not.
Everything Cluebase does, in the order you meet it. The story is on the home page; this is the list.
At the moment it breaks
What the person using your product actually experiences.
- Survives the page failing
- Built to keep working when the app around it has already stopped, which is the only moment it matters.
- Loads only on an error
- Nothing sits on your page waiting. The error is what summons the agent, so a healthy session costs nothing.
- Explains in plain words
- Names the concrete thing that broke and what is not lost. Technical detail stays in the dashboard.
- Never invents an explanation
- When it does not know the cause it says something true and small instead of guessing.
- Asks one thing at a time
- It gathers what the team needs through conversation rather than presenting a bug report form.
- Closing it loses nothing
- The conversation finishes in the background and can be reopened. The report still arrives.
What your team receives
The handover, delivered where the team already works.
- The full transcript
- Every word exchanged, so you always know exactly what a user was told.
- Who it affected
- Contact details when the user chooses to share them, captured in their own words.
- Outcome and severity
- Saved, at risk or lost for the person; P0 to P3 for the error. Two scales, kept separate.
- Slack, Telegram and email
- The incident lands in the channel your team already has open.
- Roles
- Admins and members. Everyone reads incidents; only admins change who else can.
What you learn from it
The data no other error tool has, because no other tool asks.
- Recovery rate
- Counted from real outcomes rather than modelled, so it moves when your answers get better.
- Severity against outcome
- A P0 people survived and a P3 that lost someone are different days. Both are recorded.
- Affected users, by name
- A list of people to follow up with, not a count of events to triage.
- Retention you control
- On every plan, with deletion on request.
What it takes to install
One provider, one key.
- Next.js and React
- cluebase-next and cluebase-react, shipping today.
- Vue, Svelte and vanilla JS
- Not shipped yet. On the way.
- Wrap once
- A provider at the root of the app and a key from the dashboard. No per-route wiring.
- Your agent, your name
- Choose the name and look your users see, so it reads as part of your product.
- Light and dark
- The widget renders inside your product, so it matches whichever background it lands on.