Skip to main content
screenpipe records screen and audio while it is running, then makes that local history available to AI. start with one useful output, verify the source data, and expand only after you trust it.

​
for consultants and customer work

track client time

reconstruct reviewed work blocks and active-time totals without automatic billing

write a weekly client report

combine work, deliverables, decisions, risks, and next steps into one update

turn meetings into follow-up

verify the transcript, then draft decisions and action items

prepare a CRM update

extract reviewed deal fields without auto-writing guesses into the CRM

​
for focused individual work

review your day

remember accomplishments, blockers, and open loops

turn browsing into a brief

recover sources you viewed and build a checked research summary

remember relationship context

prepare a private follow-up queue from meetings and messages

give an AI local memory

maintain a small, reviewed context file across agent sessions

​
for operations and engineering

discover repetitive work

find one repeated workflow worth improving

capture an SOP

turn one clean process run into a tested operating guide

reconstruct an incident

build a fact, inference, and unknown timeline from a bounded window

monitor one narrow surface

watch an approved app, window, or website and report a clear no-data state

​
the safe workflow

1

set the boundary

Decide which apps, windows, websites, people, and hours belong in the workflow. add exclusions before recording client, employee, financial, health, or personal information.
2

verify recording

Complete a short test, then search for something you can see or hear. a blank result is a capture problem or a no-data state—not permission for the AI to guess.
3

run it manually

Use a current Home shortcut, install a pipe from Pipes → Discover, or describe a custom automation under Pipes → My Pipes → create your own pipe. run it manually before adding a schedule.
4

inspect the output

Check time totals, names, decisions, and source moments. keep uncertain items marked as uncertain.
5

automate only the stable part

Schedule local drafts after several good manual runs. require review before sending messages, editing a CRM, billing a client, or changing another system.

​
rules that keep outputs trustworthy

  • use /activity-summary for active-time totals; do not infer hours by counting frames, OCR rows, or search results
  • give broad /search requests a time boundary
  • distinguish no matching data from the activity did not happen
  • keep source apps, meetings, URLs, or time ranges when a report may be reviewed later
  • treat AI project labels, workflow names, and suggested next steps as suggestions
  • verify current external facts from their original source before publishing a research brief
  • review any external side effect before it happens
protected local API endpoints require a bearer token when API authentication is enabled. retrieve it with npx -y screenpipe@latest auth token or from Settings → Privacy → API security, then follow API recipes.

​
start small

for personal use, begin with daily work review. for a customer or team pilot, use one person, one workflow, one to two weeks, and one agreed output. this makes privacy, accuracy, and value easier to evaluate before expanding.