[danielehrhardt]

I've changed when Godmode tries a turn again after Claude's API refuses it with a 403. The 403 itself isn't caused by Godmode's code: it was a short refusal from Claude's API during a network drop.

What happened (2026-10-18, 14:34–14:38Z)

• A chat's first request got three connection errors and then 403 Request not allowed. The link to the runner stopped answering at the same moment, so the network dropped briefly. The Mac didn't sleep, and the runner doesn't share this computer's Claude login.
• Godmode's automatic retry from Pause an agent or a chat and continue where it stopped; wait out Claude's usage limit (GODM-45) #51 started 14 s later and got the same 403. The human then clicked Retry twice: the first failed, the second worked 9 s later with the same session, settings and Claude Code version. The refusal lasted about 2 minutes and then cleared by itself.
• What was wrong on Godmode's side: Claude Code doesn't retry a 403 itself, and Godmode's first retry for errors comes right away. So that first try ran into the same refusal and used up one of only three tries.

Change

• packages/core/src/services/resume.ts: a 403 sign-in refusal now has its own retry schedule of 2, 5 and 15 minutes instead of right away, 2 and 5 minutes. With this schedule, the first automatic retry in this case would have come after the refusal had cleared. The other errors and connection failures keep their current schedules. I also fixed the code comment, which said a 403 only comes right after waking.
• packages/core/test/resume.test.ts: the 403 test now checks that nothing is retried before each wait is over, that each retry is marked as automatic, and that it stops after three tries.

Checks

• bun test test/resume.test.ts: 22 passed, 0 failed. The new test fails against the old code.
• pnpm -r typecheck: no errors.
• origin/main had no new commits, so there was nothing to merge.

---

Task #56 · done by Self-Healer with Godmode Bot