Frontmatter
| id | 9664 |
| title | Fix MCP server CWD resolution in Antigravity Sandbox |
| state | Closed |
| labels | bugai |
| assignees | tobiu |
| createdAt | Apr 3, 2026, 5:26 PM |
| updatedAt | Apr 3, 2026, 5:28 PM |
| githubUrl | https://github.com/neomjs/neo/issues/9664 |
| author | tobiu |
| commentsCount | 1 |
| parentIssue | null |
| subIssues | [] |
| subIssuesCompleted | 0 |
| subIssuesTotal | 0 |
| blockedBy | [] |
| blocking | [] |
| closedAt | Apr 3, 2026, 5:28 PM |
Fix MCP server CWD resolution in Antigravity Sandbox
Closedbugai
tobiu assigned to @tobiu on Apr 3, 2026, 5:28 PM

tobiu
Apr 3, 2026, 5:28 PM
Applied protective fallback from github-workflow into knowledge-base and memory-core configs to correctly handle proxy path modifications injected by Antigravity sandbox environment.
tobiu closed this issue on Apr 3, 2026, 5:28 PM
tobiu cross-referenced by #9663 on Apr 3, 2026, 5:29 PM
The
knowledge-baseandmemory-coreMCP servers fail withENOENTduringfs.ensureDirwhen launched by the Antigravity sandbox. This occurs becauseprocess.cwd()evaluates to/inside the sandbox environment, where the file system is read-only.This ticket implements a protective fallback identical to the one used in
github-workflow, resolving thecwdto the project root when it detects/.