Antigravity IDE: Slash Commands (workflows) Disappear Entirely (no results) Due to 4 Fatal Parser Exceptions

Google Antigravity
1

:hammer_and_wrench: FIXED: How to restore vanished Slash-Commands (0 Results) in Antigravity

If your Antigravity slash-command UI parser has suddenly died and is returning a blank “0 matching results” screen with no error logs, you have likely hit one of these 4 silent unhandled exceptions natively triggering a crash. Here is how we debugged and solved each one:

1. Multiline YAML Exception

  • The Crash: The parser completely fails if any markdown workflow file contains a folded block scalar in the YAML frontmatter (e.g., description: >).
  • The Fix: We built a script to aggressively truncate all workflow descriptions across our backups into single-line, unquoted strings. Do not use multiline YAML.

2. Greedy Recursive Bleed

  • The Crash: The Antigravity parser aggressively searches recursively through its entire installation directory. If you store unrelated markdown documentation (e.g. customized skill cards) in the global root folders, it evaluates those unknown structural fields as a malformed workflow and silently crashes globally.
  • The Fix: We physically isolated all markdown files that aren’t strictly workflows into a completely separate directory outside the parser’s reach natively, so it only scans valid slash commands.

3. Silent MCP Connection Crash

  • The Crash: If the MCP configuration JSON file contains outdated or non-existent hardware binaries from an old machine setup, opening a related project script causes the generative context to violently error out, taking down the entire Antigravity slash-command UI silently entirely unprompted.
  • The Fix: We manually scrubbed the configuration file of all static hardware directory paths and replaced them purely with system-agnostic executable aliases, safely restoring the IDE context loader.

4. Symlink Duplicate-Key Namespace Collision

  • The Crash: If using nested project workspaces, and the parser traverses upstream mapping two identically named shortcut folders to the exact same physical workflow file, the engine dies silently on an internal Dictionary “Duplicate Definition” KeyError.
  • The Fix: We deleted all redundant overlapping local symlinks across the nested sub-directories and consolidated our targets to point exclusively to one unique native root folder.
2

Hello @Artifexon, welcome to AI Forum!

Thank you for this insightful feedback on the Slash command issues and related fixes. We appreciate you being part of the community.
Happy coding!

1 Like