Commit 85f0c79
fix: use node-scoped callback token when waking restored container
wakeFromSnapshot launched the restored container with a workspace-scoped
callback token (signCallbackToken) passed as the container CALLBACK_TOKEN,
but the vm-agent uses it for node callbacks (error/activity/message
reporting) which reject workspace-scoped tokens with 403 "Insufficient
token scope". Restored sessions therefore accepted a prompt (200) but
silently failed to report the agent's reply, so no answer appeared after
wake. Sign a node-scoped token (signNodeCallbackToken) to match the initial
launch in launchInstantSession.
Diagnosed from staging Worker logs (node_auth.rejected_workspace_scoped_token).
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>1 parent ac6a9e8 commit 85f0c79
1 file changed
Lines changed: 8 additions & 2 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
5 | 5 | | |
6 | 6 | | |
7 | 7 | | |
8 | | - | |
| 8 | + | |
9 | 9 | | |
10 | 10 | | |
11 | 11 | | |
| |||
345 | 345 | | |
346 | 346 | | |
347 | 347 | | |
348 | | - | |
| 348 | + | |
| 349 | + | |
| 350 | + | |
| 351 | + | |
| 352 | + | |
| 353 | + | |
| 354 | + | |
349 | 355 | | |
350 | 356 | | |
351 | 357 | | |
| |||
0 commit comments