Skip to main content
Screenpipe is useful when research sprawls across browser tabs, PDFs, notes, chats, and calls. It can recover what you viewed and how ideas connected. It cannot prove that every claim on a viewed page is true or still current.

​
Step by step

1

Write the decision question

Start with a question such as “which three vendors meet these requirements?” define the audience, deadline, and evidence standard before searching.
2

Mark the research window

Record the approximate start and end. Use a separate browser profile or window when you need a clean boundary from unrelated browsing.
3

Recover sources

Search the window by browser_url, app name, document title, and key terms. Collect the original URL or file title for every source that may support a material claim.
4

Build a claim table

For each candidate claim, record what was observed, its source, when it was viewed, and whether the source directly supports it. Keep notes and AI inferences separate.
5

Verify outside Screenpipe

Reopen primary sources for prices, product capabilities, laws, schedules, people, and other facts that may have changed. A screen recording proves what you saw, not that the page is current.
6

Write the brief

Summarize the answer, options, tradeoffs, recommendation, contrary evidence, and unknowns. Link each important claim to its original source.
7

Save a reviewable artifact

Store the brief locally or in the approved project repository. Omit private messages and credentials that appeared during the research session.

​
Useful API searches

​
Brief prompt

Do not publish a brief containing current external claims until you have reopened and checked the original sources.