Reconstruct an incident timeline from recorded screens and conversations, supported by available logs and monitoring. Organize symptoms, changes, response actions, and recovery evidence while distinguishing observed facts from suspected causes.
Reconstruct a bounded incident timeline and separate observed events from suspected causes.
Review the instructions the agent will receive before you install.
Resolve the incident, affected system, and time window. Use screenpipe-api to recover relevant screens and conversations, then corroborate with available logs, monitoring, and service receipts. Normalize timestamps to one stated timezone while retaining source timestamps where needed.
List the first observed symptom, material changes, actions taken, and recovery evidence in chronological order. Distinguish when an event happened from when someone reported it. Label causal explanations as hypotheses unless directly established.
State the last verified condition and remaining uncertainty. An error disappearing from a screen does not prove recovery; cite a successful relevant operation or current health evidence. Propose follow-up investigation within scope. Do not restart services, roll back changes, or notify others without authorization.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Develop and test Windows-specific Screenpipe changes on a disposable Azure virtual machine. The workflow verifies native behavior, preserves logs and desktop video, and handles branch and pull request delivery when authorized.
Prepare screenpipe component releases by updating versions and dependency lock files, running required build checks, and triggering GitHub Actions. Verify build results and release artifacts, then hand public app publication over to a person.
Create charts, dashboards, scorecards, and styled summaries as standalone HTML reports for the screenpipe viewer. Keep styles, scripts, and images inside the file so the report renders in a sandbox with no network access.
Use Screenpipe’s local REST API, an interface for programmatic requests, to search screen and meeting history, review app activity and active time, retrieve synced-device records, export recordings, and rerun audio transcription.
Search Screenpipe recordings, screen text, audio transcripts, and synced-device history through its local API. Use the evidence to review activity, find meeting details, and inspect saved workflows, including recorded steps that can inform automation.
Turn a recorded software failure into a draft bug report with timestamps, reproduction steps, expected and actual behavior, and relevant evidence. Separate visible symptoms from possible causes and remove sensitive details from shareable evidence.