Hi @joeo and @romil8jain , any chance you have a custom environment.json and/or Dockerfile set up? (@romil8jain do you mind sending over some bcIds as well for us to try to diagnose the issue?)
We’re seeing that the VMs in the linked bcIds aren’t launching successfully, but it doesn’t seem to be a widespread issue across users/teams.
Hi @joshma, we have a custom environment.json but not a custom Docker image. Here it is:
{
"user": "ubuntu",
"install": "./.cursor/install.sh",
"start": "./.cursor/start.sh",
"terminals": \[
{
"name": "dev-server",
"command": "npm run dev:emulators",
"description": "Runs the Next.js development server with hot reloading and connected to the Firebase emulators"
},
{
"name": "functions-emulators",
"command": "npm run functions:serve",
"description": "Starts Firebase emulators with functions watching"
},
{
"name": "watch-callables",
"command": "npm run watch-callables",
"description": "Watches Firebase callable functions and regenerates boilerplate"
},
{
"name": "anvil-blockchain",
"command": "npm run anvil:serve",
"description": "Runs local Anvil blockchain for Web3 development"
}
\]
}
I do want to reiterate that Background Agents were working correctly before, and we did not make any changes to environment.json between the time the agents were running successfully and when they started failing.
Hi folks, we identified and fixed a race condition in our how we were provisioning the agent VMs. Apologies for the issue and thanks again for reporting it in!
