Skip to content
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 8 additions & 4 deletions selectors.json
Original file line number Diff line number Diff line change
@@ -1,13 +1,16 @@
{
"version": "0.3.6",
"lastVerified": "2026-04-11",
"version": "0.3.7",
"lastVerified": "2026-05-29",
"platforms": {
"chatgpt": {
"turns": [
"article[data-testid^='conversation-turn-']",
"[data-testid='conversation-turn']",
"[data-message-author-role]",
"[data-message-id]"
"[data-message-id]",
"div[class*=\"agent-turn\"]",
"[data-testid*=\"conversation-turn\"]",
".group\\/conversation-turn"
Comment on lines +11 to +13

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Badge Wire new turn selectors into the runtime parser

These new ChatGPT selectors are only added to selectors.json, but the actual ChatGPT parser still uses hard-coded selectors in content.js: it first queries article[data-testid^="conversation-turn-"], then falls back only to [data-testid='conversation-turn'], [data-message-author-role], and main article (content.js lines 560-574). Since selectorConfig.platforms.chatgpt.turns is only used by diagnostics/probing, pages that now expose turns only via .group\/conversation-turn, agent-turn, or the broader data-testid* selector will still produce no turns, so this patch does not fix the reported runtime breakage.

Useful? React with 👍 / 👎.

Comment on lines +11 to +13

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Badge Wire new ChatGPT selectors into the parser

On ChatGPT pages where v0.3.7 only exposes the new agent-turn/group/conversation-turn containers, these additions do not change runtime parsing: readChatGPTTurns() in content.js still queries only article[data-testid^="conversation-turn-"] and the fallback list [data-testid='conversation-turn'], [data-message-author-role], and main article, while selectorConfig is only used by the selector probe/diagnostics. As a result the reported no_turns_detected failure remains even though the probe may show the new selectors matching.

Useful? React with 👍 / 👎.

],
"turnRoleAttr": "data-turn",
"messageIdAttr": "data-message-id",
Expand Down Expand Up @@ -36,7 +39,8 @@
"[class*='human-turn']",
"[class*='HumanTurn']",
".font-user-message",
"[class*=\"user-message\"]"
"[class*=\"user-message\"]",
"div[data-is-user=\"true\"]"
],
"assistantTurn": [
"[data-testid='assistant-turn']",
Expand Down
Loading