Observability PII session context

[iamEvanYT]

Improve PostHog observability by adding PII sanitization, session context, comprehensive lifecycle and performance events, and crash reporting, with telemetry disabled in development.

---

  

[cursor]

Cursor Agent can help with this pull request. Just @cursor in comments and I'll start working on changes in this branch.
_{Learn more about Cursor Agents}

[github-actions]

Build artifacts for all platforms are ready! 🚀

Download the artifacts for:

• Linux
• Linux (arm64)
• macOS
• macOS (Intel)
• Windows

One-line installer (Unstable):

bunx flow-debug-build --open 22825931528

(execution 22825931528 / attempt 1)

[greptile-apps]

Greptile Summary

This PR significantly improves the PostHog observability infrastructure by adding PII sanitization via a before_send hook, per-launch session IDs, comprehensive lifecycle/performance event tracking, crash reporting, and gating all telemetry behind app.isPackaged (disabled in dev).

Key changes:

• PII sanitization (sanitize-pii.ts): Redacts URLs, emails, and IPs from all outgoing events via before_send; sensitive keys (e.g. url, token, cookie) are fully redacted; a SAFE_STRING_KEYS allowlist ("version") preserves useful version strings.
• Session context (session.ts): A per-launch crypto.randomUUID() session ID is injected into every event via withContext.
• Observability events (observability.ts): Tab load timing, window/space/profile lifecycle events, update status tracking, and app-ready startup timing. Uses appStartTimestamp = performance.timeOrigin to measure real process-start-to-ready latency.
• Exception autocapture (exception-autocapture.ts): Replaces the custom SDK fork with @posthog/core utilities; adds rate limiting and duplicate-capture prevention.
• Crash reporting: crashReporter.start() annotated with the session ID; child-process and renderer crash events forwarded to PostHog.
• Dev mode gating: The entire PostHog client is skipped when !app.isPackaged, so no events are sent during development.

Issues found:

• In exception-autocapture.ts, the onFatalFn passed to makeUncaughtExceptionHandler is async but called without await, so if client.shutdown() rejects, process.exit(1) is never invoked and the process continues in a post-crash zombie state.

Confidence Score: 2/5

• NOT safe to merge — critical async/await correctness bug in fatal error handler could cause process hang if shutdown fails.
• The PR implements solid observability infrastructure with good PII sanitization and session context. However, exception-autocapture.ts has a critical correctness issue where the async onFatalFn is called without awaiting its Promise, so if client.shutdown() rejects, process.exit(1) is never invoked and the process hangs in a corrupted post-crash state. This is a blocking issue that must be fixed before merge.
• src/main/controllers/posthog-controller/exception-autocapture.ts requires attention for the async/await mismatch in the fatal error handler.

_{Last reviewed commit: 6d2ea49}

[iamEvanYT]

@greptile review