NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
pub.dev
Algo Widget for Flutter — in-app bug reporting with screen recording, voice narration, a recorded interaction trace, and automatic crash capture.
Last release 1 months ago
10 Aug 2026
Too new to tell
only 1 release windows
Some releases are documented
notes for 4 of 7 stable releases
Nothing withdrawn
no release was ever pulled
1 months old
7 releases · first in 2026
One column per month.
flutter: Attach opened nothing on Android
Nothing published for this version
Nothing published for this version
a client that cannot screenshot must say so
flutter: publish the bridge fix — 0.1.3 never left the runner
Nothing published for this version
First release. Everything from the wire protocol up to a one-call AlgoWidget.init(...) , tested without a device.
First release. Everything from the wire protocol up to a one-call
AlgoWidget.init(...), tested without a device.
Protocol — the session exchange that replaces the browser's Origin
header on a native client: name the app, get a challenge, come back with a
platform attestation minted against it. A 401 carrying a challenge is step
one, not an error.
TraceRecorder — the interaction trace. Head+tail retention (setup and
failure survive; a ring buffer keeps only the failure), a media-time clock
that does not accumulate a gap across pause, the element identity ladder, and
the redaction rules: a request path never carries a query string, and there is
no code path that reads a field's value.
CrashReporter — per-launch, per-route and per-signature throttles,
persistence across the dying process, and a signature that separates the same
error on two screens while grouping one bug with its own repeats.
Bindings — a fetch interceptor (recording FAILED requests only), a
console capture that records an argument's SHAPE rather than its contents,
ErrorUtils and unhandled-rejection handlers, and a navigation tracker that
takes a route name so it works with React Navigation, Expo Router or a
hand-rolled stack. Each chains rather than replaces — an app with Crashlytics
keeps it — and restores exactly what it found.
Frame bridge — the report panel is the same page the web widget serves, in
a WebView. An unrecognised message is ignored rather than fatal, because the
panel and the SDK version independently.
AlgoWidgetPanel (from @algosoftltd/algo-widget-react-native/panel) — the
report panel in a WebView, loading the same page the web widget serves. Behind
a subpath so an app that builds its own report UI never pulls in React or
react-native-webview.
Not in this release: the native capture layer (screen, voice, screenshot). Its
contract is defined (NativeCapture) and the Kotlin and Swift cores exist, but
no module is registered yet — so a panel offers steps only until you supply an
implementation. Everything else works today.
Your coding agent can read these notes before it upgrades. Set up the MCP server →