Trailframe
SUPPORT & FAQ
Help with workflow documentation, onboarding, QA, bug reports and handovers.
Open an HTTP(S) website, click Trailframe, enter a workflow name and goal, then Start. Perform the task in that tab. Add notes to explain decisions. Stop & save, enter the observed outcome, review the evidence and choose Download full workflow.
Version 2.0.2 fixes a library communication error in version 2.0.1. For an unpacked installation, update the files in the same folder, click Reload for Trailframe on chrome://extensions, then refresh the library tab. Keep the existing installation to retain its local recordings. Open the saved workflow and try the export again.
Start before the reproduction steps. Add the expected and actual results in Workflow details, inspect failed or slow calls, and include the relevant notes. Review and remove sensitive evidence before attaching the archive or individual exports to your support ticket.
Record a complete example of the procedure. Add notes explaining choices and exceptions. The full ZIP keeps technical evidence together; the Markdown flow documents make recorded steps easier to read. Edit or expand the procedure for your audience after reviewing what was observed.
No. It captures visible page states and viewport screenshot checkpoints. It does not record continuous video, audio or the whole desktop.
The debugger permission lets Trailframe observe the chosen tab's network, page and console evidence. Capture starts only after Start. Stop detaches it. Closing Chrome's banner interrupts the recording.
Some evidence is intentionally excluded or unavailable from Chrome. Known private fields, credentials and query values are redacted. XML, HTML, scripts, binary and oversized bodies are omitted. Inspect Coverage and the request's body state for the reason.
No. Recognised private fields and iframe areas are masked, but other personal information or business data may remain. Review every part and its images before sharing. You can remove an unsafe screenshot from the library.
Trailframe divides longer recordings into storage parts. Browse them in the library. Download full workflow includes every part. Individual diagnostic exports describe only the selected part.
In the current Chrome profile's local IndexedDB. There is no recording server or automatic upload. Completed unpinned recordings expire after 30 days while the extension runs. Pin or export recordings you need to keep. Downloaded files remain until you delete them separately.
No. Recorder exports are candidates for reviewed scripts and require replacement of placeholders. AI handovers are reference evidence; the receiving system controls its learning and retention. Do not replay production writes without separate authorisation.
Review the interruption and coverage notes. Export available evidence before deleting anything. Browser quotas, the twelve-hour or approximate 256 MiB stored-evidence budget, and local library limits may stop capture. Start a continuation recording for longer work.
Version 2.1 adds lossless compression for ZIP exports and new local records. Workday screenshot pace is at most once every 30 seconds when the page changes; choose 5, 1.5 or 90 seconds if appropriate. Actions and visible page states are captured between pictures. Images are at most 1600 pixels wide. Capture is limited to 12 hours and storage budgets, so a busy page may require a continuation. The popup shows saved size. Pause for breaks and review Coverage for gaps. Chrome must remain open and awake.
Update the same unpacked folder and Reload to keep your library. Version 2.1 reads older recordings; older versions cannot read new compressed local records, so export before a downgrade.
Include Trailframe and Chrome versions, a short description, the expected and actual result, and steps that reproduce the issue. Prefer a disposable test page and minimal redacted evidence. Never send passwords, tokens, customer records or an entire private recording without review.