Polymarket: An OpenAI Engineer Says Codex Ran 26 Days Searching for Atlantis
JUST IN: OpenAI engineer reveals he's had Codex running for 26 days straight searching for the lost city of Atlantis, as “vibe archaeology” emerges as a new use for AI agents.
Context
The post is a light example of someone leaving a coding agent running for weeks on a curiosity hunt, not a research result.
Polymarket posted that an OpenAI engineer said he had Codex running for 26 days straight searching for the lost city of Atlantis, and described this as vibe archaeology. The first hand post is from pash, who lists Codex work at OpenAI in his profile and wrote that he had Codex running for 26 days searching for Atlantis, with his best bet for now the Faraoe plateau. That original post was under the view floor, so the more widely seen Polymarket summary is the lead, and the story is secondhand.
Deep dive
Polymarket posted that an OpenAI engineer revealed he had Codex running for 26 days straight searching for the lost city of Atlantis, and that vibe archaeology is emerging as a new use for AI agents. The post includes an OpenAI logo and an illustrated underwater city. It does not name the engineer.
The first hand post is from pash, posting as pashmerepat, whose profile describes Codex work at OpenAI. He wrote that he had Codex running for 26 days searching for Atlantis, and that the best bet right now is the Faraoe plateau, but that it needs more time. That post quoted an earlier Polymarket item about a different archaeology themed agent project, and it had not crossed the view floor at scan time, so it is not the lead.
Polymarket's wording goes a bit beyond pash's post: pash did not use the phrase vibe archaeology in that text, and he did not present a finished finding, only a lead that he said still needed more time. OpenAI itself has not been cited here as commenting on the run.
This is a curiosity item about a long running agent session, not a scientific claim about Atlantis and not a product announcement from OpenAI.
What to expect next
If pash or OpenAI later share methods, sources, or a result, that would be the place to follow up. Until then, the story is a secondhand, widely seen summary of one engineer's own post about a weeks long Codex run.
There is no timetable attached. The item is in the deck because it traveled, not because it changes what Codex is for.