✅ Proactively detected & fixed: agent could lose its project workspace on some cloud sessions

[edgar-durand]

Status: ✅ Resolved — detected proactively, fixed and deployed.

What happened: on certain cloud sessions, an internal auto-recovery could restart the session's relay outside the project folder. The repo cloned fine, but the agent ended up working from the wrong directory — looking "detached" from your repo (e.g. exploring the home folder instead of your code).

Fix: a 3-layer guard now prevents the recovery path from ever displacing a running session, locked in with real regression tests. Deployed to production; the affected sessions were healed live.

If you saw it: an agent that "couldn't see your repo" on a cloud session was this. New prompts now always run in your project — if an old conversation shows the agent exploring the wrong folder, that's just history; everything new runs in the repo. 💜