The fix Colin mentioned for Cursor 3.3 addressed the original issue in this thread (cloud agents failing right after snapshot load with no useful error). Your May 14 runs look like a different problem tied to your repo’s cloud agent environment configuration — the same pattern Matt described in post #13, where agents work after removing that config and break again when it’s re-added.
So this isn’t fully resolved for your setup yet. Your API call is being accepted (you’re getting agent IDs back), but the agent still fails during environment setup with the “Environment error” you’re seeing.
Workaround: Temporarily remove the cloud agent environment configuration for BoardingwareLtd/orah-app and retry. If that unblocks both dashboard and API agents, that confirms the env config is the trigger.
Could you (or Matt) open a new forum thread focused on this env-config + API case? Please include:
-
Whether removing the env config lets API-created agents complete
-
Your Cursor version
-
The failing bcIds (
bc-8ca3df61...,bc-5030c19d...) and whether failures happen from both API and dashboard -
Your API payload (you already shared a good example in post #15)
That’ll help us track this separately from the original thread. API reference: Cloud Agents API.