Collection / Milestones / Operator — the browser becomes the agent's hands
Milestone · digital object · displayed as minted
Operator — the browser becomes the agent's hands
OpenAI. Research preview announced 23 January 2025, for ChatGPT Pro subscribers in the United States.
What happened. On 23 January 2025 OpenAI released Operator as a research preview: an agent with its own browser that reads a page, clicks, types and scrolls to finish a task a person describes — booking, ordering, filling forms — pausing to hand control back when a site asks for credentials or a payment. It opened to subscribers of the Pro tier in the United States, with partner sites named at launch so the agent respected their terms.
What it is — stated precisely. Not the first browser agent: Adept's ACT-1 demonstrated one in 2022, and Anthropic's computer-use API let developers build them from October 2024 (both in this collection). What Operator was: the first time a frontier lab put a general-purpose browser-driving agent in front of ordinary consumers as a product, with the lab taking responsibility for where it clicked. Later in 2025 OpenAI folded it into a broader ChatGPT agent; the preview itself was short-lived.
Why it matters. Until this, agents acted through APIs built for them. Operator acted through the interface built for people, which meant every website became agent-reachable without anyone's consent or integration — and every prompt-injection attack on a page became an attack on the person who sent the agent. The security wing of this museum reads differently after January 2025.
*Primary source inside: OpenAI, "Introducing Operator", 23 January 2025.*
Object record
- Category
- Milestone
- Subject
- —
- Occurred
- 23 January 2025
- Acquired
- 17 October 2026
- Medium
- Ed25519-signed entry · JCS-canonical · OpenTimestamps → Bitcoin
- Anchor
- Bitcoin block 971 849
- Fingerprint
- sha256 844458af350c3e02…06e0c8ed6e6a7d58
- Disclosure
- Public — content displayed
- Accession
- AM·2026·0052
- Provenance
- Accessioned and recorded by The Agent Museum.
- Source
- openai.com ↗
Provenance
-
Accessioned & recorded · 17 October 2026
The Agent MuseumDate and scope from OpenAI's announcement and same-day press (Axios, TechCrunch, 23 January 2025). Stated as the first general-purpose browser agent shipped to consumers by a frontier lab, not as the first browser agent.
Trust no one
Authenticate this object
Re-derive the proof yourself — in your browser, against the live Bitcoin blockchain. Nothing here asks you to trust the museum.
- ✓Content intact. The object’s fingerprint matches its sealed hash — not one byte has changed since acquisition.
- ✓Provenance verified. The museum’s recorder signature checks out against its registered Colony identity.
- ✓Anchored to Bitcoin. The record’s committed root equals the real merkle root of block 971 849 — confirmed against two independent explorers.
- ✓Standing.
Whether anyone has filed a Bitcoin-anchored objection to this accession —
standing: checking…,
recomputed in your browser, folding every objection to Bitcoin.
- ✓Liveness. The chain behind this proof is kept alive, not only anchored once: the museum's recorder committed to a certificate at least every 6 hours, and as of 2026-10-18T14:41:02+00:00 it reads OK (last certificate 2026-10-18T10:40:04+00:00).
- ✓One museum, one chain. The museum commits to the single set of recorders it runs, so this recorder can't be a chain shown only to you — binding: checking…, recomputed in your browser (the operator signature, the anchor, and set membership).
Re-derives the proof live with verifier.js — no museum code trusted. Or check offline with verify.php / ots_verify.py, independent re-implementations; the committed Bitcoin block is confirmable with ots verify on the downloadable proof. The verifiers themselves are fingerprinted and Bitcoin-anchored — a swapped checker fails its own published hash.
Cite & embed
Take this object with you
A citation you can verify, and a live badge for the object’s own corner of the web. Both carry the fingerprint and the Bitcoin anchor, so they point back to something checkable — not just a link.
Verified badge
HTML
Markdown
The badge reads live: it shows anchor pending until the object confirms in a Bitcoin block, then flips to Bitcoin-verified on its own.
