screenpipe

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.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Test Windows-specific capture and permission behavior
• Investigate compiler, process, or service issues
• Preserve desktop video and logs for a pull request

Turn selected Screenpipe activity into a concise recap for a defined audience. Summarize outcomes from recorded evidence, then review the draft to remove identifying details, private links, sensitive amounts, and unnecessary personal information before sharing.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Prepare a public recap of selected work
• Create a progress summary with fewer identifying details
• Remove private details from an activity-based draft

Search team activity in Screenpipe Enterprise and review records by device and time. Preview, deploy, and schedule managed Pipes, which are AI automations, with explicit targets and checks before changes.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Find team activity related to a topic
• Review a teammate's activity timeline
• Preview and deploy a managed Pipe

Investigate and maintain documented workflows using Screenpipe evidence and shared drafts. Review whether recorded actions support each procedure, preserve verified steps, and add timing measurements only when clear start and end evidence is available.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Checking documented procedures against activity records
• Reviewing and handing off shared workflow drafts
• Investigating workflow and step durations

Find facts, relevant examples, and prior wording in work history to support a writing draft. Use source evidence to separate completed work from plans and opinions, verify quotations, and remove sensitive details from public drafts unless disclosure is authorized.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Draft a report grounded in work history
• Find concrete examples for an article
• Reuse prior wording while preserving personal voice

Operate Screenpipe from the terminal to set up continuous recording, check capture health, and search local history. Manage Pipes, scheduled AI automations, and configure and test connections to external services.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Set up continuous screen and audio recording
• Diagnose recording and storage issues
• Search recorded screen and audio history

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.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Preparing a desktop app release
• Checking whether Rust changes require a CLI release
• Updating MCP versions and checking publication

Draft a project status report against stated milestones using recent Screenpipe activity and verified outcomes. Separate work performed from delivered and accepted results, summarize blockers and next actions, and cite dated sources with verification limits.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Drafting a project report against stated milestones
• Checking delivery claims against current records
• Summarizing blockers and the next decision

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.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Finding recurring tasks in activity records
• Reviewing starred examples for workflow patterns
• Assessing a small automation candidate

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.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Drafting a bug report from recorded activity
• Recovering steps taken before and after a failure
• Comparing expected behavior with observed results