Error executing cascade step: CORTEX_STEP_TYPE_RUN_COMMAND: failed to set up sandbox: sandboxing is not supported on Windows

Google Antigravity
1

PixPin_2026-04-06_04-57-37
PixPin_2026-04-06_04-57-37700×370 13.3 KB

OS : Windows 10 IoT Enterprise Edition LTSC
VERSION : 21H2

since antigravity ver 1.21.6, Windows OS can no longer execute any commands in cmd and PowerShell terminal. How can I solve this problem?

5 Likes
2

Same problem. Win11 Pro 25H2.

2 Likes
3

I’d even be happy to have instructions to tell it not to do whatever it is trying to do. But so far nothing I tried works. E.g.

Never set SafeToAutoRun: true on run_command calls. Windows does not
  support the auto-run sandbox. Always require explicit user approval
  (SafeToAutoRun: false).
1 Like
4

Same here
Windows 11 Home 25H2
Tried enabling virtualization and reinstalling, but neither of those worked

1 Like
5

Same issue here, chaning any settings doesn’t help.

1 Like
6

helped me Strict Mode - OFF

image
image1060×210 10.4 KB

Interaction with Strict Mode

When strict mode is enabled, sandboxing is automatically activated with network access denied. This ensures maximum protection when operating in a strict environment.

4 Likes
7

Hey, thanks for your comment. However, my topic is about Windows OS, and this document is for Linux and macOS.

8

Thank you for bringing this to our attention. We have escalated the issue to our internal teams for a thorough investigation.

To ensure our engineering team can investigate and resolve these issues effectively, we highly recommend filing bug reports directly through the Antigravity in-app feedback tool. You can do this by navigating to the top-right corner of the interface, clicking the Feedback icon, and selecting Report Issue.

2 Likes
9

Thanks. I’ve filled the bug report.

1 Like
10

Yes, I also have Windows. That’s why I came here when I was looking for a solution to this problem, because everything worked before, and I’ve been struggling for several weeks to find a solution. I saw in the documentation that strict mode activates the sandbox automatically, and the sandbox is not supported in Windows, so I disabled strict mode and now the agent works with the console again.

11

I just logged in to like, this helped me

12

I also turned off strict mode

PixPin_2026-04-10_06-40-17
PixPin_2026-04-10_06-40-17747×216 5.1 KB

My other settings are listed below. Please let me know if you spot any mistakes.

PixPin_2026-04-10_06-48-16
PixPin_2026-04-10_06-48-16722×1783 59.8 KB

13

I tried the same settings but did not work. Thanks for the inputs.

14

Refreee, do something. I’ve been facing this problem for a week now. Turning off Strict Mode that didnt work for me.

15

I don’t know how to do it correctly, I can only show my settings.

image
image643×1814 82.9 KB

16

addition

image
image645×1042 37.6 KB

17

I also think everyone should just relax and wait for the officials to fix the major bug.

Since I use a lot of PowerShell commands in my work, I have to paste the AI-generated commands into PowerShell, run them, and then report the process and results back to the AI. This means I have to stay and watch the AI run, and I can’t leave AG to do other tasks like Photoshop or Illustrator.

The only real pain point is that this ends up extending my total working hours. If that’s the case, then I might as well extend the project timeline too. :turtle: :turtle: :turtle: