Review a specific meeting’s notes and transcript to summarize decisions, commitments, named owners, and stated deadlines. Keep proposals and completed work separate, flag recording gaps, and draft a concise follow-up message when requested.
Capture decisions and commitments after a meeting and draft a concise follow-up.
Review the instructions the agent will receive before you install.
Identify the exact meeting and inspect its note or bounded transcript using screenpipe-api. Keep stated intent, agreed work, and completed work separate. Notes may mix a preparation agenda, generated summary, and older material. Confirm decisions and commitments against the selected meeting's transcript; label anything supported only by the agenda as a proposal. Check speaker identity before assigning an owner, and count repeated audio captures as one utterance. Write the outcome, decisions, owners, due dates explicitly mentioned, and open questions. Do not invent owners or dates. Include a source link and flag gaps in recording. Draft a short follow-up when requested. Check the user’s current casing and punctuation preferences. Sending, updating external systems, or creating calendar events requires the user’s explicit request.
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.