Release messages after Codex recovery
This commit is contained in:
1 parent
46831520e3
commit
b9b777acaf
2 files changed
+118
-1
No files matched your search
@@ -245,6 +245,10 @@ Other resume failures remain errors rather than silently discarding context.
|
||||
The replacement's `thread/started` notification is a new root despite not
|
||||
matching the translator's old root id; its null `parentThreadId` distinguishes
|
||||
it from a subagent and moves the translator to the replacement conversation.
|
||||
That notification retries the waiting queue, so delivery does not depend on a
|
||||
later message happening to retry it. A message accepted while initialization or
|
||||
recovery is still finding a thread is recorded as queued; the phone can therefore
|
||||
reopen without losing the only visible copy before Codex acknowledges it.
|
||||
|
||||
Codex subscription limits come from the CLI's `account/rateLimits/read`
|
||||
app-server request on the machine that runs Codex. This keeps login and
|
||||
|
||||
Reference in new issue
Block a user