🐛 Known issue (fix in progress): dormant Codespaces failing to wake (name mismatch)

[edgar-durand]

Status: ✅ Resolved — fixed and deployed.

What happens: a Codespace that has gone to sleep (idle timeout) can fail to wake / resume when you reconnect to it.

Cause: a name mismatch in the wake path prevents the resume from resolving the correct Codespace.

Impact: limited to waking already-slept Codespaces — creating/deploying a new session works.

Fix: ✅ deployed. No action needed — dormant Codespaces now wake reliably. If a resume failed before, it works now.

Workaround: if a resume fails, deploying/starting a fresh session usually works in the meantime.

We'll update this thread when it's fully deployed. Thanks for your patience! 💜

[edgar-durand]

✅ Update: fixed and deployed.

The name mismatch in the wake path is resolved — reconnecting to a slept Codespace now finds the right box and resumes it (without disturbing the running agent). No action needed; if a resume failed before, it works now. Thanks for the patience! 💜