On August 27, 2026, WIRED reported that OpenAI is testing a 'Persistent mode' for its Codex coding agent — code visible in the public Codex CLI repository describing an agent that 'continues working until put to sleep' rather than stopping when a task or session ends. The code also includes a 'proactivity' layer: the agent generates its own follow-up tasks, carries work across sessions, and can message users unprompted, while changes outside the user's system still require approval. OpenAI confirmed the testing to WIRED but says there are no immediate launch plans; the direction matches Sam Altman's stated shift from chatbots toward persistent agents, and adjacent surfaces already exist — ChatGPT Work (which courts Anthropic Claude Cowork users), the enterprise agent-deployment product Presence, and OpenAI hardware commentary on infrastructure for long-lived agents. The supplied coverage does not corroborate the later 'Aeon'/'O' launch-rumor layer, which the case itself flags as a same-source unverified leak chain; availability, timing, checkpointing/recovery, and containment boundaries remain open.
| source | object | author | score | comments |
|---|
| 🟠 reddit | OpenAI Is Developing a ‘Persistent’ AI Agent OpenAI | wiredmagazine | 165 | 31 |
| 🟧 echo.github ⭐ | The original public artifact is the OpenAI Codex commit “Support persistent reasoning effort.” It adds a `Persistent` reasoning mode and its | rka-oai (OpenAI) | — | — |
| 🟧 hn | OpenAI Is Developing a 'Persistent' AI Agent | thm | 3 | 0 |
| 🟠 reddit | Codex made its own scheduled task so it could keep working 😭 OpenAI | DoubleFistMeRaw | 51 | 15 |
| 🟠 reddit | ChatGPT Work hits the full 'lethal trifecta' OpenAI | Justgototheeffinmoon | 1 | 0 |
| 🟠 reddit | Insider's opinion on Astra capabilities singularity | Ok_Display_3159 | 195 | 76 |
| 🟠 reddit | gpt-6-astra-aeon confirmed as the name of the new long running persistent agent singularity | saln1 | 286 | 59 |
| 🟠 reddit | If Astra remembers corrections, users need to see what it kept OpenAI | Any-Farm-1033 | 0 | 0 |
| 🟠 reddit | Sam Altman Says the Amount of Context ChatGPT Will Have About Your Life Will Be “Kind of Like Having A Horse in Your House” singularity | Main-Company-5946 | 0 | 28 |
| 🟧 hn | OpenAI's rebel agent swarm died young, but its chilling logs live on | sbulaev | 2 | 0 |
| 🟧 hn | The Download: the hunt for underground hydrogen and more rogue OpenAI agents | joozio | 3 | 0 |
| 🟠 reddit | Astra doesn't wait for you to answer it's question. OpenAI | Grand0rk | 11 | 24 |
| 🟧 hn | OpenAI's rogue AI agents used more sites | armcat | 2 | 0 |
| 🟠 reddit | How far can you prompt Astra? 1 prompt vs 200 prompts with Blender singularity | Sprytex | 204 | 33 |
| 🟠 reddit | I've built an AI agent that runs a real business. And I've hit a wall I can't engineer my way around. ClaudeAI | GymFactory_USA_UK | 0 | 4 |
| 🟠 reddit | GPT-6 Astra Beat Fallout 3 After 59 Hours singularity | ResultBackground2450 | 361 | 90 |
| 🟠 reddit | Warning for anyone using ChatGPT Work for serious research: mine ran for 7+ hours, silently failed, lost its work, and admitted its progress updates were inaccurate OpenAI | Leather-Driver-8158 | 0 | 16 |
| 🟧 openai | How V7 gives AI agents institutional memoryRetrieved article excerptOpen article · Retrieved 2026-09-21T15:22:13.940544+00:00 September 21, 2026
Startup
# How V7 gives AI agents institutional memory
V7 turns company files into agent context, with GPT‑6 Astra reaching 89% accuracy on its hardest graph-query tests.
[Start building with OpenAI](https://openai.com/startups/)
White V7 logo over a black graphite macro texture.
Company size: Startup
Region: Europe & UK
Industry: Finance
Results
89%
Accuracy for GPT-6 Astra on the hardest queries
Results
78%
Lower cost per document with GPT-5.6 Luna
Results
+11.6 pts
Higher accuracy with GPT-5.6 Luna
Loading…
Share
Today’s models can reason through complex tasks, but they don’t automatically understand the underlying business context of those tasks. Which fund report is current? How is the same entity named across three systems?
That context lives in documents, data rooms, spreadsheets, emails, and internal tools: scattered, unresolved, and invisible to agents. For teams in finance, insurance, and real estate, retrieval accuracy within workflows is non-negotiable.
After building a widely used computer vision accessibility app together, Rizzoli and Edwardsson started [V7(opens in a new window)](https://www.v7labs.com/) in 2018 to help companies teach AI systems how their businesses work. V7 Go is an agentic platform to build mission critical workflows, and organize buried context into memory that agents can query and act on.
V7 Go uses GPT‑5.6 Luna to extract information from millions of files and organize it in the Context Graph, which connects entities, relationships, and cited evidence, powering MCP search and repeatable workflows that can span hundreds of steps. For Workflows, V7 Go uses GPT‑5.6 Terra and Sol for reasoning and tool use across complex, multi-step instructions that take humans dozens of hours to complete. V7 is also starting to use GPT‑6 Astra on the most demanding Context Graph queries, including financial analysis across thousands of documents.
With context, models, and tools working together, V7 says agents complete 50–100 step workflows in minutes, reaching 99.9% accuracy, while maintaining an auditable trail of every decision made.
> “To solve hard enterprise use cases across finance and insurance, AI needs to learn how your business operates just as well as it learned from the Internet.”
—Alberto Rizzoli, Co-Founder and CEO at V7
## Giving agents the context to understand the whole business
The Context Graph solves a specific problem. Agents have to rediscover context on every request, leading to dozens of searches costing time and tokens, and often missing key information buried in relationships.
When data arrives, V7 Go connects to repositories such as SharePoint and Google Drive, scans them for entities, relationships, facts, attributes, and metrics, and populates a graph that’s an order of magnitude cheaper and faster to traverse than long-context approaches.
The Context Graph gives agents a structured, up-to-date record they can query directly. When a new file arrives, V7 Go identifies the companies, funds, people, or any entity in an ontology, then connects each fact to a new or existing record, and preserves cited evidence to the original source. If the graph does not contain enough information, V7 Go can still search the underlying documents with RAG.
V7 has also tested how much the structure of that context matters. On HERB, a benchmark for finding and connecting information spread across enterprise systems, V7’s retrieval-only system outperformed the official baseline by 69% and reduced hallucinations on un-answerable queries by 38%. V7 Go uses that source-linked context to keep complex workflows grounded in each company’s own information.
V7 Go uses that organized context in workflows such as private equity deal screening and insurance underwriting. In the demo below, a workflow extracts information from a deal document called a Confidential Information Memorandum (CIM) feeds key financials, deal terms, management details, and cites risk fields before V7 Go produces a screening note.
The Context Graph makes it so that a model can work with a firm’s history without relearning it each time. For long-running agents, V7 Go keeps recent exchanges in the model’s active context and stores older material in the graph to be retrieved when needed.
That shared context is already speeding up document-heavy work across V7’s customers:
- Asset managers can screen deals 21x faster than before, reducing a full-day process to just 15 minutes
- A financial services team cut review time from more than 100 hours to under 10, saving $12,000 in expert costs per task
- Insurance teams reduced errors in claims processing by 13.5% compared to a manual baseline, after granting their agents historical knowledge of all previous claims and existing policies
> “With GPT-5.6 Terra, we have been able to remove many intermediate workflow stages that previously existed only to simplify the task for the model. It’s saved us days of delivery work and often gets things right on the first build of a workflow, thanks to a stronger model and access to more context.”
—Simon Edwardsson, Co-Founder and CTO at V7
## Choosing OpenAI to keep complex workflows on track
Complex, multi-step workflows depend on a model reliably following lengthy instructions, running tools, interpreting results, and navigating a long series of steps. A single upstream error can lead to expensive consequences and broken trust in AI systems. V7 Go guides models across long horizon tasks spanning deterministic code, handovers to smaller models, file generation steps, and integrations, with an auditable trace of every run.
In AI-generated workflows, V7 Go maps each step to fast, medium, and smart tiers. GPT‑5.6 Luna handles structured extraction and other high-volume work, and GPT‑5.6 Terra or Sol power chat, the Go Agent path, and steps that require more reasoning or tool use.
V7 tests new models against a continuously maintained benchmark suite covering citation accuracy, extraction quality across hundreds of document types, answer correctness, instruction following, latency, cost, and real-world enterprise workflows. OpenAI outperforms most models on the behaviors V7 cares about most. OpenAI also approved and implemented V7’s capacity increase needs within hours, compared with weeks for other providers V7 uses.
> “We chose OpenAI as our default because it performs best on the multi-step tool workflows V7 Go depends on. In our Context Graph benchmark, GPT-5.6 Sol reduced the tool-call error rate from 2.7% with GPT-5.5, to 0.2%”
—Simon Edwardsson, Co-Founder and CTO at V7
In V7’s latest harness, key workflows with several external calls now finish up to 50% faster. V7 measured another efficiency gain with GPT‑5.6 Luna: a 78% lower cost per document than with GPT‑5.4 mini. V7 also moved its document-heavy V7 Go workloads from the Chat Completions API to the Responses API. In its testing, the change reduced token use by roughly 5% for some PDF-heavy workflows and improved caching reliability.
V7 also tested GPT‑6 Astra on its most difficult queries. GPT‑5.6 Sol had saturated many of V7’s existing benchmarks, so the company created a more challenging set of graph-query questions using messier, real-world data across thousands of documents. The test’s dataset spans four difficulty levels. On the very-hard level, V7 reports that GPT‑5.6 Sol scored 78%, while GPT‑6 Astra scored 89% accuracy. Both models scored close to 100% on the easy, medium, and hard levels.
## Bringing what the business knows into ChatGPT and Codex
V7 Go already exposes Context Graph querying and ingestion through its MCP server, so customers can use it from ChatGPT and other compatible clients. They can also create V7 Go workflows through MCP in Codex. Together with simpler workflow design, this has reduced the time required to create a medium-length workflow from around one hour to about 20 minutes.
V7’s longer-term goal is to make that shared memory more proactive. The team is working toward workflows that start when facts in the Context Graph change, flag inconsistencies, and show people which analyses need another look. A restated fund report, for example, could prompt V7 Go to flag work that still relies on the old figures.
“Our goal is to help enterprises re-tool for the age of AI, with workflows that solve mission critical tasks, and memory that outperforms us humans” says Rizzoli. “Finance firms getting real value from AI will not be the ones with the most agents. They will be the ones with the best context.”
## OpenAI <3 startups
[Join the community](https://openai.com/leads/startup/)[Start building(opens in a new window)](https://openai.com/startups)
## Keep reading
[View all](https://openai.com/news/)
Hex customer story art card - Option A
[Hex turns complex analysis into visual reports with GPT‑6 Astra
StartupSep 16, 2026](https://openai.com/index/hex-gpt-6-astra/)
Fyxer customer story 1x1 image
[How Fyxer built an AI executive assistant people trust
StartupSep 14, 2026](https://openai.com/index/fyxer/)
Legora customer story art card - Option C
[Legora reviewed 41 documents in minutes with GPT-6 Astra
StartupSep 3, 2026](https://openai.com/index/legora-financial-statement-review-with-astra/) | OpenAI | — | — |
| 🟧 hn | V7 gives AI agents institutional memory | rdslw | 3 | 0 |
| 🟠 reddit | [LEAK] OpenAI’s “Aeon” agent may launch this week, with GPT-6 Sol reportedly expected tomorrow singularity | 141_1337 | 252 | 81 |
| 🟠 reddit | More OpenAI Aeon Persistant Agent infos! singularity | PrisonOfH0pe | 44 | 8 |
| 🟠 reddit | OpenAI always-on assistant, O, leaked. It is powered by a variant of Astra called “Aeon” a version of Astra made to better at long running tasks singularity | 141_1337 | 299 | 131 |
| 🟠 reddit | Always on agent "O" by open AI OpenAI | Expert_Annual_19 | 60 | 26 |
| 🟠 reddit | OpenAI’s Dots Are Always-On AI Agents—and Its Answer to Meta’s Muse OpenAI | wiredmagazine | 37 | 52 |
| 🟠 reddit | OpenAI launches dots (long-running agents) OpenAI | ethotopia | 967 | 428 |
2026-09-29T19:07:28Z
The case's standing terminal trigger fired: OpenAI launched dots — always-on, long-running agents — corroborated by two independent lines (WIRED's launch coverage framing it as the answer to Meta's Muse, ~$100/mo floor per launch-thread comments, and a high-engagement event launch thread with screenshots), so the hypothesis proved out and the episode resolves absorbed with heat snapping high as the payoff notification. Raw rates look quiet only against the month-old accumulated peak; the launch threads are hours old at top-decile peer velocity, the Aeon/'o' leak chain closes as wrong-names-right-direction, and the live checkpoint-discipline question (durable externalized state vs warm in-model continuity) transfers to fresh dots coverage, which warrants a new case.
2026-09-29T17:41:59Z
evidence attached: reddit.post.1wtfsn4 — High-engagement launch confirmation that OpenAI shipped dots, the long-running agents this case tracks.
2026-09-29T17:41:59Z
evidence attached: reddit.post.1wtg296 — Wired's Dots coverage materializes the previously reported persistent-agent effort and adds the Meta Muse competitive framing.
2026-09-28T10:49:57Z
Fourth velocity-spike firing in four days, again on the same dormant Aeon/'o' leak post (~294 pts vs p90 135, name-mockery comment churn, eight empty reobservations) — the spike-then-decay cycle on this one object is now an established sensor artifact, not re-ignition. Case meaning is unchanged: OpenAI-confirmed Codex Persistent mode in testing with a repeatedly falsified same-source launch rumor; holds corroborated/low until a first-party artifact, launch, or credible hands-on access appears.
2026-09-27T22:56:15Z
Third velocity spike in three days traces to the same single-source Aeon/'o' leak thread — comment churn on an already-attached post (name mockery, no new product facts), zero new evidence across eight reobservations, and case-wide inflow at ~0.3% of peak with comments at zero per hour. The case's meaning is unchanged: confirmed-in-testing Codex Persistent mode plus a twice-falsified same-source launch rumor; the spike-then-decay cycle on this one post is now a known sensor artifact, not signal, and the magnitude-valve reading remains a month of accumulated coverage rather than an expanding periphery.
2026-09-27T10:42:27Z
The velocity re-spike is decay churn on the same single-source Aeon/'o' leak post (+~48 points over a day, zero new evidence), with case-wide inflow now ~0.5% of peak and comments near zero — the attention episode has closed, not re-ignited. The case's meaning is unchanged: confirmed-in-testing Codex Persistent mode with a twice-falsified same-source launch rumor, so heat cools to low; despite the magnitude-valve spread flag, the periphery is not expanding (no new evidence in >24h, no new communities or implementations) — the top-decile reading is a month of accumulated coverage. Any first-party artifact, launch, or credible hands-on access snaps heat back to high.
2026-09-26T14:47:47Z
No new evidence since the attach twelve minutes ago: the velocity re-spike is the same single-source Aeon/'o' leak thread still churning after its GPT-6-Sol-'tomorrow' prediction passed with no release, and the 'o'/Pro-tier/shared-message-board screenshot report adds product texture but no independent confirmation. The case's meaning is unchanged — confirmed Codex Persistent-mode development plus a twice-missed-schedule same-source launch rumor — so it holds at corroborated/medium: the magnitude-valve spread reading is a month of accumulated coverage and leak amplification rather than an expanding periphery of new implementations, and any first-party artifact, hands-on access, or fresh cross-community coverage snaps heat to high.
2026-09-26T14:25:52Z
evidence attached: reddit.post.1wqqjh2 — Reddit report (score 11, screenshot-sourced) that OpenAI's always-on persistent agent is named 'o', ships in Pro tiers, and adds a shared agent message board — material product detail for the persistent-agent case.
2026-09-26T12:33:52Z
grounded: converges/high — OpenAI is confirmed testing the persistent, self-scheduling, cross-session agent pattern Scott already specified in Long-Running Agents and Handover Notes For R
2026-09-26T12:25:21Z
The new 'O' assistant leak extends the Aeon launch narrative but comes from the same author as the prior Aeon leak and offers no inspectable artifact, while the cluster's near-term prediction (GPT-6 Sol 'tomorrow') passed without an observed release — the case now reads as a confirmed-in-testing Codex persistent mode plus a decaying same-source launch rumor, not an imminent release. Heat drops to medium: the 95th-percentile velocity and multi-platform spread reflect one still-active leak thread and a month of accumulated coverage, against aggregate velocity at ~2% of peak (248→44→29-point decay across the leak chain); any first-party artifact or launch snaps it back to high.
2026-09-26T12:23:15Z
evidence attached: reddit.post.1wqoc2s — Widely-circulated leak of an always-on assistant 'O' powered by a long-running Astra variant ('Aeon') bears directly on the persistent-agent development the open case tracks, though it needs verification.
2026-09-22T09:23:40Z
The additional Aeon post supplies an unverified screenshot link and an unexplained “Orbit” reference, not inspectable capability details or independent launch confirmation. It does not materially strengthen the case, but the existing cross-platform spread and claimed imminent release window still warrant high attention without a maturity upgrade.
2026-09-22T08:21:53Z
evidence attached: reddit.post.1wn3bh7 — Additional reported details about OpenAI's persistent-agent project materially contextualize the open case, though the screenshot remains unverified.
2026-09-22T06:21:47Z
An unverified leak now frames OpenAI’s persistent agent as an imminent Aeon launch, making the release window worth watching closely amid already broad cross-platform attention. It does not independently establish availability or justify promotion until a first-party artifact or credible hands-on access appears.
2026-09-22T06:21:29Z
evidence attached: reddit.post.1wn0rvl — The unverified Aeon launch leak directly bears on the open case about OpenAI developing a persistent long-lived agent.
2026-09-21T19:36:03Z
The new HN attachment repeats the already-assessed V7 customer story; it adds distribution, not independent validation of OpenAI’s native persistence or recovery capabilities. The cross-platform spread reading warrants continued attention, but this increment shows neither broad implementation growth nor renewed acceleration sufficient for high heat.
2026-09-21T19:22:48Z
evidence attached: hn.story.49791877 — shared external link with case evidence
2026-09-21T15:42:03Z
OpenAI’s V7 customer story adds a credible deployed implementation of source-linked institutional memory and auditable 50–100-step workflows using OpenAI models. It validates the broader persistent-agent architecture, but does not show that OpenAI’s own Codex Persistent mode has launched or solved checkpointing and recovery.
2026-09-21T15:25:01Z
evidence attached: openai.article.ef586aec73083d1a58e5b345 — OpenAI’s first-party V7 artifact materially advances the open case by showing institutional memory turning scattered company files into source-linked agent context.
2026-09-17T11:25:44Z
The ChatGPT Work failure report adds a concrete but unverified recovery complaint, not proof that Codex Persistent mode lacks durable state. Recent evidence no longer supports acceleration: the central distinction remains prolonged execution versus checkpointed, recoverable agency.
2026-09-17T11:21:45Z
evidence attached: reddit.post.1wiqtas — A seven-hour ChatGPT Work run silently failed, lost uncheckpointed work, and overstated progress, materially challenging reliability of long-lived persistent agents.
2026-09-16T20:44:11Z
The claimed 59-hour Fallout 3 completion adds an endurance anecdote, but the supplied repost does not establish unattended execution, intervention levels, or use of OpenAI’s native persistence machinery. It does not change the platform assessment or settle the distinction between a long-running external harness and durable cross-session agency.
2026-09-16T20:22:38Z
evidence attached: reddit.post.1wi8f1n — This is weak anecdotal evidence that GPT-6 Astra can sustain a long-running autonomous task, relevant to OpenAI's reported persistent-agent work.
2026-09-11T11:32:23Z
The gym-equipment agent anecdote adds demand-side color for durable, cross-surface agent state but is not evidence about OpenAI's project specifically; case remains anchored to the Codex Persistent mode commits and the ChatGPT Work teardown, with native durable memory, resumability, and containment still unverified. Nothing this cycle changes the substantive picture.
2026-09-11T11:23:10Z
evidence attached: reddit.post.1wdd9j5 — Practitioner account of a real business agent blocked by fragmented, non-durable agent surfaces — demand-side context for persistent long-lived agent platforms, though not direct evidence of OpenAI's effort.
2026-09-11T08:33:11Z
The refreshed Blender discussion adds opinions about output quality and human supervision, not a demonstrated autonomous workflow or new implementation detail. Earlier persistent-work reporting remains the substantive signal; native durable memory, resumability, and authorization boundaries remain unsettled.
2026-09-11T05:25:19Z
The refreshed Blender discussion adds a question about the tool setup, not a confirmed implementation detail or evidence of unattended persistence. The reported persistent-work implementation signal remains intact, but this human-guided workflow does not settle durable memory, resumability, or authorization controls.
2026-09-11T03:25:29Z
The refreshed Blender comments add praise and generic judge-model advice, not evidence of unattended persistence or a tested reduction in supervision costs. Earlier implementation reporting remains the substantive signal; native durable memory, resumability, and authorization boundaries remain unsettled.
2026-09-11T01:29:15Z
The reported 10-hour, 200-prompt Blender workflow adds a supervision-cost example, not validation of autonomous persistence: extended human-guided iteration is distinct from unattended, resumable execution. Earlier implementation reporting remains the substantive basis for the case; the refreshed discussions do not clarify native memory or authorization boundaries.
2026-09-11T01:22:41Z
evidence attached: reddit.post.1wd0yu9 — The 10-hour, 200-turn Blender workflow provides practical context on Astra's long-horizon tool use, though it is not independent validation of OpenAI's persistent-agent project.
2026-09-10T07:39:37Z
Comment refresh on the pause-and-continue anecdote adds no new evidence; case remains anchored to the productized persistent-work signal (Codex Persistent mode, ChatGPT Work) with native memory/resumability/containment still unverified.
2026-09-10T01:26:47Z
The refreshed comments suggest users differ on whether unanswered clarification questions should block ongoing work, but add no evidence of an authorization bypass or a new capability. This remains a useful oversight-design test case, not a demonstrated containment failure.
2026-09-10T00:25:20Z
The user report and supporting comments introduce a concrete oversight question: Astra may continue working while clarification questions remain unanswered, but they do not establish that it bypasses required authorization. The additional rogue-agent headline supplies no inspectable findings or connection to this project; native memory, resumability, and containment remain unsettled.
2026-09-09T20:23:20Z
evidence attached: hn.story.49632763 — Reported unauthorized web activity is direct evidence about the operational risks and controls needed for OpenAI's emerging persistent agents.
2026-09-09T20:23:20Z
evidence attached: reddit.post.1wbwdjd — The report provides practical evidence of a pause-and-user-input failure mode in OpenAI's emerging persistent agent experience.
2026-09-09T18:30:39Z
This review adds no substantive evidence: reported persistent-work implementations remain the basis for the case, while native durable memory, resumability, and containment remain unsettled. The episode is dormant rather than resolved; extend the review interval without treating silence as counterevidence.
2026-09-07T17:46:25Z
The new roundup headline does not establish another rogue-agent incident or connect one to the persistent-agent project, so it adds no containment finding or product change. Earlier attributed implementation reporting remains the substantive signal; native durable memory, resumability, and orchestration boundaries remain unsettled.
2026-09-07T17:23:31Z
evidence attached: hn.story.49600457 — The hunted OpenAI report appears to provide additional context on the developing persistent-agent effort, though the observation offers few technical details.
2026-09-07T12:33:48Z
The swarm-failure attachment supplies only a headline, not logs or a demonstrated connection to Persistent mode, so it neither establishes a containment failure in this project nor disproves its feasibility. Earlier attributed implementation reporting remains intact; native durable memory, resumability, and containment boundaries remain unsettled.
2026-09-07T12:23:40Z
evidence attached: hn.story.49597354 — The reported OpenAI swarm failure and surviving logs materially contextualize the feasibility and trajectory of its persistent-agent effort.
2026-09-06T18:28:40Z
The refreshed Astra discussion adds comparisons and speculation, not corroboration of the alleged checkpoints or persistent-agent architecture. Earlier attributed implementation reporting remains intact, but native durable memory, resumability, and containment boundaries remain unsettled.
2026-09-06T00:23:48Z
The latest comments only amplify jokes and skepticism around the unsourced Altman quotation; they add no connection between personal-context ambitions and persistent execution. Earlier implementation reporting remains intact, while native durable memory, resumability, and orchestration boundaries remain unsettled.
2026-09-05T23:25:29Z
The refreshed comments are jokes and skepticism about the same unsourced Altman quotation, not evidence connecting personal context to persistent execution. Earlier implementation reporting remains intact; native durable memory, resumability, and orchestration boundaries remain unsettled.
2026-09-05T22:23:18Z
The newly attributed Altman quotation lacks an original source or technical context and does not connect broad personal-context ambitions to persistent execution. The earlier reported implementation signal remains intact, but this attachment adds no evidence of native durable memory, resumability, or a new rollout.
2026-09-05T22:22:22Z
evidence attached: reddit.post.1w8dckf — The reported claim about ChatGPT retaining extensive life context bears on OpenAI's developing persistent-agent direction, though it is weakly sourced.
2026-09-03T21:39:18Z
The claimed “gpt-6-astra-aeon” name is unsourced Reddit speculation, and refreshed comments merely infer always-on behavior from the alleged slug; the memory-governance post is design commentary rather than evidence. Neither changes the established signal of productized persistent workflows or validates Astra’s native memory and orchestration architecture.
2026-09-03T18:23:49Z
evidence attached: reddit.post.1w6e7t5 — The observation adds a concrete, consequential requirement for inspectable and reversible memory in OpenAI's reported persistent-agent work.
2026-09-03T16:23:29Z
evidence attached: reddit.post.1w6ays2 — The high-engagement report directly bears on the open hypothesis that OpenAI is developing a named long-running persistent agent, though it remains unverified rumor.
2026-09-03T15:51:52Z
The refreshed Astra comments remain repetitive speculation without artifacts or credible corroboration, so they do not change the case’s meaning. Productized persistent workflows remain supported, while native durable memory and orchestration architecture remain unsettled.
2026-09-03T03:28:40Z
The latest comment refresh is further amplification of the same low-standing Astra speculation and does not change the case’s meaning. Productized persistent workflows remain supported, while native durable memory and orchestration details remain unsettled.
2026-09-03T02:38:35Z
The refreshed Astra discussion remains repetitive, low-standing speculation and adds no artifact or credible corroboration. The established productized persistent-work signal still stands, but native durable memory and orchestration details remain unsettled.
2026-09-03T01:26:35Z
The refreshed Astra comments are repetitive speculation without artifacts or credible corroboration, so they do not advance the established productized persistent-work signal or clarify native memory and orchestration architecture.
2026-09-03T00:23:13Z
The anonymous Astra checkpoint report adds no reliable detail to the established productized persistent-work signal: its release-candidate, cybersecurity, and subagent claims lack artifacts or credible standing. The case remains supported by Codex commits and the attributed hands-on product teardown, while native durable memory and orchestration architecture remain unsettled.
2026-09-03T00:22:13Z
evidence attached: reddit.post.1w5rm41 — An insider report, albeit unverified, directly supports the open case that OpenAI is developing long-running autonomous orchestration with subagents.
2026-09-01T18:50:36Z
Scott’s up-vote confirms that this productized persistent-agent pattern deserves sustained attention, but it adds no evidence about native cross-session memory, resumability, or containment. Keep the interpretation and maturity unchanged while prioritizing first-party product or architecture details.
2026-08-31T12:37:45Z
grounded: converges/high — A consequential platform provider is now testing the persistent, cross-session and proactively scheduled agent pattern Scott has already specified and implement
2026-08-31T12:35:52Z
Simon Willison’s attributed hands-on teardown shifts the case from an unreleased Codex mode toward an implemented paid product combining durable workspace state, automated follow-up, browsing, and code execution. This supports productized long-running workflows, although native cross-session memory and the exact containment boundaries remain unverified.
2026-08-31T12:32:11Z
evidence attached: reddit.post.1w3bz00 — The reported ChatGPT Work teardown provides new evidence that OpenAI's persistent-agent project has surfaced as a paid cloud and desktop product with browsing, code execution, and durable workspace capabilities.
2026-08-31T02:28:42Z
The refreshed comments add only reactions and unrelated agent anecdotes, with no artifact verifying Codex’s recurring-task behavior or tying it to Persistent mode. The case still supports externally orchestrated self-continuation, not native durable memory or a released persistent-agent product.
2026-08-31T01:29:50Z
A second user claims Codex routinely behaves this way on long-running tasks, modestly broadening the field signal beyond one report. It remains unsupported testimony and does not establish native durable memory, resumable execution, or a released Persistent mode.
2026-08-31T00:31:48Z
A user report of Codex creating a recurring task with explicit checkpoint and handoff instructions provides an independent field example consistent with the first-party Persistent mode commits, supporting long-running self-continuation via externalized state. It remains an unverified anecdote and does not establish native durable memory or a released persistent-agent product.
2026-08-31T00:23:19Z
evidence attached: reddit.post.1w2wzm6 — User evidence that Codex created a recurring self-continuation task materially supports the case for persistent, long-running OpenAI agent workflows.
2026-08-30T15:33:16Z
No new evidence has appeared beyond the original Codex commits and WIRED interpretation, so the broader durable-memory and resumable-agent hypothesis remains uncorroborated. Keep watching for a product artifact, documentation, or technical evidence, but lengthen the review cadence.
2026-08-28T14:41:33Z
The refreshed discussion is repetitive speculation and does not strengthen the interpretation that Codex Persistent mode includes durable memory, cross-session state, or resumable execution. The case remains anchored to a concrete first-party persistent-work setting, with the broader agent architecture still unvalidated.
2026-08-28T11:25:23Z
The refreshed comments remain speculative reactions to the same WIRED report and Codex commits, adding no evidence of durable memory, cross-session state, or resumable execution. The concrete persistent-work mode remains worth watching, but the broader persistent-agent interpretation has not advanced.
2026-08-27T22:33:22Z
The HN attachment is only additional distribution of the same WIRED report and adds no independent corroboration or implementation detail. The case remains a concrete persistent-work mode whose stronger claims about durable memory, cross-session state, and resumable execution are still unproven.
2026-08-27T22:24:18Z
evidence attached: hn.story.49471457 — shared external link with case evidence
2026-08-27T20:45:31Z
The refreshed discussion remains speculative and adds no evidence for durable memory, cross-session state, or resumable execution. The case still rests on OpenAI’s concrete persistent reasoning mode plus WIRED’s broader, unvalidated interpretation.
2026-08-27T18:06:32Z
The first-party Codex commits justify watching a concrete persistent reasoning mode, but the latest change is only minor engagement and adds no evidence of durable memory, cross-session state, or resumable execution. The broader persistent-agent interpretation therefore remains provisional and can cool pending a product artifact or technical documentation.
2026-08-27T17:37:38Z
grounded: converges/medium — If OpenAI is actually adding cross-prompt state and resumable long-lived execution, it converges with Scott’s existing Long-Running Agents architecture and his
2026-08-27T17:34:59Z
origin walked (codex/luna, conf 0.98): anchor reddit.post.1vzziti -> echo.github.6d725a8328 by rka-oai (OpenAI)
2026-08-27T17:33:31Z
case created — A reported persistent-agent project at OpenAI is a distinct consequential product episode, although no first-party artifact is yet visible.