Align inbox & scout copy with self-driving docs vocabulary - #3968
Merged
Conversation
The mobile inbox fell back to "Untitled signal" for reports with no title, but the object is a report — the desktop app and mobile's own TinderView already say "Untitled report". Aligns the four remaining spots. Generated-By: PostHog Code Task-Id: c095eab9-ff75-4110-8b4f-d29ca1bd95da
|
😎 Merged successfully - details. |
|
React Doctor found no issues in the changed files. 🎉 Reviewed by React Doctor for commit |
Renames user-facing display strings to the canonical docs terms: "finding" → "signal" (scout emissions and report evidence), "Responder" → "agent" (the investigating agent), "skill" → "scout" (scout tooltips/labels), and "inbox item" → "report". Updates the inbox CLAUDE.md naming convention to match. Backend API fields, deep links, analytics event names, and type names are unchanged. Generated-By: PostHog Code Task-Id: c095eab9-ff75-4110-8b4f-d29ca1bd95da
joshsny
changed the title
The header link opens cloudSkillUrl (analytics action open_skill_in_posthog), i.e. it opens the scout's underlying skill in PostHog. Since scouts are driven by skills, this keeps saying "View skill" rather than "View scout". Generated-By: PostHog Code Task-Id: c095eab9-ff75-4110-8b4f-d29ca1bd95da
Contributor
|
✅ Visual changes approved by @joshsny — baseline updated in 6 changed, 2 removed. |
Same as the detail header: the row card's link opens cloudSkillUrl (analytics action open_skill_in_posthog), i.e. it opens the scout's underlying skill in PostHog, so it keeps saying "View skill" rather than "View scout". Generated-By: PostHog Code Task-Id: c095eab9-ff75-4110-8b4f-d29ca1bd95da
joshsny
marked this pull request as ready for review
July 30, 2026 14:05
6 updated, 2 removed Run: 0f4f68f5-b48d-46c9-a6b3-61363fe55ea6 Co-authored-by: joshsny <7135900+joshsny@users.noreply.github.com>
Contributor
|
Reviews (1): Last reviewed commit: "Keep "skill" wording for the scout row c..." | Re-trigger Greptile |
andrewm4894
approved these changes
Jul 30, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
The self-driving docs on posthog.com define the canonical user-facing vocabulary — signal, report, scout, signal source, inbox, self-driving. Several inbox and scout surfaces in the desktop/mobile app used different words for the same concepts, so a user moving between the docs, the web app, and PostHog Desktop would see the terminology shift under them.
Surfaced from a naming-consistency audit across the posthog.com docs, PostHog/posthog, and this repo (Slack thread).
Changes
User-facing display strings only — aligned to the docs vocabulary:
packages/ui/src/features/inbox/CLAUDE.mdso the naming convention matches the docs (this previously mandated "finding"/"Responder").Backend endpoints, shared API fields, TypeScript types, deep-link params, and analytics event/property names are intentionally left on the legacy
signals/findingnaming — only human-visible copy changed.How did you test this?
Copy-only string edits (no identifier or contract changes). Verified via diff review and grep that no analytics values, API fields, deep links, or type names were touched, and that no test assertions reference the changed strings. I (the agent) did not run the app or a full typecheck.
Automatic notifications
Created with PostHog from a Slack thread