Thank you for reaching out!
Could you please share a few more details about your issue? This will help us better understand and analyze the problem so we can provide you with a more accurate and helpful response.
I just started using Antigravity today. I opened a project like using VSCode (agy my-project-folder), and encountered an error while creating the workspace rule. The above is the error message mentioned.
Antigravity Version: 1.13.3
VSCode OSS Version: 1.104.0
Commit: 94f91bc110994badc7c086033db813077a5226af
Date: 2025-12-19T21:03:14.401Z
Electron: 37.3.1
Chromium: 138.0.7204.235
Node.js: 22.18.0
V8: 13.8.258.31-electron.0
OS: Darwin arm64 25.2.0
Language Server CL: 846830895
Hello @hawberr_i, thank you for sharing additional details.
Could you please try the following to help us verify the root cause?
1.Ensure that the configuration file (e.g., .cursorrules, .aichat, or the specific config file your workspace uses) is not read-only and that the Antigravity process has write access to the root directory.
2. Open the Developer Tools (Help > Toggle Developer Tools), go to the Console tab, and attempt to add the rule again. If you see a specific error trace (e.g., EACCES, JSON parse error, or a 403), please share that here.
3. As a workaround, can you manually edit the rule file in the editor to add your instruction? If that works, it confirms the issue is isolated to the UI/Agent interaction layer.
This is the error trace information after opening the developer tools and adding workspace rules:
workbench.desktop.main.js:6905
POST https://127.0.0.1:64457/exa.language_server_pb.LanguageServerService/CreateCustomizationFile 500 (Internal Server Error)
next @ workbench.desktop.main.js:6905
(anonymous) @ workbench.desktop.main.js:6905
(anonymous) @ workbench.desktop.main.js:6905
mcu @ workbench.desktop.main.js:6905
unary @ workbench.desktop.main.js:6905
(anonymous) @ workbench.desktop.main.js:6905
t @ workbench.desktop.main.js:3661
createRule @ workbench.desktop.main.js:3661
await in createRule
createRule @ workbench.desktop.main.js:3661
$createRule @ workbench.desktop.main.js:3661
S @ workbench.desktop.main.js:6892
Q @ workbench.desktop.main.js:6892
M @ workbench.desktop.main.js:6892
L @ workbench.desktop.main.js:6892
(anonymous) @ workbench.desktop.main.js:6892
C @ workbench.desktop.main.js:2791
fire @ workbench.desktop.main.js:2791
fire @ workbench.desktop.main.js:3590
l.onmessage @ workbench.desktop.main.js:6903
workbench.desktop.main.js:6845 Failed to create rule: ConnectError: [unknown] no workspaces found
c @ workbench.desktop.main.js:6845
(anonymous) @ workbench.desktop.main.js:6845
C @ workbench.desktop.main.js:2791
D @ workbench.desktop.main.js:2791
fire @ workbench.desktop.main.js:2791
addNotification @ workbench.desktop.main.js:4339
error @ workbench.desktop.main.js:4339
t @ workbench.desktop.main.js:3661
await in t
createRule @ workbench.desktop.main.js:3661
await in createRule
createRule @ workbench.desktop.main.js:3661
$createRule @ workbench.desktop.main.js:3661
S @ workbench.desktop.main.js:6892
Q @ workbench.desktop.main.js:6892
M @ workbench.desktop.main.js:6892
L @ workbench.desktop.main.js:6892
(anonymous) @ workbench.desktop.main.js:6892
C @ workbench.desktop.main.js:2791
fire @ workbench.desktop.main.js:2791
fire @ workbench.desktop.main.js:3590
l.onmessage @ workbench.desktop.main.js:6903
I manually added files in .agent/rules, but the Agent seems to be unable to read them (@rules: No results).
I had the same issue, finally it seems that the last version of antigravity is not working well with projects in folders starting with . (i.e. .gemini or .lumina in my case). I’m on linux by the way.
In addition, the agent manager is not able to run shell commands using my workspaces because it has issue reading the path. The workaround was to open the folders directly (and not the workspaces), then bash execution works perfectly well.
Error Message returned by Gemini: path is not in a workspace which you have access to: either proceed without accessing that path, or ask the user if they are willing to turn off workspace validation
I also work on Linux and my workspace paths all are defined by default using:
"folders": [
{
"path": "."
}
],
Perms:
-rw-rw-r-- 1 myuser myuser 993 Mar 10 12:14 my-project.code-workspace
I can’t tell when was the last version it used to work, but it used to work.
Same here. On v1.20.5, my old rules are missing from the list. The files are still there and the chat says they’re active, but they don’t seem to be applied in reality.