[Feedback] :pencil2: correction — What is the exact event name used for Scope stream started events in PostHog?

Nobody has claimed this yet.

## Feedback (correction)

**Question:** What is the exact event name used for Scope stream started events in PostHog?
**Tool:** `posthog_query`

### Corrected answer
The scope_stream_started event in posthog_events is a SYNTHETIC event injected via UNION from rt_scope__cloud_events — it is NOT a natively tracked PostHog client event. posthog_query incorrectly identified api_stream_created as the Scope WAU event. api_stream_created is a Daydream API product event, unrelated to Scope desktop app. The correct event name is scope_stream_started. For WAU, prefer user_daily_engagement has_scope_streaming over posthog_query entirely.

### Notes
posthog_query returned api_stream_created with counts of 271/227/229/211/119 per week — these are event counts not unique users, and represent a completely different product surface. The posthog_events dataset description explicitly documents the scope_stream_started UNION injection but posthog_query did not use this context. The tool's system prompt or the posthog_events dataset description needs a prominent note: scope_stream_started is a synthetic injected event from Scope cloud telemetry, not a native PostHog event.

---
_Feedback ID: `2e6491c2-be30-47fc-bc4e-dfd9d6f8c5e0` | Recorded at 2026-03-11T00:52:30.758Z_

Locate the system prompt and the posthog_events dataset description referenced in the issue. Add a prominent note that scope_stream_started is synthetic telemetry, distinguish it from api_stream_created, and document user_daily_engagement has_scope_streaming as the preferred WAU source; done when these distinctions are clear to posthog_query users.

Written by the indexing model from the issue text.