An agent that can never resume now fails fast instead of retrying forever in the background.
What's wrong with this entry?
A new error class marks a resume that will never succeed, so the retry machinery gives up instead of looping.
- AgentResumePermanentlyRefusedError sits alongside AgentResumeTransientError.
- The observer restarts fresh on it and logs the error name.
- The wake router drops queued events for the affected agent.
- The resume subscriber no longer swallows the error silently.
AgentResumePermanentlyRefusedError
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.235
Question options with identical text are no longer confused with each other
Both mention agent
-
v2.1.236
Teammate messages whose summary swallowed the body are split back apart
Both mention agent
-
v2.1.238
Claude is told to stay in a worktree even when it did not create one
Both mention agent