You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 9995b96
Browse filesBrowse the repository at this point in the historyBrowse files
Required mostly for metrics so we can track its usage accurately rather
than bundled in with the existing "Ask AI" integration.
(Googlers: see the attached bug for a link to the backend CL, this needs
to land first before this can land).
Bug: 406795908
Change-Id: Ibf0fff042f72a6e622e9d9d9e87769a71feb23af
Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/6407494
Reviewed-by: Nikolay Vitkov <nvitkov@chromium.org>
Commit-Queue: Jack Franklin <jacktfranklin@chromium.org>
thrownewError('Failed to generate AI entry label');
266
-
}
267
258
}
268
-
269
-
constAI_LABEL_GENERATION_PROMPT=`## Instruction:
270
-
Generate a concise label (max 60 chars, single line) describing the *user-visible effect* of the selected call tree's activity, based solely on the provided call tree data.
271
-
272
-
## Strict Constraints:
273
-
- Output must be a single line of text.
274
-
- Maximum 60 characters.
275
-
- No full stops.
276
-
- Focus on user impact, not internal operations.
277
-
- Do not include the name of the selected event.
278
-
- Do not make assumptions about when the activity happened.
279
-
- Base the description only on the information present within the call tree data.
280
-
- Prioritize brevity.
281
-
- Only include third-party script names if their identification is highly confident.
282
-
- Always use "responsiveness" rather than "user interaction responsiveness".
thrownewError('Failed to generate AI entry label');
25
+
}
26
+
}
27
+
28
+
constAI_LABEL_GENERATION_PROMPT=`## Instruction:
29
+
Generate a concise label (max 60 chars, single line) describing the *user-visible effect* of the selected call tree's activity, based solely on the provided call tree data.
30
+
31
+
## Strict Constraints:
32
+
- Output must be a single line of text.
33
+
- Maximum 60 characters.
34
+
- No full stops.
35
+
- Focus on user impact, not internal operations.
36
+
- Do not include the name of the selected event.
37
+
- Do not make assumptions about when the activity happened.
38
+
- Base the description only on the information present within the call tree data.
39
+
- Prioritize brevity.
40
+
- Only include third-party script names if their identification is highly confident.
41
+
- Always use "responsiveness" rather than "user interaction responsiveness".
0 commit comments