Service eligibility and regional restrictions
PuppyIP serves only compliant overseas businesses and their authorized personnel. Proxy services are not available in mainland China. The service may only be used for lawful business activities outside mainland China. Use of this service within mainland China is prohibited.
Hosting a proxy IP or server overseas does not change these restrictions. The service must not be provided to end users in mainland China through relaying, forwarding, sharing or resale. Before use, read the Terms of Service.
Key Takeaways
- Tibo confirms the integration is being developed and is not rolling out yet.
- Sometime this year describes a plan; exact dates, plans and regions remain unspecified.
- The post announces no new Chat/Work usage limits, prices or conversation-migration rules.
What Tibo actually confirmed
At 23:35 UTC on October 28, 2026 (07:35 UTC+8 on October 29), Tibo quoted a user discussing Chat/Work unification and usage limits. He clarified that the team is working on it but rollout has not started. The quoted user’s claim is context, not launch evidence.
He described bringing the strongest capabilities of both together sometime in 2026, while proceeding carefully and taking time. That is a development direction and intended timeframe; a specific release date remains unknown.
Shared Recents already exists: what is different?
Current OpenAI help describes Chat as quick conversational assistance and Work as longer, multi-step work, subject to plan and workspace access. Their conversations can already share desktop Recents. Codex retains a separate view and history.
The July 16 release notes already described these desktop navigation changes. Seeing conversations together therefore does not establish that the proposed capability integration has shipped.
For example, suppose an ordinary conversation and a multi-step task appear in the same Recents list. That shows a shared place to find them. Confirming new shared capabilities still requires explicit details about supported tasks, clients, and any account or workspace restrictions.
Have usage limits, prices or migration rules been announced?
This clarification gives no combined allowance, price, plan list or regional rollout. Current help says Work follows the Codex usage structure. That existing rule does not establish that regular Chat usage has joined that pool.
The post also leaves conversation and Project migration, and any plugin-permission changes, unspecified. Keep existing terms as the basis for subscription or team decisions until explicit new terms are published.
Check two separate usage questions: how a Work task is metered today, and whether a future Chat/Work integration would change that calculation. Existing help explains the first; this clarification does not answer the second. It provides no basis for estimating additional usage or changing a team budget.
What to check now
Identify whether you are using Chat, Work or Codex, then inspect the features, model choices and usage information available there. For team accounts, also check workspace access. This article has not inspected readers’ accounts or verified individual availability.
When a formal release arrives, check its date, eligible plans and regions, clients, usage rules and migration terms. This page will follow substantive changes using the same original-author and official-documentation approach.
Sources
Frequently Asked Questions
Is this another Codex usage-reset announcement?
The post concerns Chat/Work integration. It announces no new reset and supplies no new Day number; it is not evidence that additional usage has reached accounts.
Should I migrate conversations or reconnect plugins now?
The post provides no migration or reauthorization procedure. Continue in your current experience, and check the applicable scope and steps if formal migration instructions later require action.
Does this confirm that my account has a unified experience?
No. Tibo says rollout of this integration has not started, and this article has not tested individual accounts. An existing layout or shared Recents alone does not establish access to the proposed integration.