Seventeen days
On November 30, 2026, OpenAI shuts down Agent Builder, its visual tool for agent workflows. That is 17 days from today. OpenAI gave notice on June 3, 2026, on its deprecations page. The notice also covers the Evals platform and reusable prompts.
I start with that date because it tells you how this market works. OpenAI ships agent products quickly, and it retires them quickly. A guide to open AI agents is useful only if it carries the date on which the writer checked the names. I checked every name and price in this guide on November 13, 2026.
The phrase itself needs one note. People type "open AI agents" as three words. The company writes its name as one word, OpenAI. Some people mean open source agents instead. This guide covers the products of OpenAI. For the open source frameworks, read my comparison of agent orchestration frameworks.
I am Chris Machetto. I run Frenchy Digital, a software agency that started in 2016. We build agents for clients on several model providers, and OpenAI is one of them. That gives me a commercial interest, so I show the arithmetic and I give the source of each number.
This is the order. First, a map of each current product. Second, the idea that most owners get wrong. Then the ChatGPT products, the API products, the products that OpenAI retired this year, the prices and a decision table. The guide ends with what fails first, a boundary table, the limitations and three tasks for this week.
The map of OpenAI agent products
This table is the whole guide in one place. Each row is a product that exists on November 13, 2026, or one that ends this month. The status column is the part that changes most.
| Product | Who uses it | Where it runs | How you pay | Status on November 13, 2026 |
|---|---|---|---|---|
| ChatGPT Work | Staff in any company | Inside ChatGPT: the desktop app, the web and mobile | A ChatGPT plan; usage counts against the plan | Launched July 9, 2026 |
| Workspace agents | Teams on Business, Enterprise and Edu plans | In the cloud, inside ChatGPT, with schedules and Slack triggers | Credits from the workspace pool since July 6, 2026 | Launched April 22, 2026 |
| Codex | Developers | CLI, IDE extension, cloud, desktop app, GitHub | A ChatGPT plan, or an API key at token rates | Active; the CLI is open source |
| Responses API | Developers who write their own loop | Your code calls the API | Tokens plus tool calls | Recommended for all new projects |
| Agents SDK | Developers who want the loop written for them | Your application, in Python or TypeScript | Tokens plus tool calls; the library is free | Updated April 15 and May 6, 2026 |
| Agents API | Developers who want OpenAI to run the harness | OpenAI runs the harness; OpenAI hosts the sandbox, or you do | Tokens, tools and container time; no extra fee | Public beta since September 10, 2026 |
| ChatKit | Teams that need a chat window in their app | Your front end, in React or plain JavaScript | No separate fee on the page | Available |
| Agent Builder | No-code builders | The OpenAI dashboard | Not relevant now | Shuts down November 30, 2026 |
| Frontier | Large enterprises | Managed by OpenAI | Price not public | Limited availability since February 5, 2026 |
Two names are not in the table. OpenAI retired ChatGPT agent, the virtual computer that it launched in July 2025. The Atlas browser shut down on August 9, 2026. Both get their own rows in the section on retired products.
One more product belongs to this story. OpenAI announced Frontier, an enterprise agent platform, on February 5, 2026. The announcement page did not open for me today. A secondary report from February 13, 2026 describes limited availability for selected enterprise customers, and no public price. I give it one paragraph and no more, because I cannot verify more.
The wrong idea: one OpenAI agent
Most owners think that OpenAI sells one agent. You pay for it, you connect it to your systems, and it works. Vendors and headlines make that idea reasonable.
The real picture has two stacks, and they bill in different units. The ChatGPT stack is for your staff. You pay a seat price each month, and the agent works inside ChatGPT with the apps that an admin connected. The API stack is for your developers. You pay for tokens and tool calls, and the agent works inside software that you own.
The two stacks share models and tools, but they do not share a product. A workspace agent cannot run inside your customer app. An Agents SDK agent cannot appear in the ChatGPT window of your staff. When a vendor says "we use OpenAI agents", ask which stack.
The definition is the same on both stacks. It comes from the OpenAI guide for product teams.
Agents are systems that independently accomplish tasks on your behalf.
OpenAI, A practical guide to building agents
The guide lists three parts: a model, tools and instructions. I used that definition in my guide to AI agents for business, and it applies here. The product decides where the three parts live and who pays for them.
The ChatGPT stack
Three products live inside ChatGPT today: ChatGPT Work, workspace agents and Codex. Each one replaced something that came before it, so I give the history in a few lines each.
ChatGPT Work: the agent for one person
OpenAI launched ChatGPT Work on July 9, 2026, together with the GPT-5.6 models. Engadget described it as "something of a general purpose productivity agent". You give it a goal. It reads your connected apps and files, works in steps, and returns a spreadsheet, slides, a document or a small web app. It can run on a schedule, and you can start a task on your phone and check it later.
On the same day, OpenAI merged the Codex desktop app into a new ChatGPT desktop app with three modes: Chat, Work and Codex. The Neuron reported that the three modes are available in the desktop app on every plan, including Free. On the web and on mobile, Work reached Pro, Enterprise and Edu accounts first, then Plus and Business.
Work is the successor to ChatGPT agent. OpenAI launched ChatGPT agent on July 17, 2025, as an upgrade to Operator, with a virtual computer and a visual browser. 9to5Mac reported 400 queries a month on Pro and 40 on Plus at launch. In summer 2026 OpenAI retired it.
The retirement left a trace on the developer forum. A user wrote on August 8, 2026 that OpenAI removed agent mode and told users to use Work. OpenAI support answered on September 7 that "Work now has a separate cloud browser that can navigate interactive sites". The browser can pause for a sign-in or a takeover on supported accounts.
The desktop app also has a browser with multiple tabs. That browser replaced ChatGPT Atlas, the standalone browser that OpenAI launched for macOS on October 21, 2025. The Wikipedia entry on Atlas, which cites Lifehacker and TechRepublic, gives August 9, 2026 as the shutdown date.
Workspace agents: the agent for a team
OpenAI launched workspace agents on April 22, 2026, as a research preview for Business, Enterprise, Edu and Teachers plans. The Decoder reported that OpenAI calls them an evolution of GPTs. Codex powers them. They run in the cloud, on a schedule or from a Slack message, and they keep working when the user is offline.
The admin controls are the reason that I prefer them to a personal agent for team work. Techstrong.ai reported that administrators define what data and systems agents can access. A sensitive action, such as a sent message or a changed record, can require approval. Enterprise admins get a Compliance API and can pause an agent.
The price changed in July. The preview was free. Credit-based pricing took effect on July 6, 2026, according to a report that cites the OpenAI rate card. The same report says that there is no fixed credit cost for a run. Measure ten runs before you promise a budget.
If you considered a no-code builder for this job, read my guide to no code AI agents first. Workspace agents are the no-code option inside OpenAI now, because Agent Builder ends this month.
Codex: the agent for developers
Codex is the coding agent. The Codex documentation lists six places where it runs. They are the ChatGPT desktop app, the mobile app, the web, the Codex CLI, the IDE extension and Codex Cloud. It connects to GitHub, to GitLab in beta, to Slack and to Linear.
The command line tool is open source. The repository describes it as "a coding agent from OpenAI that runs locally on your computer", under the Apache-2.0 license. OpenAI recommends sign-in with a Plus, Pro, Business, Edu or Enterprise plan. An API key also works, and then you pay token rates.
The history is short. OpenAI released the CLI on April 16, 2025. The cloud agent followed as a research preview on May 16, 2025. Both dates come from the Wikipedia timeline, which cites TechCrunch and Wired. The desktop app arrived in February 2026 and merged into the ChatGPT app on July 9, 2026.
The plan prices come from the ChatGPT pricing page on November 13, 2026.
| ChatGPT plan | Price on November 13, 2026 | Agent products in it |
|---|---|---|
| Free | $0 | Chat, Work and Codex modes in the desktop app, with limits |
| Go | $8 a month | The same modes, for light use |
| Plus | $20 a month | Work on the web and mobile; Codex on the web, CLI, IDE extension and iOS |
| Pro | $100, $200 or $500 a month | Everything in Plus, with no five-hour limit |
| Business | $20 a user a month on an annual plan; $25 monthly | ChatGPT and Codex for each user, plus workspace agents on credits |
| Enterprise and Edu | Contact sales | Everything in Business, with admin controls and credit pools |
One detail on Plus matters for an agent. The page gives an estimate of 15 to 160 GPT-6.1 Sol messages in each five-hour period, and weekly limits can apply. A long Work task uses more of that allowance. Pro plans have no five-hour limit, and that is the reason that a heavy user pays $100 or more.
The API stack
The API stack has three layers, and the OpenAI guide to building agents separates them the same way. The Responses API is the model call. The Agents SDK is a loop that runs in your code. The Agents API is a loop that OpenAI runs for you.
The Responses API: the model call with tools
The Responses API is the interface that OpenAI recommends for new work. Its migration guide says: "While Chat Completions remains supported, Responses is recommended for all new projects." A request can call the model and hosted tools in one turn. The answer comes back as a typed list of items.
The hosted tools are the reason that it counts as an agent product. The tools guide lists function calling, web search, remote MCP servers, skills, shell, computer use, image generation, file search, tool search and programmatic tool calling. The Assistants API, the older hosted option, shut down on August 26, 2026. Its migration guide says that runs moved to Responses and that threads moved to the Conversations API.
The Agents SDK: the loop in your code
The Agents SDK is a library for Python and TypeScript. Its documentation names three primitives. Agents are "LLMs equipped with instructions and tools". Handoffs let an agent delegate to another agent. Guardrails validate inputs and outputs. Sessions keep the working context, and the SDK includes tracing.
The 2026 update changed its scope. On April 15, 2026, OpenAI added sandboxed execution, a harness and memory controls. On May 6 the same features reached TypeScript, according to the API changelog. Help Net Security reported built-in support for seven sandbox providers: Blaxel, Cloudflare, Daytona, E2B, Modal, Runloop and Vercel. A sandbox agent gets files, a shell and a patch tool. In the words of the sandbox guide, it "is still an Agent".
The important sentence in the SDK overview is this one: "The Agents SDK runs in your application; the Agents API runs a managed harness in OpenAI's service." With the SDK, your server owns the tools, the storage and the approval decisions. That is the product that I select for the software of a client.
The Agents API: the loop that OpenAI runs
The Agents API entered public beta on September 10, 2026. The changelog entry says: build agents with a managed Codex harness while OpenAI handles session orchestration. The overview says that OpenAI "manages sessions, orchestration, context compaction, and recovery". You supply the task, the model, the tools and the environment.
The environment is a sandbox. OpenAI can host it, you can run it yourself, or a partner can run it. VKTR reported nine sandbox partners at launch: Blaxel, Cloudflare, Daytona, DigitalOcean, E2B, Modal, Oracle, Runloop and Vercel. There is no fee for the API itself. You pay for tokens, tools and hosted container time.
Since the launch, OpenAI added computer use in a hosted browser on September 29, scheduled automations on October 23, and automatic review on October 30. Automatic review means that a model approves or denies tool requests in eligible projects. I treat that as a help for a person, not as a replacement.
Read the data controls before a pilot. The overview says that the Agents API "currently supports data residency only in the United States and does not support Zero Data Retention (ZDR)". A self-hosted sandbox does not change that. For a client in Europe, or for a healthcare client, that sentence decides the product.
ChatKit: the chat window
ChatKit is the smallest product in the stack. The guide says that it "provides a customizable chat embed to handle all user experience details". You put it in a React app or a plain page, and it connects to a service that you built with the Agents SDK. The same guide carries the Agent Builder notice and says: "ChatKit is still available."
What OpenAI retired this year
This section exists because of the hook. In the twelve months before today, OpenAI retired or scheduled the end of eight agent products or models. The table gives the dates from the deprecations page and from the reports that I name above.
| Product | What it was | What happened | Where OpenAI points you |
|---|---|---|---|
| Operator | A browser agent in ChatGPT | ChatGPT agent replaced it in July 2025 | ChatGPT Work |
| ChatGPT agent, also called agent mode | A virtual computer with a visual browser, from July 2025 | Retired in summer 2026; secondary sources report that the help page says it is no longer available | ChatGPT Work |
| ChatGPT Atlas | A browser for macOS, from October 2025 | Shut down on August 9, 2026 | The browser in the desktop app, and a Chrome extension |
| Assistants API | The first hosted agent API | Shut down on August 26, 2026 | Responses API and Conversations API |
| Agent Builder | A visual canvas for agent workflows | Shuts down on November 30, 2026 | Agents SDK or workspace agents |
| Evals platform | A hosted test dashboard and API | Read-only; shuts down on November 30, 2026 | Promptfoo |
| Reusable prompts | Prompt objects at /v1/prompts | Shut down on November 30, 2026 | Your own application code |
| computer-use-preview | The first computer use model | Shut down on July 23, 2026 | gpt-5.6-terra, and the computer tool on newer models |
The pattern is clear. OpenAI consolidates. Operator became ChatGPT agent, which became ChatGPT Work. Atlas became a browser inside the desktop app. The Assistants API became the Responses API and the Conversations API. Agent Builder becomes the Agents SDK or a workspace agent.
The notice periods differ. The Assistants API got twelve months. Agent Builder, Evals and the prompt objects got about six months. ChatGPT agent, a consumer product, got less, and users on the developer forum said that they got no notice.
That difference is useful. An API product gives you time to move. A ChatGPT product can change on a Tuesday.
The Evals shutdown has a lesson of its own. OpenAI points users to Promptfoo, and a detailed report on the shutdown says that OpenAI now describes Promptfoo as part of OpenAI. New runs there are separate from the old ones. If your tests lived in the dashboard, export them now. I explain a test set that you own in AI agent evaluation and observability.
What it costs, with the arithmetic
Each price below is a list price that I read on November 13, 2026. The ChatGPT stack bills in seats and credits. The API stack bills in tokens, tool calls and container time. Keep the units apart.
Start with tokens. Assume that one support conversation uses about 20,000 input tokens and 2,000 output tokens. That is a scenario, not a measurement of your traffic. The prices come from the OpenAI pricing page.
| Model, list price on November 13, 2026 | Input per 1M tokens | Output per 1M tokens | One scenario conversation |
|---|---|---|---|
| GPT-6 Luna | $0.10 | $0.50 | About $0.003 |
| GPT-6.1 Terra | $1 | $5 | About $0.03 |
| GPT-6.1 Sol | $2 | $10 | About $0.06 |
| GPT-6 Astra | $10 | $50 | About $0.30 |
Calculate the Sol row by hand. 20,000 input tokens at $2 for each million cost $0.04. 2,000 output tokens at $10 for each million cost $0.02. The total is six cents. On GPT-6 Luna, the same conversation costs about a third of a cent.
Tools add small amounts. The same page lists them.
| Hosted tool | List price on November 13, 2026 | What that means |
|---|---|---|
| Web search | $10 for 1,000 calls, plus the content tokens at model rates | One cent a search |
| File search | $2.50 for 1,000 calls; storage $0.10 a GB a day after the first GB | A quarter of a cent a search |
| Code interpreter container | $0.03 for a 20-minute session at 1 GB | Three cents each time the agent runs code |
| Computer use | No separate line; tokens, and each screenshot counts as image input | The screenshots are the cost |
| Agents API | No extra fee; tokens, tools and hosted container time | The same meter as the rows above |
Put the two together. A conversation on GPT-6.1 Sol with two web searches costs about eight cents before the search content tokens. One thousand such conversations a month cost about $80. The model is not where your money goes.
Now the ChatGPT stack. Ten people on Plus cost $200 a month. Ten people on Business cost $200 a month on an annual plan, or $250 on a monthly plan. Workspace agents then draw credits from the pool of the workspace, and the rate card gives no fixed cost for a run.
This is our own price, because I can confirm it. A custom agent from Frenchy Digital costs $5,000 plus a $5,000 setup fee, so $10,000 to start. After launch it costs $2,500 a month. Year one is $40,000 plus usage, and each later year is $30,000 plus usage. You pay the usage to OpenAI directly, and the tables above show that it is small.
Three years of a custom agent cost $100,000, which is about $2,778 a month. Compare that with ten Business seats at $200 a month. The custom agent is worth the difference in two cases. The agent must live inside your product, or it must follow rules that a workspace agent cannot hold. If your company is in New York, our team for AI agent development in New York can run that comparison with your numbers.
Which product fits which task
This is the table that I use on a discovery call. The left column is the task as the owner describes it. The middle column is the product that I would start with, not the only option.
| The task | The product that I would start with | Why |
|---|---|---|
| One person wants a report, a slide deck or a spreadsheet from company files | ChatGPT Work | It is in the plan that you pay for, and a person watches it |
| A team wants the same task each week, on a schedule or from Slack | Workspace agents | Admin controls and approvals exist, and no code is necessary |
| A developer wants a bug fixed or a feature written in a repository | Codex | It is the coding agent, in the terminal, the IDE or the cloud |
| Your product needs an agent inside it, with your own tools and rules | Agents SDK | The SDK provides the loop, and your code owns the tools and the approvals |
| A task needs files, commands and hours of work, and you do not want to run the sandbox | Agents API | OpenAI runs the harness and keeps the session |
| You need one model call with a web search or a file search | Responses API | No agent framework is necessary |
| You need a chat window in your app this week | ChatKit | The embed exists, and it connects to your Agents SDK service |
Two rules sit behind the table. First, the OpenAI guide says: "Our general recommendation is to maximize a single agent's capabilities first." One agent with good tools beats three agents with handoffs, until the prompt holds too many branches. Second, the Anthropic guide on agents gives the same advice from the other side. It recommends "finding the simplest solution possible". Both companies sell models, and both tell you to start small.
The OpenAI guide also gives three signs that a task fits an agent at all. The signs are judgment on exceptions, rules that are too complex to maintain, and unstructured material. If a task shows none of the three, "a deterministic solution may suffice". A form and a rule cost less than any product in this article.
One real project, one scenario
The project that I can show in public is the Wisdom Tooth Clinic in Miami, an oral surgery practice. We built a platform with four agents: scheduling, insurance and eligibility, intake and consent, and recall. The voice line runs on Retell. OpenAI is in the stack for one narrow job.
The case study says what that job is. Intake summaries go to OpenAI server-side, with the name of the patient stripped, under a business associate agreement. The model only summarizes. Deterministic code evaluates the warning signs in the medical history, such as anticoagulants or cardiac history. The model does not decide.
Two more details apply to any OpenAI agent. The scheduling agent books through signed, opaque offer identifiers, so the model never sees or invents a raw time slot. And the agent is not allowed to quote a price, because a Florida dental advertising statute makes an all-inclusive fee claim non-compliant.
I will not quote a result from that project. The practice opened only recently, and the case study says that the acceptance gates are not yet measured. What I can say is that the platform went from first commit to live booking in 31 days.
Now a scenario, with invented inputs. Consider an accounting firm with 15 people. Each Monday, a senior accountant spends about three hours on a report. The report pulls numbers from a practice management system and a shared drive. The firm wants an agent for that report.
- Route one: a workspace agent on ChatGPT Business. Ten seats at $20 a month on an annual plan are $200 a month. The agent runs each Monday on a schedule and posts the draft to Slack. The credits for four runs a month are not fixed, so the firm measures them.
- Route two: an Agents SDK build inside the portal of the firm. At our prices, $10,000 to start and $2,500 a month. Three years cost $100,000, or about $2,778 a month.
- The difference is about $2,578 a month, before credits. At a loaded cost of about $75 an hour for the accountant, three hours a week are about $975 a month.
I tell that firm to start with the workspace agent. Route two pays only if the report must go into a client portal, or if the data cannot go into ChatGPT at all. Both conditions are possible. Neither is the default.
What fails first
Five failures occur frequently enough that you must plan for them. For each one, the table shows how you see it and what limits the damage.
| The failure | How you see it | What limits the damage |
|---|---|---|
| The product changes under you | A deprecation notice with a shutdown date about five months out | Keep tools, prompts and rules in your own code; export on the day of the notice |
| The agent reads a page that gives it orders | Unusual actions after a web search or a browser step | Treat screen and page content as untrusted; approval before each write; an allow list of sites |
| The sandbox is less isolated than you think | The agent reaches files or networks outside the task | Docker or a hosted provider for untrusted commands; credentials outside the sandbox |
| Data goes where your contract forbids | A regulated data set in a service with no residency option | Read the data controls page before the pilot; use the SDK in your own region if necessary |
| Usage costs grow with the task | A Work task that uses a large part of the plan allowance in one day | Hard spend limits in the API; one task at a time in ChatGPT until you know the cost |
The first row is the one that this guide is about. Agent Builder got a notice on June 3 and ends on November 30. The export does not convert the workflow graph. A team that kept its logic in the canvas now rebuilds it in code, in 17 days or less.
The second row has no complete solution. OWASP puts prompt injection first on its Top 10 for LLM applications. The OpenAI computer use guide says: "Computer use can affect real accounts and data." It also says: "Treat screen content as untrusted." Those two sentences come from the seller. Read them as a warning label. I explain the controls for browser agents in computer use agents and browser automation.
The third row comes from the SDK documentation itself. The sandbox guide says: "The backend determines which isolation controls apply; a session does not itself guarantee OS-level confinement." The local client on Linux adds no confinement at all. Use Docker or a hosted provider for commands that the model writes. Keep credentials outside the sandbox. The April update separates the harness from the compute layer for that reason.
The fourth row is the Agents API sentence on data residency. I repeat it because it is easy to miss on a quickstart page. United States only, and no Zero Data Retention.
The fifth row is new in 2026. Work bills against your plan allowance, and a long task uses more of it. On the API, set a hard spend limit for the project before the first run. The changelog says that OpenAI added hard spend limits for organizations and projects on July 22, 2026.
What an agent may do alone
Complete this table before you switch on any product in this guide. It takes about an hour. The rows are the four places where an OpenAI agent can act.
| Area | May act alone | Needs approval from a person | Must never touch |
|---|---|---|---|
| ChatGPT Work for staff | Drafts, research, summaries of company files | Any email or message that leaves the company | Payments, contracts, decisions about people |
| Workspace agents | Scheduled reports, ticket triage, drafts in Slack | Record changes in a CRM or a ticket system | Customer data outside the admin allow list |
| Codex | Code changes on a branch, tests, pull request drafts | Merges to the main branch, dependency changes | Production databases, secrets, deploy keys |
| Agents SDK or Agents API | Read-only tools, searches, file edits in a sandbox | Each write tool, each payment, each outbound message | Credentials inside the sandbox; data outside the agreed region |
Each product has a feature for the middle column. ChatGPT Work pauses for a sign-in or a takeover. Workspace agents let an admin require approval for a sensitive action. The TypeScript SDK has a human-in-the-loop guide and guardrails. The Agents API has automatic review, where a model approves tool requests. I would still keep a person on each write.
The OpenAI guide names the two triggers for a person. The first is a failure threshold, such as an agent that fails to understand a customer after several attempts. The second is a high-risk action. The examples in the guide are "canceling user orders, authorizing large refunds, or making payments." Put those three in the right column on day one.
Warning signs when a vendor says OpenAI agents
These are the signs that tell me not to buy, from a product or from a builder, and that includes us.
- The vendor names a product that no longer exists. OpenAI retired Operator, ChatGPT agent and the Assistants API, and Agent Builder ends this month. A proposal dated this month that builds on them is out of date.
- The vendor cannot say which stack. Ask: does the agent run inside ChatGPT or inside our software? If the answer is unclear, the price is unclear too.
- An accuracy or deflection rate with no method. In this market, the seller publishes each such figure. Ask for the test set.
- No test set at all. The Evals platform ends on November 30. Ask where the tests live now.
- A quote before the vendor asks what the agent must read and write. The integration is the cost, not the model.
- Data terms in one sentence or less. For the Agents API, ask about residency and retention. For a workspace agent, ask which connectors the admin allowed.
- Security badges with no report. Ask for the document, not the logo.
- A contract with no exit: no source code, no export, no end date.
On the seventh point, this is our own position. Frenchy Digital signs business associate agreements with healthcare clients. We hold no SOC 2 or ISO 27001 attestation. If your procurement process requires one, a vendor that has it will pass and we will not.
Limitations
This is what I did not verify, or decided not to use as evidence.
- Every page on openai.com and help.openai.com answered 403 to my requests on November 13, 2026. I cite only pages that loaded. Those are the developer documentation, the ChatGPT documentation, the SDK documentation, the GitHub repository, the PDF guide and the reports that I name.
- The status of ChatGPT agent comes from two secondary sources. One is a tool directory that read the help page on August 30, 2026. The other is a support reply on the developer forum. I did not read the help page myself.
- The Frontier facts come from one secondary report of February 13, 2026. I use only the launch date, the limited availability and the absence of a public price.
- The general availability date of workspace agents and the current credit rates are on OpenAI help pages that I could not open. I use the July 6, 2026 pricing date from a report that cites the rate card.
- The nine sandbox partners of the Agents API come from a trade report. The overview page that I read does not name partners.
- Each price is a list price on November 13, 2026. OpenAI changes prices, and the promotional prices on the page have end dates.
- The token scenario and the accounting firm scenario are arithmetic on assumed inputs, not measurements.
- The OWASP site shows its 2025 list as current, and some security firms describe a 2026 edition with a different order. I state only that prompt injection is first, which is true in both.
- I did not verify the first release dates of the Agents SDK and the Responses API today, so I do not print them.
Three tasks for this week
- 1.Open the OpenAI deprecations page. Search it for each product name in your current proposals and contracts. Write down each shutdown date that you find.
- 2.Decide who the first agent works for: your staff, your customers or your product. That answer selects the stack, and the stack selects the price unit.
- 3.If the answer is your staff, switch on ChatGPT Work or a workspace agent for one task, in a plan that you pay for now. Measure ten runs before you decide anything else.
If you complete those three tasks and want a second opinion on the stack, book a discovery call with us. If the ChatGPT stack is enough, I will tell you.
Start with the deprecations page.
Which OpenAI Product Fits Your Task?
Book a discovery call with Frenchy Digital, a senior-led, Black-owned agency in Los Angeles. Bring the task and the list of systems that it touches. If ChatGPT Work or a workspace agent is enough, we will tell you. If you need an agent in your own software, you get a fixed-price proposal.
Which Stack Do You Start With?
Book a discovery call. Bring the task and the list of systems that it touches. We will tell you whether the ChatGPT stack is enough, or whether you need an agent in your own software.
1517 S Bentley Ave Suite 204, Los Angeles CA 90025
Frequently Asked Questions
Sources & References
- 1OpenAI developer documentation: deprecations (Assistants API, Agent Builder, Evals, reusable prompts, computer-use-preview)↗
- 2OpenAI developer documentation: API changelog (Agents SDK April 15 and May 6, 2026; Agents API September 10, 2026)↗
- 3OpenAI developer documentation: API pricing (models and hosted tools)↗
- 4OpenAI developer documentation: Building agents (Agents API, Agents SDK, Responses API, ChatKit)↗
- 5OpenAI developer documentation: Agents SDK overview↗
- 6OpenAI developer documentation: Agents API overview↗
- 7OpenAI developer documentation: Migrate to the Responses API↗
- 8OpenAI developer documentation: Assistants migration guide↗
- 9OpenAI developer documentation: Using tools (hosted tools in the Responses API)↗
- 10OpenAI developer documentation: Computer use↗
- 11OpenAI developer documentation: ChatKit↗
- 12OpenAI Agents SDK, Python documentation↗
- 13OpenAI Agents SDK, Python documentation: sandbox agent guide↗
- 14OpenAI Agents SDK, TypeScript documentation↗
- 15ChatGPT documentation: pricing (Free, Go, Plus, Pro, Business, Enterprise and Edu)↗
- 16ChatGPT documentation: Codex↗
- 17GitHub: openai/codex, Codex CLI repository (Apache-2.0)↗
- 18OpenAI: A practical guide to building agents (PDF)↗
- 19Engadget: OpenAI releases a new ChatGPT tool for all things work related (July 9, 2026)↗
- 20The Neuron: GPT-5.6 and the new ChatGPT desktop app, complete guide (July 10, 2026)↗
- 219to5Mac: ChatGPT can now browse and perform web-based tasks for you (July 17, 2025)↗
- 22OpenAI Developer Community: Agent Mode was removed with no real replacement (August 8, 2026, with an OpenAI support reply of September 7, 2026)↗
- 23The Rundown: ChatGPT Agent is no longer available, its successor (status checked August 30, 2026)↗
- 24Wikipedia: ChatGPT Atlas (launch October 21, 2025; shutdown August 9, 2026)↗
- 25The Decoder: OpenAI launches workspace agents in ChatGPT (April 22, 2026)↗
- 26Techstrong.ai: OpenAI debuts workspace agents to extend ChatGPT into enterprise workflows (April 23, 2026)↗
- 27Kommunicate: ChatGPT workspace agents, pricing and controls (updated July 8, 2026)↗
- 28Help Net Security: OpenAI updates Agents SDK, adds sandbox for safer code execution (April 16, 2026)↗
- 29VKTR: OpenAI launches managed Agents API for cloud-based agents (September 11, 2026)↗
- 30Hidekazu Konishi: Before Agent Builder, Evals and reusable prompts shut down (October 20, 2026, updated November 7, 2026)↗
- 31Wikipedia: OpenAI Codex, timeline of the CLI, the cloud agent and the desktop app↗
- 32NxCode: OpenAI Frontier, enterprise AI agent platform guide (February 13, 2026)↗
- 33Anthropic: Building effective agents (December 19, 2024)↗
- 34OWASP GenAI Security Project: Top 10 for LLM applications↗
Related Articles You May Find Helpful
- AI Agents for Business: What They Do, What They Cost, How to Start
- AI Agent Orchestration Frameworks Compared: LangGraph, CrewAI, Claude Agent SDK, OpenAI Agents SDK
- No Code AI Agents: What They Can Do and When to Move to Code
- Computer Use Agents and Browser Automation in 2026
- AI Agent Security: 10 Controls Before You Connect Your Data

