Try it with your materials
A folder is your agent’s desk
Your agent needs context: the information needed for the task. Instead of describing your company every time, prepare one folder with a company brief, a task brief and photos. Point to it again for the next task and check that the agent read the right files.
01 · Choose the location
In local Codex, select the project folder. For a cloud task, attach files or provide the repository. Check the visible file list.
02 · Supply context
Ask it to read the company brief and task brief, and inspect the specified photo. Request a summary and questions before work begins.
03 · Review the result
Save drafts in output/. Compare them with the photo, offer and goal. A finished ad still needs your review.
my-campaign/
Select a file to see its role and contents.
COMPANY_BRAIN.md
Approved facts: what the company does, its offer, audience, websites and voice.
# Company Brain Updated: [date] | Owner: [person] ## Company Name: [name] What we do: [one sentence] Where we operate: [area] ## Services [service, scope, source of current pricing] ## Customers [who we help and what problem we solve] ## Official links Website: [URL] Services: [URL] Contact: [approved contact] ## Brand voice [three examples of how we write] ## References and evidence [case studies, approved claims, logo and photo paths] Photo usage rights: [source and scope] ## Unknowns [missing information, person responsible] Never invent prices, results, testimonials or product details.
Example: an ad from your photo
Add your product or project photo to references/ and record usage rights. In the brief, name the service, audience, format and elements that must stay unchanged. An advertising skill can structure the process; an available image tool can create the visual. Without that tool, the deliverable is a brief and prompt, not a generated image.
Work in the campaign folder I selected or attached. First list the files you can access. Read AGENTS.md, COMPANY_BRAIN.md and brief.md. Inspect the exact reference photo named in the brief; if it is missing or unreadable, ask for it. Summarise the company, audience and goal, and list missing information. Propose a plan before creating materials. Check available tools: do not claim to have generated an image without using an image tool. Save drafts in output/ and list the files created. Do not alter originals or publish anything.
PL/EN templates, without photos or customer data. Unzip, fill the placeholders and add your own files.
Next: build your Company Brain in lesson 15What Codex is, without the jargon
Codex is an agent that works on a project, most often one with code. It can read files, change them, run commands and tests, and then show exactly what it did. It runs in the ChatGPT desktop app, in a terminal, in a code editor and in the cloud. It shares the same account limits as ChatGPT Work.
If you do not write code you do not have to start with Codex: for documents, spreadsheets and decks, Work is simpler. Codex becomes useful when someone technical is on your team, or when you want to understand how their work looks from the inside.
Six terms that are enough to start
- Repozytorium / Repository
- A project folder together with the history of every change. Like a document folder where every version is kept.
- Diff
- A view of differences: what was removed and what was added. Like “track changes” in a word processor, but for project files.
- Test
- An automatic check that a feature still works. A “green” test means the check passed, not that the program is free of bugs.
- Pull request / Scalenie
- A bundle of changes submitted for review. Merging approves it and adds it to the main version of the project.
- Uprawnienia / Permissions
- Settings that say what the agent may do on its own and what it must ask about. Start cautious and widen them once you trust the results.
- AGENTS.md
- A file with rules for the agent in a given project, e.g. how to run tests and what not to touch. Read at the start of work.
A safe cycle for one task
Goal in one sentence
“Fix the rounding bug in the price function.” One goal per task. Two goals are two tasks.
Scope
Name the files or folder and say what must not be changed (e.g. configuration, customer data).
How we will check
Give the test command or describe the expected result. Without it, “done” only means the agent says so.
Watch and approve requests
When the agent asks permission for a command or a change outside scope, read exactly what it will do before you click.
Review changes before merging
Open the diff, read every change and check the test result. The decision to merge always belongs to a person.
Example prompt (fictional project)
The project has a bug: the formatPrice function in [path] rounds a price to one decimal place instead of two. Goal: fix it and add a test that catches it. Scope: change only [function file] and [test file]. Do not touch configuration or other files. Check: run [test command] and show me its output. Stop after the changes and show me the diff for review. Do not merge or send anything.
Notice that the prompt has a goal, a scope, a way to check and a place to stop. These are the same elements you know from Work, written more precisely.
How to read a diff
A fictional one-line change. A line with − was removed, a line with + was added. The signs matter more than the colours, because colours are not seen the same by everyone.
function formatPrice(cents) {− return (cents / 100).toFixed(1);+ return (cents / 100).toFixed(2);}
We read it like this: instead of one decimal place (toFixed(1)), formatPrice now returns two (toFixed(2)). A price of 12.5 becomes “12.50” rather than “12.5”. If the diff contains changes beyond what the task covered, ask the agent why it made them.
Five questions before you approve
- Do the changes touch only the files in the task? Extra files need an explanation.
- Was the test actually run and did it pass, or did the agent only say it would? Ask for the command output.
- Was anything deleted? Read deletions most carefully.
- Were new libraries or configuration changes added? Ask why.
- Are there any passwords, keys or customer data in the changes or the chat? Never paste them into a prompt.
What if I have no code project?
Ask a technical colleague for a small, unimportant practice project, or do the exercise in Chat: paste the fictional function from the diff above and ask for an explanation of what changed and how to check it. The point is not to write code but to build the habit: goal, scope, check, review.
Lesson 07 - ChatGPT Work and Codex in practice
Limits, optimization and the Enterprise tier
Below are limits, working practices and questions for your administrator. Update history is in a separate expandable section.
1. What the limits are
Context window
ChatGPT Work doesn't "remember" infinite pages at once (see Lesson 03 on tokens). Split big tasks into smaller packets with a clear goal and named files.
Usage limits
Every plan has an agent-work pool refreshed on a cycle - higher plan = bigger pool. When it runs out, ChatGPT Work tells you plainly and when it returns.
Parallel tasks
How many tasks can run in parallel depends on the plan. In a company, set a queue: urgent, can-wait, and who approves outputs before send.
File access
File scope depends on where the work runs: in the cloud it is uploaded files and connected tools, locally only what you approve on your computer. This is a safeguard, not a limitation. Keep each project in a dedicated folder.
2. Eight rules for optimal work with ChatGPT Work
These are the difference between "fun toy" and "tool that saves hours". Print and pin them by the team's desk.
One task = one goal
"Prepare the June sales report" not "handle sales, marketing and by the way the website". Small, specific tasks finish faster and burn less quota.
Put context in AGENTS.md once
An AGENTS.md file in the project folder is the standing brief: what the project is, which tools to use, what not to touch. ChatGPT Work reads it on start - you don't repeat it in every prompt.
Plan first, execute second
Add: "show me the plan first and wait for approval". You catch a misunderstanding in 30 seconds instead of 20 minutes of agent work.
New topic = new session
An old chat drags all its context. Starting new work in a fresh session gives faster replies and slower quota burn.
Repeating process = skill
If you're writing the same instruction a third time - turn it into a skill (Lesson 09). Written once, then it runs on a single call.
Point at files, don't "look around"
"Data is in /reports/june.xlsx, columns B and F" beats "find the sales data". Every minute of searching costs quota and adds risk.
Control the result, not each step
Instead of hovering over the agent, set a checkpoint: draft, diff or a summary to approve. You decide on send - ChatGPT Work decides on the path.
Measure what you automate
Log: task, manual time vs. ChatGPT Work time, number of revisions. After a month you know which automations to expand and which to drop.
3. ChatGPT Work Enterprise
The same agent - plus the management layer a larger organization requires.
Team usage rules
Check the limits and available reports for your specific plan with the administrator. A limit shared across products on one account does not automatically mean one pool for the entire team.
Control and audit
The admin decides who accesses ChatGPT Work, which environments and integrations. Audit logs show who ran what - key for GDPR and compliance.
IT-managed environments
Enterprise lets you define which environments the agent runs in, which secrets it sees and which systems it can reach. IT sets it up once - the team uses it safely.
Centrally approved integrations
Instead of 50 people wiring up personal accounts - one approved list of connectors (Slack, GitHub, CRM) with least-privilege access.
What an Enterprise rollout looks like in practice
- 1Pilot (2-4 weeks): one team, 2-3 processes, plain Business plan. You gather evidence that it works.
- 2Usage policy (1 page): what you may automate, what data may reach the agent, who approves sends. A policy template is in the prompt library.
- 3Enterprise conversation with OpenAI: with numbers from the pilot you negotiate terms against real usage - you're not buying blind.
- 4Department-by-department rollout: IT configures environments and integrations, each department gets a short training and a list of approved automations.
More detailChange history and model retirementsDated course information. Open it for an older model or plan change; confirm current terms on your account.
ChatGPT interface guide
Usage: read your account limits
In short ↳The screenshot shows two usage windows and renewal times. The 100% and 82% values describe this account when captured.
Where to find it: Settings → Usage
Select the screenshot to enlarge it.
What you see on screen
- 1
Plan limits
The screenshot describes a limit shared across Codex, Work, agents and Excel, excluding Chat. This does not establish a team-wide pool or the absence of other limits.
- 2
5-hour limit
Read the percentage and renewal time. Five hours names the usage window, not guaranteed continuous working time. Per the pricing page (18 Oct 2026) Pro plans currently have no five-hour limit - you will mostly see this counter on Plus and Business.
- 3
Weekly limit
You cannot derive a task count from 82%; tasks differ in duration, tools and settings.
- 4
Usage resets
No resets are available here. Do not plan work assuming one will become available.
- 5
Credits
The credits and top-up section begins below. Inspect current terms and cost settings before enabling it.
How to use it - in plain words
- Before a large task, inspect both limits and renewal times.
- Split work into stages and inspect usage after the first.
- When usage is low, save progress and inspect available options.
Try it on your account
Find both renewal times. Explain why 82% does not mean two more large tasks.
More detailDevDay 2026 announcementsRecorded product changes. Check current availability and account terms before making a decision.
DevDay - San Francisco, 29 September 2026
OpenAI DevDay 2026 announcement summary
Agents API - public beta
Not chat over an API, but task execution: hosted runtime, memory, tools and multi-agent work in a single task. Plus Computer Use in the API, Tool Search and automatic Context Compaction for long conversations.
Decisions API - a model that decides
Built on GPT-6 Luna. It doesn't generate text, it picks one of the options you define and returns it with a confidence score: classification, routing, the agent's next step. It answers in about 150 ms. Limited preview, pricing has not been published yet - check the current price before you build on it.
Dots - agents that keep working
OpenAI answers Meta's Muse with Dots: personal agents on GPT-6 Astra running 24/7 on their own cloud computer, connected to more than 4,000 apps. They keep context between conversations and work with the laptop closed. Background app access is read-only - changing data or sending anything needs your approval. One primary Dot for now; Pro and Business Premium (Enterprise/Edu: beta, off by default).
Codex - security and many environments
Codex Security Cloud scans your repo for vulnerabilities, investigates the findings itself, removes duplicates and prepares the fixes - and scanning can run continuously. Plus multiple cloud dev environments, Codex Cloud working with the laptop closed, voice control in the CLI, the /agents view and code review in the desktop app.
Ultrafast - fast, at a price
Codex up to 8x faster (up to 300 tok/s), the API up to 6x faster. OpenAI quotes 6x the standard price - for GPT-6 Astra that works out to 60 USD/M input and 300 USD/M output, though some of those line items are calculated rather than published in the DevDay materials. Available in the API and in ChatGPT Work and Codex for Enterprise and the Pro 500 plan (500 USD/mo).
Pro 200 and Pro 500 - recorded changes
The DevDay material describes a Work and Codex limit change from 20x to 10x, GPT-6 Pro messages from 200 to 100 per week, and a Pro 500 plan (500 USD/mo) with Work and @ChatGPT for Slack and Teams. It also describes a transition period and a one-off credit for existing customers. Confirm current terms on your account.
ChatGPT Space and Pages
A shared space where a team and ChatGPT build pages: interactive documents with charts, checklists and images that update themselves from connected sources. Pro, Business and Enterprise, desktop and web (mobile: view only). Collaborative slides with export to PowerPoint and Google Slides are due within weeks. Team Tasks and the Slack/Teams connection are Business and Enterprise only.
Plugin extensions and @ChatGPT in Slack and Teams
Plugins get a home in the ChatGPT sidebar: panels beside the conversation, fullscreen apps and file viewers (web support for Free and Go is still to come). You can mention @ChatGPT in Slack and Teams channels, threads and direct messages; teammates do not need their own ChatGPT licence.
Meetings plugin - notes without a bot
Takes notes on calls and in-person conversations without a bot joining, creates a summary with action items and adds it to a Space. Beta in the Mac desktop app for Pro and Business. Agree recording consent and GDPR rules with participants before you use it.