Workflow
One profile. Relevant routes. A receipt for every outcome.
The agent adapts to changing forms while credentials and protected decisions remain with you.
Find the valid route. Leave a receipt.
The campaign loop
Scan
Public pages provide the first product facts, sources, and preliminary destination fit.
Confirm
You correct uncertain facts and define what the agent may submit, skip, or escalate.
Authorize
You start a campaign in an owned Codex and Chrome environment with the project inbox available.
Execute
The backend leases one idempotent attempt at a time while unrelated routes continue independently.
Continue
Bounded human actions wait in a queue. Completing one resumes that same attempt after revalidation.
Verify
Receipts, public listings, and backlink checks remain distinct evidence states.
Human action is a pause, not a failure
A destination can request a protected step without freezing the rest of the campaign.
Complete a destination security check
The instruction names the action, reason, expiry, and what the agent will revalidate before resuming.
Same attempt resumes
A single-resume lease prevents duplicate forms and repeated actions.
Other routes continue
A bounded action affects its destination, not the entire campaign.
What the agent learns
The skill uses a universal operating prompt and lightweight destination intelligence. After each attempt, it records observed fields, route changes, eligibility clues, friction, and safe recovery notes.
Those observations improve future decisions without storing directory passwords or converting every page into a brittle click-by-click recipe.
Workflow questions
Do I need Codex and Chrome?
The first client supports Codex operating an authenticated Chrome session. Other clients can be added after the workflow is proven.
Does the campaign need constant supervision?
No. It continues until a bounded protected action is needed or a route becomes terminally blocked. Open actions remain visible for later completion.
How are retries handled?
Every attempt uses stable identifiers and revalidation. A retry cannot silently create a duplicate listing or replay a protected action.
Start with fit, not a promise.
Scan a public product page to separate fully supported zero-touch routes from assisted candidates and product fit.