Included agentic usage increases across paid plans
OpenAI has increased the ChatGPT Work and Codex usage included with several paid plans. The company says Pro 100 and Pro 500 now include twice their previous allowance, with Business Premium also covered by the increase. The change expands how much long-running research, coding and deliverable work subscribers can perform before purchasing additional credits.
OpenAI also cancelled a reduction previously announced for Pro 200. Customers who already had the higher Work and Codex allowance keep it, while subscribers on the lower allowance receive twice that amount, bringing them to the stated common level. Reversing a planned reduction should reduce near-term uncertainty for users who selected a plan around expected capacity.
A cancelled reduction reduces customer uncertainty
Agentic usage is harder to compare than a simple message limit. A coding task may inspect a repository, run tests and iterate for an extended period, while another request may finish quickly. Subscribers need dashboards that show what consumed allowance, how model choice affects use and when additional credits begin to apply.
More included capacity can improve experimentation, but it can also hide inefficient workflows. Repeated retries, oversized context and unnecessary tool calls may consume time and compute without improving a result. Teams should track completed tasks, review effort and defects rather than treating allowance consumption as evidence of productivity.
Teams should measure outcomes rather than consume allowances
Business workspaces need internal controls even when the commercial plan permits more activity. Repository access, connected applications and tool permissions should reflect job roles, and long-running tasks need clear approval for consequential writes. Higher usage does not change the organisation’s responsibility for data handling or human review.
The practical value will depend on stable disclosure of allowances and predictable metering. Users should record before-and-after task volumes and costs over a representative month. If the increase enables more valuable work without proportionally increasing oversight burden, it can change the economics of using Work and Codex as routine production tools.
What teams should validate before production
For implementation, teams should record the exact model, software, dataset, connector and policy versions behind every result. Representative evaluation must include normal work, boundary cases, deliberate misuse and component failure, with outcomes separated by user role, data sensitivity and consequence. A strong average should never hide a serious failure in a critical path. Changes should pass the same regression set before promotion, and operators need a documented fallback that preserves evidence rather than silently broadening access or lowering quality.
Procurement and planning should account for the human work required to review exceptions, maintain controls and investigate incidents. Published performance or efficiency claims are useful starting points, but production confidence comes from evidence collected in the organisation’s own environment. A named owner, measurable acceptance threshold, cost model and tested shutdown path turn a promising release into a service that can be governed over time. Where decisions affect safety, rights, money or regulated records, accountable professional review remains essential.
Security and operational evidence
Security review should map every identity, credential, network destination, stored artefact and administrative access path involved in the workflow. Logs need enough context to reconstruct who initiated an action, which evidence was consulted, what the system proposed and what ultimately executed. Sensitive prompts and traces should not be retained merely because they are useful for debugging. Retention, redaction and access must follow the underlying data classification, with a practical process for correcting or removing material when policy or law requires it.
Operational monitoring should measure quality and service behaviour together. Latency, throughput and availability matter, but so do unsupported claims, missed constraints, unsafe tool calls and the rate at which people overturn recommendations. Teams should rehearse dependency outages and partial failures before unattended operation. If a model, connector or external service becomes unavailable, the workflow should fail predictably, preserve its state and tell the user what remains unfinished. Clear degradation is safer than an agent improvising around a missing control.
Transparency should scale with adoption
Organisations should explain the scope and limitations of the deployed capability to the people affected by it. Users need to know when automation is involved, how to challenge an outcome and where a human can intervene. That transparency improves feedback and prevents a pilot result from being interpreted as blanket approval for broader autonomy. Expansion should follow demonstrated evidence, not novelty or pressure to match a competitor announcement. The durable advantage comes from dependable integration, careful measurement and learning that survives the next model or product update.
Finally, teams should schedule a review after real usage rather than treating launch as the end of governance. The review should compare expected benefits with observed quality, cost, incidents and user behaviour, then retire workflows that do not justify their complexity. A service that works well can expand through the same evidence-based process. A service that fails should be narrowed or stopped without losing the records needed to understand why. This feedback loop is what turns experimentation into accountable operational capability.