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 labeled the October 19 change Day 14: earlier messages in a desktop-app thread can be edited.
- The post gives no operating-system, client-version, account-eligibility, rollout, or control-location details.
- In a reply, Tibo called it 'Registers as time travel,' but did not explain reply regeneration or changes to actions already underway.
- This is a usability update; the post does not announce a quota reset or usage change.
What did Day 14 actually confirm?
On October 19, Tibo labeled the change Day 14 and said earlier messages within a thread can now be edited in the desktop app. He called it a small quality-of-life improvement that users had requested for a long time. That describes the feature he announced; it does not establish that every user already has the control.
The post does not name a specific operating system, desktop client or version, account plan, or rollout schedule. It also gives no button label. It confirms editing earlier messages in a desktop-app thread, not support in the web app or command-line client.
When is editing an earlier message useful?
An earlier request may be missing a constraint. For example, you might first ask for a log summary, then realize you need IP addresses masked before the summary is made. Editing the earlier message can put that correction at the earlier point in the thread. This is a hypothetical example, not a tested workflow.
In reply to a question about changing an earlier prompt, Tibo said, 'Registers as time travel.' That suggests the edit is understood in the thread's earlier context, but it is not a full behavior specification: he did not say whether old replies remain, later messages are regenerated, or an already-started tool or external action changes. Recheck later replies and action state before relying on the thread; changing text is not the same as undoing a completed action.
How can you check whether it is available?
Open the relevant thread in the desktop app and look for an edit action near an earlier message. Tibo did not publish a menu path or the exact name of the control, so there is no confirmed click-by-click sequence to follow.
If the control appears, review the edited text and the thread that follows before continuing a task. If it does not appear, the public post gives no minimum version, rollout date, or alternative-client plan. Use the interface you actually see rather than assuming the same feature exists on the web or in CLI.
What should you do with later results?
Editing changes the message text, but the announcement does not explain what happens to replies already in the thread. If the assistant has already produced a command or file, inspect the current result and state clearly which parts need to be redone under the corrected request.
For tasks that call tools or change external state, do not treat edited text as an undo button. Continue only after the later replies and the actual action state match the corrected request.
Is this a quota reset?
Tibo made the original 28-day commitment on October 4 UTC (October 5 in China Standard Time): each day would bring either one meaningful improvement for most Codex or Work users or a full reset. Day 14 describes the message-editing feature; it does not confirm that a reset also happened that day.
The Day 14 post says nothing about plans, personal usage, or quota changes. To check your actual available usage, rely on the information shown for your account. Being able to revise a message is not evidence that usage was restored or that a new reset entitlement was added.
Sources
Frequently Asked Questions
Can I edit earlier thread messages on the web or in Codex CLI?
Tibo’s Day 14 post mentions only the desktop app. It does not confirm web or CLI support, or give a schedule for other clients.
Will editing an earlier message automatically redo later replies?
Tibo replied, 'Registers as time travel,' but did not say whether old replies remain or later content is regenerated. Check the actual thread after editing; do not treat the feature as undoing tool actions or external changes.
Does this update reset Codex usage?
No reset was announced in the Day 14 post. It describes editing an earlier message in a desktop-app thread and reports no usage change.