← knowledge.oriz.in

Screenpipe upstream contribution burst 2026-07-03

decision screenpipeupstreamcontributionreview

Screenpipe upstream burst — 2026-07-03

Session summary

Two grill-me waves ran comprehensive audits against screenpipe/screenpipe (fast-moving Rust+Tauri monorepo, 2000+ upstream stars). Fork stayed byte-clean per no-fork-divergence. All 37 contributions filed atomically from chirag127/<branch> heads against upstream/main.

Wave 1 — reactive (user hit onboarding stuck)

Root cause: SAP CPIT DLP intercepts WebView2 → localhost:3030 from the same Tauri process (curl works from outside, webview does not).

7 PRs:

4 issues:

Wave 2 — proactive comprehensive review

Six parallel subagents (UX/perf/security/architecture + deep-research + live-metrics extraction from user's own running engine).

Deep-research findings (4 axes, sourced 2026-07): Tauri v2 patterns, screen-recording competitors 2026, MCP spec 2026-07-28 RC (breaking), Rust pipeline patterns.

Live metrics from user's 3h session: OCR cache 0% hits, 33% empty transcriptions, 1.5GB app RAM, 100%+ single-core CPU sustained.

12 more PRs:

14 more issues:

Discipline maintained

Every contribution:

Parallel-agent turbulence

7+ concurrent subagents on same submodule caused branch clobbering / stash races. Recovered every commit via git reflog + push-by-SHA. Never used git reset --hard on fork state. Lesson: --isolation worktree for parallel fork work. One subagent (architecture review) used worktree correctly at repos/frk/screenpipe-review-arch/ — cleaned up post-run.

Cross-refs

Follow-up if any land

If maintainer merges > 60% of PRs, this session becomes a case study for the fork-thin-upstream-tracking + audit-loop pattern. Track merge rate over next 30 days.