My cloud agents were set up with environment.json files but as of yesterday/today (March 17th/18th 2026) they no longer have access to use computerUse subagent (via the Task tool), and I’m wondering why this stopped suddenly?
Hi @Konnor_Willison,
This is a known issue with how cloud agent environments configured via environment.json interact with the computer use capability check.
When you set up an environment through the web dashboard, computer use works during that initial setup flow. However, for regular agent runs afterward, if your repo has an environment.json file that uses a base image configuration (rather than a custom Dockerfile or snapshot), the system doesn’t recognize it as a testing-capable environment and silently disables computer use.
Workaround: Delete the environment.json file from your .cursor/ directory in the repo. This allows the environment configuration saved in the dashboard to take effect, which should restore computer use capabilities.
A related thread describes the same pattern and confirms this workaround. Our team is aware of the issue and working on a fix so that environment.json-based setups properly retain computer use access.