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.
Turn a recorded software failure into a reproducible bug report with timestamps and observed behavior.
Review the instructions the agent will receive before you install.
Resolve the affected app, failure, and approximate time. Use screenpipe-api to inspect the relevant activity and frames; use transcripts only for additional context. Recover the actual sequence before, during, and after the failure.
Write reproduction steps, expected behavior from the user's intent or documented contract, actual behavior, environment/version when verified, and the smallest useful evidence links. Separate visible symptoms from hypotheses about the cause. Mark steps that could not be reproduced.
Remove credentials, unrelated screen content, personal identifiers, and private business metrics from shareable evidence. Do not repeat destructive actions to reproduce the bug. Return a draft report unless issue creation is explicitly authorized.
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.
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.
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.
Find past discussions across existing screenpipe, Codex, Claude, Cursor, and Gemini CLI chats by title, workspace, or message text. With explicit authorization, send follow-up work to a specific supported chat; Gemini CLI supports search only.