Hi, thank you for the detailed reply.
I was not aware there is any environment configuration which we can do. I checked and I do not have any .cursor/environment.json file. I have only one rule, which says to always read the AGENTS.MD file.
I was reading this, Setup | Cursor Docs
So, does this mean that this is order the cloud agent will follow,
Since, no environment file exists, so the next thing it has to use is the “Personal environment configuration” which does exist, as I created the environment before and it was successful. I see the snapshot for it,
snapshot-20260318-cf3cf67e-8e0c-4745-bd34-7f4026a08ec6
Update Script
sudo mkdir -p /run/mysqld && sudo chown mysql:mysql /run/mysqld && sudo mysqld_safe &
sleep 5
eval “$(sudo cat /proc/1/environ 2>/dev/null | tr ‘\0’ ‘\n’ | grep -E ‘^(VARIOUS_SECRETS)=’ | sed ‘s/^/export /’)”
DB_PASS=$(echo $DATABASE_URL | sed -n ‘s|mysql://root:\([^@]*\)@.*|\1|p’) && sudo mariadb -e “ALTER USER ‘root’@‘localhost’ IDENTIFIED BY ‘$DB_PASS’; FLUSH PRIVILEGES;” 2>/dev/null
pnpm install --dir /workspace
pnpm install --dir /workspace/web/frontend
pnpm install --dir /workspace/web/backend
cd /workspace/web/backend && npx prisma migrate deploy
Settings
Enable testing
So, I am guessing this is the “update” script which the cloud agent runs. From what the cloud agent prints during execution, I think all of these steps work fine, so I am unsure why it gets stuck after that.
This is the final output I see in the cloud agent before it becomes unresponsive.
260320 21:04:12 mysqld_safe Logging to syslog.
260320 21:04:12 mysqld_safe Starting mariadbd daemon with databases from /var/lib/mysql
Lockfile is up to date, resolution step is skipped
Already up to date
╭──────────────────────────────────────────╮
│ │
│ Update available! 10.32.0 → 10.32.1. │
│ Changelog: Release pnpm 10.32.1 · pnpm/pnpm · GitHub │
│ To update, run: pnpm add -g pnpm │
│ │
╰──────────────────────────────────────────╯
Done in 896ms using pnpm v10.32.0
Lockfile is up to date, resolution step is skipped
Already up to date
Done in 1s using pnpm v10.32.0
Lockfile is up to date, resolution step is skipped
Already up to date
Done in 1.1s using pnpm v10.32.0
Loaded Prisma config from prisma.config.ts.
Prisma schema loaded from prisma/schema.prisma
Datasource “db”: MySQL database “checkoutrules” at “localhost:3306”
27 migrations found in prisma/migrations
Applying migration `20260318123000_add_news_indicator_settings`
The following migration(s) have been applied:
migrations/
└─ 20260318123000_add_news_indicator_settings/
└─ migration.sql
All migrations have been successfully applied.
It reports all good a far as I can see, so no need idea why it got stuck.
I appreciate the help, thank you.
