Skip to content

Ingest collection browser action traces#55

Closed
giaphutran12 wants to merge 1 commit into
codex/playwright-candidate-artifactsfrom
codex/browser-action-trace-ingestion
Closed

Ingest collection browser action traces#55
giaphutran12 wants to merge 1 commit into
codex/playwright-candidate-artifactsfrom
codex/browser-action-trace-ingestion

Conversation

@giaphutran12
Copy link
Copy Markdown
Collaborator

Summary

Stacked on #54 (codex/playwright-candidate-artifacts).

This wires the next honest Playwright precondition: if the collection runner or an Agent-enabled canary emits explicit browser actions, BigSet now preserves them in the process trace.

  • Adds optional collection report fields: browser_actions and agent_browser_actions.
  • Maps explicit action reports into PopulateRuntimeTraceStep { kind: "browser" }.
  • Preserves fields mechanically:
    • target_text / targetText -> browserAction.targetText
    • value_description / valueDescription -> browserAction.valueDescription
    • status -> step.status
    • error -> step.error
    • phase -> step.input.phase
    • unknown actions -> browserAction.action = "unknown"
  • Preserves order by appending browser_actions before agent_browser_actions in the same report scope.
  • Does not infer selectors, clicks, or form inputs from URLs/source outcomes.

What this does not claim

  • The current vendored collection pipeline is not claimed to emit these fields yet.
  • No Playwright script is generated.
  • No cron replay or script promotion is enabled.

Verification

  • node --import ./backend/node_modules/tsx/dist/esm/index.mjs --test backend/test/collection-agent-runner.test.ts backend/test/populate-playwright-readiness.test.ts
  • npm --prefix backend run build
  • npm --prefix backend test
  • git diff --check
  • node --check benchmarks/dataset-agent/run-benchmark.mjs
  • make verify-self-healing

@giaphutran12 giaphutran12 self-assigned this May 22, 2026
@coderabbitai
Copy link
Copy Markdown

coderabbitai Bot commented May 22, 2026

Important

Review skipped

Draft detected.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 0e9a9bbf-2e02-4edb-9973-a3f808c196f3

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch codex/browser-action-trace-ingestion

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

@giaphutran12
Copy link
Copy Markdown
Collaborator Author

Closing stale draft cleanup PR; superseded by later BigSet work.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant