Rasa Tracker Viewer

Dump Rasa's Tracker JSON to visualise it. This tool shows you the tracker in a more readable manner.

It is a fully static, client-side app (no build step, no server). Paste a tracker JSON — from GET /conversations/{id}/tracker, or just the events array — and explore its events as a collapsible timeline. Events are collapsed by default and show the event type + one key parameter (e.g. text for user/bot messages, flow_id for flows, tool_name for MCP tools, name/value for slots). Click any node to expand the full structured fields and raw JSON.

Run locally

Open index.html directly in a browser, or serve the folder:

python3 -m http.server 8000
# then visit http://localhost:8000

Live demo

https://rasahq.github.io/tracker-viewer/ — the page loads a built-in sample tracker automatically.

Sharing

Use the Share button to encode the current tracker directly into the URL as a #t= fragment, so the visualization is fully reproducible from a link (no server, no upload). The payload is minified, then gzip-compressed before base64url encoding, which keeps the URL much shorter than raw JSON.

Open a link with #t=... and the app decodes it automatically and renders the tracker. Plain (uncompressed) #t= links, as well as legacy ?t= query links, are still supported for backwards-compatibility.

Note on very large trackers: the payload lives in the URL fragment (#t=), which is never sent to the server, so the GitHub Pages CDN's 414 URI Too Long limit (which only applies to the request line / query string) no longer applies. Browser address-bar limits are far larger, so trackers up to several tens of kilobytes share fine. For truly enormous trackers, share the JSON file another way (e.g. a gist or pastebin) and paste it into the input panel instead.

Testing the share round-trip

The built-in sample is small, so it makes a short link — click Share, copy the link from the address bar, and open it in a new tab to confirm the tracker re-renders. Repeat against http://localhost:8000 (served above) for a fast local loop without deploying.

Deploy to GitHub Pages

The app is static, so any Pages source works:

1. Push this repo to GitHub.
2. In Settings → Pages, set the source to a branch and the folder that contains index.html (root, /docs, or a subfolder such as tracker-viewer/).
3. The included .nojekyll ensures GitHub does not process the files.

No special configuration is required; everything runs in the browser.

Contribution

Please test your fixes with the trackers listed in sample_trackers directory.