pod
Other formats agents might prefer:
markdownjsonllms.txt

Agent? You probably want markdown or json, or Pod over MCP.

Reported issues for screenpipe

Pod holds 21 of 29 problems reported by people outside the maintainer team. Issues filed by the project's own owners, members and collaborators are excluded entirely — a maintainer's release checklist is not a warning to a prospective user.

Back to screenpipe.

Most discussed

meta: 19 open PRs from chirag127 — batch review request + offer consolidated PR

Hi @louis030195 and @codenamejason,

Filed 19 PRs over two sessions (2026-07-03) covering CI, perf, a11y, docs, UX, security, and analytics opt-out. All branch off upstream/main, ≤5 files each, tests pass locally.

PR list by category

CI / build (3)

  • #4831 parameterize ONNXRUNTIME_VERSION
  • #4853 concurrency group on sdk.yml
  • #4857 tsconfig noFallthroughCasesInSwitch

Onboarding / UX (4)

  • #4851 detect 401 on live-feed polls, show actionable copy
  • #4852 SCREENPIPE_SKIP_ONBOARDIN

Read the thread · 2026-07-03 · closed · outside contributor · 3 comments

Wrong pipe name recorded in execution database

Description

When running a pipe via the UI, the execution record in the database is recorded with an incorrect pipe name. The chat title shows the correct pipe name, but the execution database record shows a different pipe's name.

Steps to Reproduce

  1. Run the automation-roi pipe from the UI (POST /pipes/automation-roi/run)
  2. Check the execution details in the chat interface
  3. The execution record shows pipe_name = "action-item-reconciler-v2-full-improved" instead of `"automation-

Read the thread · 2026-06-07 · closed · external user · 4 comments

Add Custom MCP Connections When Creating Or Configuring A Pipe

Description

Add an option to connect a custom MCP server from the connections list when creating or configuring a pipe.

Reason

This would make pipes more flexible by allowing users to connect their own MCP tools, data sources, and workflows directly inside Screenpipe.

Read the thread · 2026-05-26 · closed · external user · 1 comment

Day Recap / Pi AI fails with all tested local Ollama models (mistral, qwen3, qwen3.5) — tool calling not reliable enough

Summary

The Day Recap feature on the Home tab returns hallucinated or empty summaries when used with any local Ollama model I tested. The model seems to never actually call the Screenpipe tools (search-content, activity-summary, etc.) and instead reasons in circles before concluding "no data found" or inventing fake content.

The same query against the same data produces a perfect, accurate summary when used via Claude Desktop with the Screenpipe MCP server, which proves the data and th

Read the thread · 2026-04-29 · closed · external user · 1 comment

Search API returns near-duplicate OCR results, wasting LLM context

Problem

When an LLM agent queries GET /search?content_type=ocr&start_time=...&limit=N, it receives many near-identical OCR text entries that differ only by minor rendering artifacts (cursor blink, anti-aliasing, slight scroll). This wastes LLM context window on redundant information.

Example: querying a 15-minute window while the user was in a terminal returned 81 OCR results. The top 5 were nearly identical:

frame 16225 | 23:16:00 | "copy OCR text fails on deduplicated frames" x Bas

[Read the thread](https://github.com/screenpipe/screenpipe/issues/2285) · 2026-02-22 · closed · external user · 3 comments

### [bounty] Moving from supabase to s3

@neo773 

let's migrate plugin storage to s3, i did supabase s3 implementation (https://github.com/mediar-ai/screenpipe/pull/1553) but same issue with supabase, so now we've decided to move to s3 with our own account

we basically need to set up:
- publishing workflow in cli
- update backend route for publishing (different repo)
- update routes related to other storage operations: e.g. downloading, checking for updates, etc.
- migrate existing plugins there

[Read the thread](https://github.com/screenpipe/screenpipe/issues/1558) · 2025-03-06 · closed · external user · 7 comments

### [bounty] [pipe] [developer program] daily/weekly activity summary

[please read the developer program description https://github.com/mediar-ai/screenpipe/issues/1184]

* implement tools for time tracking and productivity analysis.  

suggest other ideas, send us your plan, write comments, give feedback

[Read the thread](https://github.com/screenpipe/screenpipe/issues/1190) · 2025-01-22 · closed · external user · 12 comments

### [feature] Make screenpipe able to use the computer

**describe the feature**
Same as computer use from https://www.anthropic.com/news/3-5-models-and-computer-use

**why is this needed?**
Why would computer users do things on computers if they can just ask the AI to do it?

**alternatives considered**
Integrate with the lower level APIs of every possible app. This is a much harder problem.

[Read the thread](https://github.com/screenpipe/screenpipe/issues/567) · 2024-10-22 · closed · external user · 8 comments

## Most recent

### [feature] add new meeting provider - read.ai

**describe the feature**
Add new meeting  provider.

**why is this needed?**
This is a popular provider.

- https://support.read.ai/hc/en-us/articles/49381161088659-API-Reference
- https://support.read.ai/hc/en-us/articles/49379985941523-Read-AI-API-and-MCP-Overview
- https://www.read.ai/integrations

[Read the thread](https://github.com/screenpipe/screenpipe/issues/5791) · 2026-08-03 · closed · outside contributor · 0 comments

### [feature] list Migma.ai under Communication connections

## What is Migma.ai?

Migma.ai is an email campaign platform for creating branded emails, managing opted-in audiences, sending or scheduling campaigns, and reading delivery and campaign results.

Could Migma.ai be listed in **Settings → Connections → Communication**?

```text
Communication
┌────────────────────────────────────────────────────────────┐
│ Migma.ai                                                   │
│ Create, send, schedule, and track email campaigns.     [+] │
└───────────────────

[Read the thread](https://github.com/screenpipe/screenpipe/issues/5748) · 2026-08-01 · closed · external user · 0 comments

### security: SecretStore falls back to base64 (effectively plaintext) when encryptStore is off

## Context

`crates/screenpipe-secrets/src/store.rs::SecretStore::set` stores secrets as base64 with a zero nonce when no keychain-derived encryption key is available:

```rust
None => {
    // No encryption key — store as base64 with zero nonce
    let encoded = BASE64.encode(value).into_bytes();
    (encoded, vec![0u8; 12])
}

The gate is is_encryption_requested — reads .encrypt-store flag file OR store.bin magic OR settings.encryptStore == true in store.bin JSON (`crates/screenp

Read the thread · 2026-07-03 · closed · outside contributor · 1 comment

onboarding: streaming summary catch swallows network errors on corp-restricted networks

Symptom

Onboarding streams a fetch summary from a model endpoint at components/onboarding/engine-startup.tsx:529-549. On corp-restricted networks (DLP, DNS filtering, cert pinning failure), the fetch fails and the block only logs ${resp.status} — no user-visible message, and the onboarding screen keeps showing the "settling in…" pulse.

The fallback timer eventually flips the screen to the local prose, but between fetch failure and fallback expiry, the user has no signal that anything wen

Read the thread · 2026-07-03 · closed · outside contributor · 1 comment

MCP: track 2026-07-28 stateless-spec RC + migrate reads to Resources

MCP spec 2026-07-28 RC is a breaking change

packages/screenpipe-mcp/package.json:34 pins @modelcontextprotocol/sdk ^1.27.1 which implements spec 2025-11-25 (stateful, initialize/initialized handshake, Mcp-Session-Id header).

The 2026-07-28 RC (blog.modelcontextprotocol.io 2026-05-21, verified 2026-06-03 in H1 state summary) is stateless:

  • initialize/initialized removed
  • Mcp-Session-Id heade

Read the thread · 2026-07-03 · closed · outside contributor · 1 comment

[feature] auto audio-device handling WITH a blocklist (skip bluetooth mic inputs to preserve A2DP)

describe the feature

keep screenpipe's automatic audio-device handling, but let me layer a blocklist on top of it. one mode: auto-discover and record inputs as they connect/disconnect, minus a small persistent set of devices to never open.

the specific need is bluetooth microphone inputs. A2DP (the high-quality listening profile) is output-only; the moment macOS opens a bluetooth headset's mic for capture, the OS downgrades the whole device from A2DP to HFP/SCO and audio qualit

Read the thread · 2026-06-10 · closed · outside contributor · 0 comments

[bug] pipes cannot authenticate to github — oauth connection exposes no token

describe the bug the github connection is OAuth-connected and shows as "connected" in the app, but neither a pipe runtime nor the local API can retrieve a usable token, so pipes cannot create github issues/comments.

steps:

  1. connect github via the OAuth flow (shows "connected").
  2. from a pipe (or via the local API) try to read the connection: GET http://localhost:3030/connections/github returns {"credentials":{}} — no access token.
  3. token endpoints like /connections/github/token,

Read the thread · 2026-06-10 · closed · outside contributor · 1 comment

macOS: closing the lid permanently kills System Audio capture — no recovery, no error, health reports ok (mic unaffected); CoreAudio tap immune

Summary

On macOS, closing the MacBook lid (clamshell, external display stays active) instantly and permanently kills the System Audio (output) capture stream. It does not recover when the lid is reopened — even when system audio is actively playing afterward. Microphone capture survives the same event without interruption.

The failure is completely silent:

  • No error or warning is logged when the output stream dies
  • [DEVICE_RECOVERY] never fires for the output device (it watchdogs th

Read the thread · 2026-06-08 · closed · external user · 1 comment

[bug] GitHub connection proxy returns 403 — User-Agent not forwarded/accepted by GitHub

Bug

The GitHub connection proxy (GET/POST http://localhost:3030/connections/github/proxy/...) returns 403 Forbidden on every request. The response body is GitHub's own error:

Request forbidden by administrative rules. Please make sure your request has a User-Agent header.

This happens even when the client sets an explicit User-Agent header, which suggests the proxy is stripping or overriding it with a value GitHub's API rejects. GitHub requires a valid User-Agent on all REST API

Read the thread · 2026-05-31 · closed · outside contributor · 0 comments

[bug] owned-default /eval endpoint silently no-ops — returns success:true but JS does not execute against page

describe the bug

The POST /connections/browsers/owned-default/eval endpoint reports success but the supplied JS does not actually run against the page document. The same JS works correctly against user-browser/eval.

This breaks the documented "escape hatch when navigate + snapshot aren't enough" use case for the owned webview, and silently — there's no error to catch.

to reproduce

# 1. load a real page in owned-default
curl -sH "Authorization: Bearer $SCREENPIPE_LOCAL_API

[Read the thread](https://github.com/screenpipe/screenpipe/issues/3676) · 2026-05-28 · closed · outside contributor · 0 comments

### [feature] built-in pipe to file github bug reports & feature requests with full diagnostic artifacts

**describe the feature**

a first-party screenpipe pipe (or built-in app action) that turns any crash, quirk, or "i wish it did X" moment into a properly-formatted github issue on `screenpipe/screenpipe` — without the user ever leaving the app or having to remember to do it later.

concretely:

- **trigger surfaces**
  - "report a bug" / "suggest a feature" menu items in the tray + settings
  - auto-prompt on detected crash (parse the latest `~/Library/Logs/DiagnosticReports/screenpipe-app-*.ips

[Read the thread](https://github.com/screenpipe/screenpipe/issues/3674) · 2026-05-28 · closed · outside contributor · 1 comment

### [feature] Cross-reference version schemes across app, CLI, MCP, and cloud — five separate numbers today with no canonical view

## The problem

A single Screenpipe install on macOS exposes **five different version schemes**, with no canonical place that ties them together:

| Surface | Where it's shown | Example (my install, 2026-05-21) |
|---|---|---|
| Tauri app version | `Info.plist`, About dialog | `2.4.247` |
| Engine / CLI binary | `screenpipe --version` | `0.3.307` |
| `screenpipe-mcp` npm package | `npx screenpipe-mcp@latest` | `0.18.2` |
| `@screenpipe/cli-darwin-arm64` npm shim | npm dist tag | `0.1.0` |
| Clou

[Read the thread](https://github.com/screenpipe/screenpipe/issues/3500) · 2026-05-21 · closed · outside contributor · 1 comment

### [bug] screenpipe-mcp-http package doesn't exist

**describe the bug**
screenpipe-mcp-http doesn't exist

**system info**
- os: Tahoe 26.4.1 (25E253)
- screenpipe version: screenpipe-app-v2.4.210

**additional context**

➜ npx screenpipe-mcp-http --listen-on-lan --api-key $(openssl rand -hex 16) npm error code E404 npm error 404 Not Found - GET https://registry.npmjs.org/screenpipe-mcp-http - Not found npm error 404 npm error 404 The requested resource 'screenpipe-mcp-http@*' could not be found or you do not have permission to access it. np

Read the thread · 2026-05-21 · closed · outside contributor · 0 comments

The remaining reports are on the project's issue tracker.