feat(init): track completion-screen actions in run telemetry - #1534
Merged
Conversation
The completion screen lets users open Sentry (issues / first event) or install the Sentry agent plugin, but neither click emitted any telemetry, so we had no idea how many people take either action. Tag the run's `cli.command` transaction on interaction: - `wizard.completion.opened_sentry` — opened issues/first event - `wizard.completion.agent_plugin_clicked` — chose to install the plugin - `wizard.completion.agent_plugin_installed` — installer actually ran on exit Tags are bound in InkUI (main bundle) via a new `track` action so the Ink sidecar never imports the Sentry SDK, matching the existing `openUrl` pattern. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
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
1 participant
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.
Summary
On the init completion screen you can open Sentry (issues / first event) or install the Sentry agent plugin. Neither click emitted any telemetry, so we couldn't tell how many people actually take either action — the buttons just called
openUrl/ queued a shell command with nothing landing in traces.This adds tags on the run's
cli.commandtransaction when the user interacts with the completion screen.Changes
New
trackaction onCompletionActions, bound inInkUI(main bundle) so the pre-bundled Ink sidecar never has to import the Sentry SDK — same pattern already used foropenUrl. The click handlers inink-app.tsxcall it, and the tags land on the activecli.commandtransaction alongside the rest of thewizard.*tags.Tags:
wizard.completion.opened_sentry— opened the Issues feed / first event (menu item or theoshortcut)wizard.completion.agent_plugin_clicked— chose to install the agent plugin (sticky: un-toggling still counts the click)wizard.completion.agent_plugin_installed— the installer actually ran on exitclickedvsinstalledis intentional so we can see the funnel (chose to install vs. actually ran).Not segmenting by framework here — just raw counts.
Test Plan
tsc --noEmitcleanbiome checkclean on changed filesvitest runon the completion-screen snapshot suite — 40/40 passExample query once this ships (project
cli):transaction:cli.command wizard.completion.agent_plugin_clicked:true