Search for a command to run...
Crafting seamless user experiences with a passion for headless CMS, Vercel deployments, and Cloudflare optimization. I'm a Full Stack Developer with expertise in building modern web applications that are blazing fast, secure, and scalable. Let's connect and discuss how I can help you elevate your next project!
No comments yet. Be the first to comment.
The Codex–ChatGPT Pro dual-agent workflow separates implementation from acceptance; it does not prove that one AI system is the strongest coding agent. Codex can hold the repository, requirements, per
Japan's physical AI strategy entered an execution phase in 2026, with a national model program running through 2030. The government is funding factory-data preparation and robotics foundation models.
The AI infrastructure bubble may stay contained while chips, power, and construction capacity remain scarce. In July 2026, NVIDIA CEO Jensen Huang told Axios that a bubble was highly unlikely within f
Firecrawl gives AI agents a programmable web-context layer for search, extraction, crawling, document parsing, and browser interaction. It can remove a large amount of scraping glue code, but it does
A Codex long-running agent workflow succeeds when responsibility, state, wake conditions, acceptance criteria, and stopping boundaries remain visible and reviewable.
OpenAI developer experience lead Jason Liu recently showed a Codex thread that had been running for five weeks and had coordinated roughly 400 sub-agents. The number is memorable, but it describes compute activity more than organizational maturity. The important result was continuity: after being woken again, the thread still understood its role, consulted prior state, and resumed the same body of work.
That demonstration changes the enterprise question. A pilot asks whether a model can finish one assignment. An operating system for agents must explain how unfinished work survives, what causes another run, who approves irreversible actions, and when the loop must stop.
The workshop used pinned threads for durable responsibilities such as chief of staff work, Agents SDK support, command-line tooling, open-source projects, and feedback. Each thread retained its own history, goal, and automation schedule. Threads could also find, rename, and message other pinned threads when coordination was required.
The durable unit here is a responsibility boundary, not a sub-agent count. A long-running thread needs at least four layers:
| Layer | What must persist | Operational purpose |
|---|---|---|
| Responsibility | One role, its stakeholder, and its allowed scope | Prevent the agent from reconstructing its job after every wake-up |
| State | Facts, decisions, open loops, blockers, and the next action | Let work cross days while remaining reviewable |
| Wake condition | A schedule, event, human message, or retry rule | Control when the system spends resources and makes another decision |
| Acceptance and stop rules | Tests, evidence, approvals, and termination conditions | Keep completion criteria from drifting and loops from running indefinitely |
OpenAI's operating whitepaper describes a compatible design. Pinned threads become a durable home for work, context, decisions, and loops. Memory lives outside the conversation in a form that people can open, edit, diff, and reuse. That external state matters more than a vague claim that the model remembers, because governance requires inspectable records.
Long-lived context is not free. OpenAI warns that long threads may cost more than short ones. Every scheduled heartbeat also reloads state, inspects the environment, and decides whether anything changed. A realistic total-cost model separates at least four categories:
Heartbeat frequency should follow the arrival rate and risk of new information. High-risk events benefit from event triggers and human approval. Low-risk monitoring can use longer intervals. When nothing has changed, the agent should record that fact and end the run.
This is why sub-agent count is a weak productivity metric. Four hundred sub-agents may represent useful decomposition, or 400 attempts without a dependable acceptance test. Better measures include evidence produced per goal, the human takeover rate, the share of wake-ups with no state change, and the amount of rework.
The workshop's most important warning involved tool-path substitution. When a Slack connector could not upload a file, the agent could use computer control instead. When a Gmail connector could not send a message, the agent could open a browser and press Send. A restriction on one connector may fail to restrict the outcome across the complete environment.
This is a boundary-design issue. If an agent can access files, a browser, a terminal, and external services, governance should classify the possible result rather than the named tool.
| Action class | Recommended default | Evidence to retain |
|---|---|---|
| Read, search, and organize | Run automatically inside approved sources | Source list and timestamps |
| Draft and edit local files | Run automatically with a preserved diff | File diff and test results |
| Send externally or publish | Require explicit human approval | Recipients, public URL, and content read-back |
| Delete, pay, or change identity and access | Apply least privilege and dual confirmation | Actor, approver, and immutable audit record |
OpenAI says the Codex app limits file edits to an approved folder or branch by default. Elevated commands, including network access in relevant environments, require permission. Those defaults are useful, yet an enterprise still has to inventory browser sessions, stored credentials, and every alternative path to the same outcome.
Most teams do not need to reproduce the 400-sub-agent example. A stronger starting point is one low-risk, repeatable job with an output that can be verified. Define five fields before the first unattended run:
A first pilot might check a known system each morning, summarize new feedback, or create a reviewable draft after a data change. It should not begin with permission to send email, move money, or publish publicly. After two weeks, inspect four signals: wake-ups with no new information, where human corrections cluster, which evidence can be collected automatically, and which step most often triggers a stop.
If those records are clear, a second thread may be worth adding. If the team cannot explain why the first thread continued after a particular wake-up, more agents will multiply an invisible operations problem.
Adoption has expanded quickly. In April 2026, OpenAI reported more than three million weekly Codex developers. The same update introduced automations that preserve context in an existing thread, then wake automatically over days or weeks. A May update reported more than four million weekly users. In June, OpenAI said Codex had passed five million weekly users, with nondevelopers accounting for roughly 20 percent and growing more than three times faster than developers.
Those vendor figures do not prove return on investment. They do show that the product is moving beyond a narrow coding audience. As agents take on research, operations, design, and cross-tool workflows, responsibility design, approval policy, and audit evidence become part of the buying decision. Model benchmarks become less informative than an organization's ability to keep work safe across time.
If any answer is missing, keep the pilot narrow. The defensible advantage of a long-running agent comes from the operating design and control surface around it.
No. A safer design preserves the thread's responsibility and state over time, then wakes it through a schedule, event, or human message. Each run still needs a completion condition, time limit, and stop rule.
No. It was a cumulative count in one workshop example, not a reference architecture. Most teams should validate one low-risk loop before scaling.
Operational state should live in files or systems that people can open, edit, version, and audit. Conversation history can add context, but it should not be the sole record.
An agent may reach the same outcome through another tool. Controls should cover result classes such as send, upload, delete, and pay across every available path.
Choose a low-risk task with a regular cadence, known inputs, and a result that a test or data read-back can verify. Work involving publication, financial transactions, or sensitive data needs approval and audit controls first.
In Tenten's content publishing, data monitoring, and development-agent workflows, completion is split into evidence that can be read back: public URLs, API state, file diffs, and test results. A common failure is treating long execution as durable responsibility. Without state files, approval points, and stop rules, a team cannot tell whether an agent is advancing the work or repeatedly consuming resources.
