Trailframe – Workflow Recorder & Bug Reports

Record browser workflows, screenshots and network activity for SOPs, onboarding, QA and clearer bug reports.

Trailframe records browser workflows so you can document procedures, explain bugs and hand over work with useful context. Capture one chosen tab's actions, field changes, visible page states, screenshot checkpoints and network activity. Add a goal, explain decisions with notes, record the outcome and export a clearly named workflow package. USE TRAILFRAME FOR • Process documentation and SOPs: record a real task, then use the action timeline, notes and Markdown exports to explain the procedure. • Employee and customer onboarding: show how a browser-based process works and preserve the steps for later reference. • Bug reports and support handovers: keep reproduction steps, screenshots, console errors and relevant network requests together. • Manual QA and regression checks: document what you tested, the expected result and what actually happened. • API and web-app troubleshooting: inspect request/response evidence, failed or slow calls, redirects and readable stream messages. • Team and client handovers: share the task's goal, sequence, decisions and observed outcome in one package. • Process improvement: review repeated steps, interruptions and browser-visible results before changing a workflow. • AI-assisted documentation and automation planning: supply recorded evidence to an AI so it can help describe the procedure or draft a reviewed automation plan. WHAT YOU CAN CAPTURE • Clicks, typed changes, selections, checkboxes, submissions, scrolling and selected navigation keys, with timestamps and selectors. • Structured visible page states and automatic viewport screenshot checkpoints. • Network request/response metadata, redacted readable JSON, text, CSV, form and GraphQL bodies, plus readable WebSocket and server-sent messages. • Console text, warnings, errors, navigation, notes and download-response metadata. REVIEW AND EXPORT Search your local library, browse recording parts, inspect failed or slow requests, review screenshots, add workflow details and remove unsafe images. Download one workflow ZIP containing all recorded parts, a chronological timeline, coverage report, page states, images, HAR files, Recorder JSON and Markdown documents. The filename includes the workflow name, website, UTC start time and a unique ID. Individual-part exports are also available. LOCAL BY DEFAULT No account is required to use Trailframe. Recordings stay in your Chrome profile until you choose to export or share them. There is no recording server, analytics or automatic upload. Workflow mode includes non-private values, readable bodies, page states and screenshot checkpoints by default. Diagnostics mode offers lighter capture. Recognised passwords, secrets, authentication headers, private fields and URL query values are excluded or redacted. Screenshots mask recognised private fields and iframe areas. Other sensitive business data may remain: review every export before sharing. KNOW THE BOUNDARIES Trailframe records one HTTP(S) tab at a time. Other tabs and popup windows are excluded. Frame and dedicated-worker observation is best effort. Screenshots are checkpoints, not video. File contents, audio, hidden server state, XML, HTML, script and binary bodies are excluded. Lossless ZIP and local-storage compression keep repetitive evidence smaller. Workday screenshot pace defaults to at most once every 30 seconds when the page changes; choose 1.5, 5 or 90 seconds instead. Actions and visible page states are captured between pictures. Images are at most 1600 pixels wide, with up to 500 checkpoints including the final state. Limits include twelve hours or approximately 256 MiB of stored evidence per workflow and 512 KiB per readable body. Chrome must remain open and awake. Busy pages and browser storage quotas may stop capture sooner; use a continuation recording when needed. The coverage report identifies gaps and unavailable evidence. Trailframe does not automatically replay actions, submit business transactions or train an AI model. Recorder exports need review and replacement of placeholders before use. Request/action links are temporal associations, not proof of causation. Chrome 125 or later is required. Chrome displays a debugging banner while recording. Trailframe is currently a preview release.