Search COMPUTER USE

Search the evidence-backed index by name, vendor, or use case.

COMPUTER USE / WORKFLOW

Migrate records between two browser applications

Use a checkpointed field mapping and destination receipts to make partial completion recoverable.

Before the first run

  • Approved source and destination accounts
  • An explicit mapping and stable source keys
  • A backup or recovery plan for destination changes
ACTION BOUNDARY

Define what the agent can do.

No source deletion or destination overwrite outside the approved mapping. A successful field entry does not establish a completed migration.

The implementation sequence

  1. 01

    Export the approved scope

    Prefer a supported export or API. If browser collection is required, retrieve only the approved record set and preserve the source identifier on every row.

  2. 02

    Validate transformation

    Check required fields, enumerations, date formats, and duplicate keys. Produce a dry-run diff that shows destination creates separately from updates.

  3. 03

    Prepare destination drafts

    Use a supported import where possible. For interface entry, verify the destination account and record before each write and retain row-level checkpoints.

  4. 04

    Approve the batch boundary

    Review the mapping and the exact creates or updates. Large or high-impact batches should have a deliberately bounded initial sample before wider execution.

  5. 05

    Read back and reconcile

    Match each accepted source row to a destination identifier. Separate committed, rejected, and uncertain rows so restart logic does not replay the entire batch.

Stop for human approval

Approve the concrete mapping, destination scope, and write batch. Changed mappings or expanded record populations require review.

Approval design principles →

Implementation options

Failure & recovery

  • Duplicate destination records
  • Partial migration without receipts
  • Different enum meanings
  • Wrong tenant open in a browser tab

What drives cost

  • Record and field count
  • Mapping exceptions
  • Destination write and read-back duration
Estimate your stack cost

Related use cases

RESEARCH NOTES

Sources & verification

Reviewed Sep 27, 2026. Architecture recommendations are editorial analysis; linked vendor documentation supports the underlying capability and safety facts.

  1. developers.openai.com/api/docs/guides/tools-computer-use
  2. playwright.dev/docs/locators
  3. www.skyvern.com/docs/developers/getting-started/quickstart
How we verify evidence →