Agents not reading workflow when directed with slash commands

Google Antigravity
,
1

With the 1.14.2 update my agents often skip reading the workflow. This is specifically in regards to workflows in the current workspace and untested otherwise.

Multiple agents self-diagnosed the same root cause:

The System-Level Cause

The system prompt contains this instruction (L16):

“If a workflow looks relevant, or the user explicitly uses a slash command… I should use view_file to read [the file].”

The looks relevant clause introduces discretion. When I saw /research debug screen UI, I:

  1. Correctly detected the slash command
  2. But decided the project-context workflow was “more relevant” to check first
  3. Then proceeded with what I thought was “helpful” (diving into the code)
  4. Never read research.md

For reference my prompts always start with the slash command followed by additional context. The most recent was:

/research debug screen UI

research item 1
research item 2
…
research item 15

2 Likes