Cannot Use Agent Demos with Prior Environments

Support Help
,
1

Not sure if it’s a bug but I only see the option to enable agent demos when I connect new repos or setup new environemnts. Existing ones don’t show me the option for some reason.

6

This is actually expected behavior. The “Enable agent demos” option is an onboarding prompt that only appears for repos that don’t yet have a cloud environment configured. Once you’ve set up an environment on a repo (which is the case for your existing ones), demos are already enabled automatically - there’s no separate toggle needed.

So if your existing environments have a snapshot or Dockerfile configured, agent demos should already work on those repos without needing to do anything extra.

If demos genuinely aren’t working on a repo that has an environment set up, the most likely cause would be either:

  • The environment was created as a basic git-repo type (without a snapshot/Dockerfile)

  • Or enable_testing was explicitly set to false in your .cursor/environment.json

Let me know if you’re running into an issue where demos aren’t actually producing results on your existing environments - that would be a different problem worth investigating.

7

Ah, I see. But the agent seems less inclined to create demos unless it is on a new cloud environment…
If I ask specifcally it seems to kind of do it but not the way it used to on the first time.

8

That difference is expected. The polished demo you got the first time comes from the environment setup run specifically - that run is tasked with bringing the environment up and showing it works, so it reliably records a demo. Regular agent runs afterward are focused on the code change you asked for, so they won’t put together a full environment demo on their own unless you ask.

A couple of things that affect whether a regular run can make demos at all:

  • Model: demo/computer-use recording only runs on recent Claude models (Sonnet or Opus). If the agent is on a different model, it can’t record one.

  • Testing not disabled: make sure enable_testing isn’t set to false in your repo’s .cursor/environment.json.

Even with both in place, a regular run frames the demo around verifying the specific change it made rather than walking through the whole environment, so it’ll look a bit different from that first setup demo. If there’s a particular run where you expected a demo and didn’t get one, drop the agent link here and I’ll take a look.

9

I always use Cursor 2.5 now… can I request you enable it for that?
I mean when I explicitly tell it to record a video it does… it just installs its own MP4 recorder tool :laughing: