"Use Configured Environment" for Automations not working 100%

[evsasse (Evandro Sasse)]

Where does the bug appear (feature/product)?

Background Agent (GitHub, Slack, Web, Linear)

Describe the Bug

Even though I have the “Use Configured Environment” option toggled ON for my Automation, and that environment works super well for agents that I kick-off manually. When the Automation runs it says that certain things are not installed??

Steps to Reproduce

• Configure the environment for a certain repo, with some tools it may require.
• Configure an Automation for that repo, that would use those tools.
• Make sure the “Use Configured Environment” option is toggled on.
• Then check on the Automation run, if it was able to use the pre-installed tool.

Expected Behavior

It should be able to “Use Configured Environment”…

Screenshots / Screen Recordings

Version Information

Cursor Web.

For AI issues: which model did you use?

GPT 5.4

Does this stop you from using Cursor

Sometimes - I can sometimes use Cursor

[deanrie]

Hey, thanks for the report. I see the screenshots. The agent says Ruby and bundle aren’t available in the VM.

A few questions:

1. How is the environment set up, via agent-driven setup (snapshot on cursor.com/onboard) or via a Dockerfile in .cursor/environment.json?
2. Is the Automation set up as Private or Team Owned?
3. Can you share the URL for the specific automation run?

I passed this to the team. It looks like a bug where Automations don’t pick up the environment correctly. No ETA yet, but your report helps us prioritize it.

[evsasse (Evandro Sasse)]

1. via agent-driven setup (snapshot on cursor.com/onboard)
2. Team Owned
3. https://cursor.com/agents/bc-8ff48eca-2952-4d5e-9fd0-2e7eb4d20693

[evsasse (Evandro Sasse)]

Also, I see that it didn’t sign the commits it did.

And on that environment “Update Script" I have some tweaks to make it sign the commits.

So it indicates to me that the “Update Script" for that environment has also not run.

[evsasse (Evandro Sasse)]

• https://cursor.com/agents/bc-efa52df4-578a-4f0a-9704-d9f6a4612f64

Previously it was not able to run Ruby, but was able to create PRs… Now it is also not able to create PRs too .

[pierric (Pierric Cistac)]

Same here, the toggle is “on” for “Use Configured Environment”, but clearly it’s not using it (in the agent startup steps, I can see it’s clearly loading the wrong snapshot)

The env is also configured through agent-driven setup, and team-owned (https://cursor.com/agents/bc-e9d60ff3-cc6f-4c6f-a38a-8f1fefdd0139)