OpenAI's DevDay keynote on September 29 included more than 20 announcements. Most were aimed at developers and businesses, but several of them line up well with the daily work of genealogists: long research projects, piles of records to transcribe, shared family trees, and sensitive DNA data. The Neuron podcast hosts reacted live, and I watched the replay with a genealogist's eye.
Dots: an assistant that keeps working
The headline announcement was Dots, an always-on personal agent built into ChatGPT. Dots has its own cloud computer and browser, connects to more than 4,000 apps through ChatGPT plugins, and keeps working in the background. OpenAI's demos showed Dots reviewing overnight messages, rebuilding a slide deck, rescheduling a conflict, and fixing software bugs. Dots is included in the plan and does not count against usage. It is available now to Pro, Business Premium, and Enterprise users.
Steve Little introduced me to Dots last week and showed me how to use it like an assistant, and that framing is the key. Think of a research assistant who drafts the correspondence, organizes the research log, summarizes what came in overnight, and reminds you what is waiting for your review. For a genealogist juggling several projects, that is a very different tool from a chatbot you have to prompt from scratch every time.
One personal observation: Dot's speech pattern sounds to me very "Silicon Valley Californian". In the keynote demo, Dots was upbeat and casual, even handing out wedding advice. Dots is like having an Astra-level smart Alexa or Google Nest that you can converse with; so you could talk through a brick wall problem on the drive home from the courthouse or archive and have Dots pick up the thread when you sit back down at your desk.
Spaces: a shared workspace for research teams
ChatGPT Spaces gives teammates and Dots a shared place to work on pages, files, and data. Someone can tag Dots in a comment and it gets to work. For genealogists, the obvious fits are family history societies, project volunteers, and cousins collaborating on a shared line. A space could hold a research log, a source list, and a draft write-up, with Dots keeping the log current while the humans make the judgment calls. OpenAI also said a collaborative presentation feature is coming, which could help with society talks.
Codex in the cloud: long jobs without babysitting
Codex now runs fully in the cloud, so a task started on a phone keeps running after the laptop closes. For genealogists who build their own scripts, this suits the long, tedious jobs: batch processing record images, cleaning and merging spreadsheets of census extractions, or analyzing large sets of DNA matches. You hand off the task and check on it later.
Speed and cost: Sol, Ultra fast, and cheap cached input
GPT-6.1 Sol is described as delivering close to Astra-level intelligence at about a fifth of the price, and cached input is discounted by 95 percent. Caching matters for genealogy because research is full of repeated context. When you work through a long run of court records or a family file, the same background material gets reread again and again, and cached input makes that far less expensive. Ultra fast mode runs about eight times faster at six times the price, which most genealogists will not need but may enjoy for large transcription batches.
The new Decisions API answers from a fixed set of options in a fraction of a second. It is built for routing and classification, which could suit sorting a pile of unlabeled images into record types, such as deeds, wills, or probate inventories.
Privacy: the item genealogists should watch most closely
OpenAI previewed Private Intelligence, which pairs zero data retention with private safety processing, with private inference coming this fall. Genealogists handle sensitive material, including DNA results, living relatives' details, and unpublished family stories. The hosts called this the most significant item for enterprises and predicted every provider will offer something similar by January 1. If it works as described, it could ease one of the biggest concerns about putting genetic and family data into AI tools. Genealogists should still read the fine print on what is retained, who can access it, and what counts as an approved safety purpose.
Tools for the people who build genealogy software
Sign in with ChatGPT lets users spend their own plan's tokens inside third-party apps. For the small developers behind genealogy tools, that removes the burden of paying for every user's AI costs. Plugin extensions let developers build full applications inside ChatGPT, and the new OpenAI Marketplace gives them a way to reach customers. It is easy to imagine tree builders, record indexes, and DNA analysis tools showing up in that ecosystem.
Cautions
Dots and most of the new products are not yet available in the EU or UK, which leaves many genealogists waiting. The hosts also urged viewers to treat vendor-published benchmarks as marketing, since each lab picks the comparisons that flatter it.
That brings up a term worth knowing: benchmaxxing. It means tuning a model, or the way its results are presented, to score as high as possible on public benchmark tests rather than to be better at real work. A model can post impressive numbers on a coding or math test and still stumble when asked to read a faded deed or untangle two men of the same name. Test any new tool on your own records and your own research questions before trusting it. Whatever an assistant produces, a genealogist's standards do not change. Cite the source, check the original, and keep the human in charge of the conclusions.
The takeaway
Most of what OpenAI shared is about making AI easier to use and easier to fold into daily work. For genealogists, the promise is an assistant that handles the tedious parts of research while you handle the evidence. The new privacy options and cheaper cached input make that more realistic, and the shared Spaces make it easier to work as a team.
Compiled by Katherine and Claude (Sonnet 5.5 Medium). Source: The Neuron's OpenAI DevDay 2026 live watch party on YouTube.
.jpeg)
No comments:
Post a Comment