Your AI companion for Ably.

Start realtime debugging with a defined slice of evidence.

Realtime incidents are hard to explain when everyone is looking at a different channel, connection, environment, or time range. “We saw messages stop” can mean many things until the evidence is scoped precisely enough for someone else to reproduce the investigation.

Strawberry can turn the visible Ably console context into a defined evidence record. It can document the relevant channel or connection, time window, observed behaviour, surrounding application context, and missing data without claiming a root cause before the engineering review.

Compare the console with the code path that should explain it.

A dashboard observation is useful only when it is connected to the part of the system that produced it. The problem may sit in client behaviour, authentication, a deploy, a server-side publisher, or assumptions in the application, not necessarily in the realtime platform view alone.

With Ably, repository, logs, and incident materials open, Strawberry can prepare a cross-context investigation map. It can link the observed behaviour to likely code paths and recent changes, while preserving the distinction between a lead and a confirmed causal explanation.

Hand the incident over without losing the engineering thread.

An on-call handover should not force the next engineer to reconstruct the last hour from chat messages and browser tabs. It needs a brief they can trust: what is happening, how wide the impact is, what evidence has been checked, which mitigations were considered, and what decision is now blocked.

Strawberry can assemble that narrative from the visible Ably context and the related incident materials. It helps create a source-linked handoff that names uncertainty honestly and makes the next operator’s entry point concrete.

Build a recurrent health review without turning it into production automation.

Teams often know the questions that indicate realtime risk before a customer reports it: are there unexplained changes in activity, open incidents without an owner, or environment changes that need a human review? A focused periodic check can surface those questions without touching live architecture.

Save the read-only Ably health-review prompt as a Strawberry skill once it captures your operating standard. A routine can prepare the private brief, while configuration changes, key handling, and production responses stay inside an explicit engineering approval flow.

Frequently asked questions