Review selected meeting and conversation history to identify explicit promises and deadlines, then check later evidence to distinguish open, completed, superseded, and uncertain commitments while keeping tentative ideas separate.
Find explicit promises and deadlines in selected work history and reconcile their latest status.
Review the instructions the agent will receive before you install.
Resolve the person or project and review period. Use screenpipe-api to retrieve relevant meetings and conversations. Extract explicit commitments with the original speaker, action, date wording, and source; keep tentative ideas separate.
Search for later updates or completion evidence for each commitment. Verify current connected records when available, and report unchecked channels. A drafted message is not sent, a planned meeting is not held, and an opened ticket is not resolved.
Present confirmed open, completed, superseded, and uncertain items. Resolve relative deadlines using the source's date and timezone, retaining ambiguity. Prioritize by stated deadlines and dependencies. Do not contact people, create reminders, or edit task systems unless covered by the user's request or standing instructions.
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.