Key takeaways

  • OpenAI published the Third Moment customer story on October 14, 2026. It reports 10,000 concurrent agents, 36–48-hour autonomous research sessions and one trillion OpenAI tokens consumed in a single day.
  • Third Moment’s disclosed pattern puts Codex inside an outer GPT-6 Sol or GPT-6.1 Sol harness that reviews unfinished trajectories and chooses retry, termination or human escalation. That is a concrete supervision design, not proof that every session remains coherent or useful.
  • OpenAI reports that Codex reduced one order-level US-equity backtest from about three hours to about three to five minutes—a roughly 97% reduction. No code, workload, repetitions, hardware comparison or independent reproduction is published.
  • The public Third Moment site offers a managed OpenAI-compatible endpoint through a contact route, but gives no self-serve plan, price, service level, model catalog, capacity promise or general availability statement for the 10,000-agent research system.
  • Teams evaluating long-running agents should cap tokens, tools, wall time and concurrency; preserve complete trajectories; separate completed work from useful work; and require recovery, security and human-escalation evidence before scaling.
01

OpenAI published the 10,000-agent account on October 14

OpenAI’s October 14, 2026 customer story says Third Moment Research runs 10,000 agents concurrently on investigations lasting 36–48 hours. It names GPT-6 Astra, GPT-6 Sol and GPT-6.1 Sol as reasoning models, Codex as the action harness, and Daybreak as part of security testing. The page also displays one trillion OpenAI tokens consumed in a single day.

This is not a new model or public API launch. It is a provider-published account of one customer’s private system. OpenAI supplies quotes from Third Moment’s founders and describes the architecture, but publishes no system identifier, customer entitlement, capacity reservation, price, service level, aggregate success rate or independent evaluation. The verified news is that the companies disclosed the operating pattern and scale; the reported outcomes remain customer claims.

02

The outer harness decides whether unfinished work continues

Third Moment says quantitative-research agents run the default Codex harness inside Dockerized environments with a terabyte of data, documentation and a repository containing feature engineering, GPU-supported training, trading strategies and simulation modules. Codex can plan, use tools, create objectives, spawn subagents and compact context as work continues.

For agents that stop before finishing, Third Moment places Codex inside an outer harness powered by GPT-6 Sol or GPT-6.1 Sol. The outer layer examines the trajectory and decides whether to retry, terminate or escalate to a human. That is more specific than simply increasing a model’s context window, but the story does not publish the decision prompt, retry ceiling, escalation rate, false-completion rate, checkpoint format or recovery results after process, network or model failures.

03

A 97% backtest reduction is one optimization result, not an agent benchmark

OpenAI says Codex analyzed recorded simulation trajectories, timestamps and the codebase after agents repeatedly polled a slow backtest. It identified caching and memory-packing changes and deployed a fix that reduced a year-long order-level US-equity backtest from approximately three hours to approximately three to five minutes. Comparing three hours with the midpoint of that range yields about a 97.8% reduction, consistent with the page’s displayed 97% figure.

The article does not provide the repository, input size beyond the broad workload description, cache state, hardware, profiling output, patch, correctness checks, number of repetitions or runtime distribution. It also does not separate how much improvement came from caching versus memory packing. Treat this as a customer-reported case result—not evidence that Codex cuts arbitrary backtests, agent runtimes or token bills by 97%.

04

Long duration and token volume do not establish useful autonomy

Third Moment says GPT-6.1 Sol can maintain a coherent computational-research thread across days and is currently its most-used model because it uses fewer tokens while delivering performance similar to Astra. The team also says agents found an unanticipated effect involving non-displayed exchange trades and improved a baseline trading system. OpenAI reports these statements without publishing the strategy, holdout design, statistical tests, transaction costs, leakage controls, deployment status or financial outcomes.

Concurrency, wall time and token consumption measure activity and capacity. They do not measure whether an investigation was correct, novel, reproducible, economical or accepted by a human expert. A one-trillion-token day could indicate productive parallel search, expensive redundancy or both. The evidence needed to tell those stories apart—completed tasks, accepted findings, severe errors, duplicate branches, idle polling, retries and cost per accepted result—is absent.

05

Published token rates are not the system’s total price

OpenAI currently lists GPT-6.1 Sol Standard short-context rates at $2 per million input tokens, $0.10 cached input, $2.50 cache writes and $10 output. Requests above 272,000 input tokens move the full request to higher rates, and Fast, Ultrafast, Batch, Flex and regional processing carry different multipliers. GPT-6 Astra’s documented Standard rates are higher. Those public rates establish a menu, not Third Moment’s bill.

The story does not break the reported trillion tokens into model, input, cached input, cache writes, reasoning, visible output, retries or processing modes. It also omits Codex and tool charges, data and GPU infrastructure, orchestration, storage, security testing and people. Third Moment’s own site currently asks prospective customers to get in touch for a managed OpenAI-compatible endpoint and publishes no price. Buyers should request total cost per accepted research outcome rather than multiplying one token rate by the headline volume.

06

Daybreak is an access program, not proof of containment

OpenAI’s story says Third Moment uses Daybreak to test whether an agent could escape its research environment and reach the wider network before simulations launch. The current Daybreak API guide documents organization and project approval, model permissions and explicit cyber-program selection through access_programs.cyber. It also says selecting a program does not grant access and does not guarantee that every safety check or prompt will succeed.

Neither reviewed OpenAI page publishes Third Moment’s threat model, test corpus, environment boundaries, findings, remediation rate, independent review, residual risk or runtime enforcement. Pre-launch penetration testing can improve assurance, but it does not replace least privilege, network controls, credential isolation, immutable audit records, runtime detection, spend limits and a tested kill switch. The stronger claim—that 10,000 autonomous agents were proven contained—is not supported by the public evidence.

07

Third Moment’s public offer is narrower than the customer-story scale

Third Moment’s current site markets a fully managed, OpenAI-compatible inference endpoint. Its stated process detects recurring failures on approved real traffic, lets the customer confirm which issues to address, builds evaluations, improves the model or harness, and ships a revised endpoint. It says Third Moment operates serving, evaluation design, reinforcement-learning post-training, harness optimization and versioning.

The reviewed page does not promise access to the quantitative-research environment, 10,000 concurrent agents, 36–48-hour sessions or hundreds of thousands of collaborating agents. It provides a contact route rather than self-serve provisioning and does not publish pricing, support, security documentation, data-use terms, regions, models, capacity or service levels. OpenAI describes hundreds of thousands of subagents as Third Moment’s roadmap, not current availability.

08

What teams building long-running agents should do next

Trial one bounded investigation with a frozen question, data snapshot, tool set and acceptance rubric. Set ceilings for concurrent branches, wall time, total tokens, cache writes, external calls and spend. Require each branch to emit a checkpoint, evidence links, unresolved assumptions and a termination reason. Score accepted findings, severe errors, redundant work, human interventions and full cost—not simply duration or task completion.

Constrain the runtime with per-agent identity, deny-by-default network access, scoped credentials, sandbox and egress controls, checkpoint recovery, deterministic approval for consequential actions, and a global kill switch. Wait when the provider cannot show account-specific access, capacity and commercial terms. Reject a scale-up when complete trajectories, correctness gates, incident evidence, rollback and cost per accepted result cannot be produced.

09

Copy-ready long-running agent trial record

Complete one record per investigation type and configuration. Do not treat concurrency, elapsed time or token volume as the outcome.

Entries stay in this browser tab and are not submitted to AccessAllGPT. Blank responses are copied as [Unresolved].

Question, data snapshot, permitted claims, acceptance rubric, expert reviewer, deadline, consequence level and prohibited use.

Model IDs and snapshots, effort, Codex and outer-harness versions, prompts, tools, container image, repositories, data and infrastructure.

Maximum agents and subagents, wall time, tokens by class, cache writes, tool calls, retries, compute, external spend and hard-stop behavior.

Completion test, retry and termination policy, human-escalation triggers, approval boundaries, checkpoint cadence and stale or looping detection.

Attempted, completed and accepted investigations; correctness and reproduction; severe errors; duplicate branches; unresolved findings and reviewer agreement.

Process, network, model and tool failures; checkpoint restoration; malformed state; timeout handling; recovery time; degraded mode and rollback drills.

Threat model, identities, credentials, files, network and egress, sandbox controls, red-team cases, findings, remediation, runtime detection and kill switch.

Input, cache-read, cache-write, reasoning and output tokens by model and mode; tools, compute, storage, security and people; cost per accepted result.

Scale, constrain, repeat, wait or reject; approved ceiling, evidence gaps, accountable owner, expiry and mandatory re-evaluation triggers.

Primary sources

  1. How Third Moment Research runs 10,000 agents for 36+ hoursOpenAI · Reviewed: October 14, 2026 publication date; headline metrics; self-improving-agent description; Codex backtest optimization; Dockerized research environment; outer-harness supervision; model-evaluation claims; Daybreak security-testing description; collaboration roadmap · Retrieved · Supports: OpenAI published a customer story reporting that Third Moment runs 10,000 agents concurrently for 36–48-hour investigations, used Codex to reduce one backtest from about three hours to about three to five minutes, consumed one trillion OpenAI tokens in one day, and uses Daybreak to test research environments before simulations launch.
  2. Third Moment ResearchThird Moment Research · Reviewed: Current product positioning; four-stage detect, confirm, improve and ship process; managed serving, evaluation, post-training, harness optimization and versioning scope; OpenAI-compatible endpoint example; contact route · Retrieved · Supports: Third Moment currently markets a managed OpenAI-compatible inference endpoint that detects recurring failures on approved customer traffic, builds evaluations, optimizes the model or harness, and ships a revised endpoint; the reviewed page gives no public price, service level, model catalog or self-serve access path.
  3. GPT-6.1 Sol model referenceOpenAI Developers · Reviewed: Current model ID; model positioning; 1,050,000-token context window; 128,000-token maximum output; reasoning controls; Responses API tools; Standard, long-context, Fast, Ultrafast, Batch, Flex and regional pricing qualifications; data-residency statement · Retrieved · Supports: OpenAI currently documents gpt-6.1-sol with a 1.05-million-token context window and Standard short-context list prices of $2 input, $0.10 cached input, $2.50 cache writes and $10 output per million tokens; those rates do not reveal Third Moment’s actual mix, discounts, tool charges or total bill.
  4. Use Daybreak in the Responses APIOpenAI Developers · Reviewed: Organization and project approval prerequisites; access_programs.cyber request field; standard, daybreak_blue and daybreak_red options; compatible model table; explicit and omitted defaults; response inspection; validation and authorization errors · Retrieved · Supports: OpenAI documents Daybreak as an approval-gated Responses API access program: request selection does not grant access, project and model permission still apply, and a selected program does not guarantee every safety check or prompt will succeed.

Limitations

This report is a desk review of four first-party or provider-controlled surfaces. AccessAllGPT did not obtain Third Moment or OpenAI accounts, API keys, contracts, capacity allocations, private prices, invoices, token logs, prompts, model traces, agent trajectories, datasets, repositories, patches, containers, orchestration code, evaluations, trading results, security findings, incident records or interviews; run GPT-6 Astra, GPT-6 Sol, GPT-6.1 Sol, Codex or Daybreak; reproduce the 10,000-agent concurrency, 36–48-hour session, one-trillion-token day, three-hour-to-three-to-five-minute backtest change, baseline improvement, token-efficiency comparison, latency benchmark, coherence claim or containment testing; or independently determine whether the system is available to customers. The OpenAI article is a customer story and Third Moment’s page is provider marketing. Products, documentation, prices and access can change.

Disclosures

AccessAllGPT received no OpenAI or Third Moment account, credits, endpoint, output, data, trace, benchmark, security report, briefing, review, payment or compensation for this article. OpenAI and Third Moment Research did not sponsor, review or endorse it. AccessAllGPT did not test, score or rank the models or system. AccessAllGPT Research is operated by NeuralArc, is independent, and is not affiliated with OpenAI, Third Moment Research or organizations cited. Publication-wide relationships are listed on the disclosures page.

Further AccessAllGPT guidance

  1. OpenAI Launches GPT-6.1 Sol
  2. GPT-6 Astra: Its Safety Monitor Cannot Be Your Agent Rollback
  3. Asana Reports a 76× Browser-Agent Cost Cut
  4. Control the Hand-off Between AI Agents and Human Approvers
  5. Design an Agent Benchmark That Predicts Production
  6. AI API Data Retention and Residency Procurement Gates
  7. AccessAllGPT Research methodology
  8. Evidence standards
  9. Publication disclosures

Continue the research

Get evidence-led updates for teams making production AI decisions.