Find repeated tasks in recorded activity or starred examples, then describe their steps, exceptions, and human decisions. Assess a small automation candidate using captured evidence, available tools, permissions, and clear completion criteria.
Identify repeated work from recorded activity or starred examples and assess which steps could be automated.
Review the instructions the agent will receive before you install.
Resolve the work area and review period. Use screenpipe-api to find multiple distinct occurrences of a candidate workflow. Describe the trigger, inputs, observed steps, outputs, exceptions, and human decisions with source pointers.
Count independent occurrences, not repeated frames or repeated discussion of one occurrence. Separate observed steps from inferred steps. If timing matters, use authoritative active time where available and label missing coverage; frame counts are not effort.
Assess a small automation candidate by its available tools, permissions, reversible boundaries, and observable completion criterion. Identify the decisions that still require a person. Do not claim time savings without a baseline or create a schedule, integration, or external action merely from discovering a pattern.
For starred work, retrieve captured evidence directly with screenpipe-api's starred-only search and a bounded time range. For broader workflow review, use the activity summary's starred intervals to prioritize existing evidence; retrieve missing steps only when needed. A star indicates intent, not repetition, completion or time savings. Do not add interval history to standing prompts.
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.