Resume interrupted work by reviewing recent Screenpipe activity and checking the current state of relevant files, jobs, or services. Recover the last verified result, identify unfinished steps, and avoid repeating actions that may already have completed.
Recover the last verified state of an interrupted task and identify the next useful action.
Review the instructions the agent will receive before you install.
Resolve which task the user wants to resume. Search recent Screenpipe activity with screenpipe-api for that project or artifact, then inspect a small window around the last relevant work.
Recover the objective, last verified result, unfinished step, and any error or pending operation. Check the current file, job, or service before continuing when available; an old screen or chat preview does not establish that a process finished.
Return a brief checkpoint and continue work already authorized by the current request. Avoid repeating external writes that may have completed during the interruption; inspect their receipt or state first. When the next action depends on missing information, state that gap instead of inventing prior intent.
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.
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.