> ## Documentation Index
> Fetch the complete documentation index at: https://docs.screenpipe.com/llms.txt
> Use this file to discover all available pages before exploring further.

# turn browser research into a checked brief

> Recover pages, documents, and questions from a bounded research session, then create a concise brief that preserves sources and uncertainty.

{/* https://screenpi.pe */}

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.

```mermaid theme={null}
flowchart TD
    A["research question"] --> B["bounded pages and notes"]
    B --> C["claims linked to original sources"]
    C --> D["fact and freshness check"]
    D --> E["reviewed brief"]
```

## step by step

<Steps>
  <Step title="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.
  </Step>

  <Step title="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.
  </Step>

  <Step title="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.
  </Step>

  <Step title="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.
  </Step>

  <Step title="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.
  </Step>

  <Step title="write the brief">
    Summarize the answer, options, tradeoffs, recommendation, contrary evidence, and unknowns. link each important claim to its original source.
  </Step>

  <Step title="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.
  </Step>
</Steps>

## useful API searches

```bash theme={null}
export SCREENPIPE_API_KEY="$(npx -y screenpipe@latest auth token)"

curl -H "Authorization: Bearer $SCREENPIPE_API_KEY" \
  "http://localhost:3030/search?browser_url=github.com&start_time=3h+ago&end_time=now&limit=50"

curl -H "Authorization: Bearer $SCREENPIPE_API_KEY" \
  "http://localhost:3030/search?q=vendor-or-topic&content_type=all&start_time=3h+ago&end_time=now&limit=50"
```

## brief prompt

```markdown theme={null}
Create a research brief from these bounded screenpipe results.

Include:
- decision question and scope
- candidate answer
- source table: claim, original URL or document, observed time, support level
- options and tradeoffs
- contrary evidence and unknowns
- facts that require a current primary-source check
- recommendation, clearly labeled as analysis

Do not treat a viewed page as verified truth.
Do not invent missing URLs or source details.
Exclude unrelated private activity.
```

<Warning>
  do not publish a brief containing current external claims until you have reopened and checked the original sources.
</Warning>