Hey @Thorsten_Ruppenstein, thanks for the report and for tracking down the cause.
You’re right: the persistent session state directory is currently created under a fixed /tmp path rather than respecting $TMPDIR, and resume checks that directory even when you’ve never started a persistent session. I’ve passed this along to the team.
In the meantime, if someone with admin rights on the machine can pre-create the directory for you, resume should work again:
- Find your user id with
id -u - Create
/tmp/cursor-agent-persist-<your uid>owned by your user - Set its permissions to 700 (
chmod 700 /tmp/cursor-agent-persist-<your uid>)
Starting a new chat (without resume) should not be affected. Could you also share which OS this is on and how /tmp is restricted (read-only mount, sandbox, container)? That helps us make sure the fix covers your setup.