What's the Subagent format for antigravity-cli?

[mystilleef]

Looks like gemini-cli subagents are not compatible with antigravity-cli.

How do you migrate gemini-cli subagents, the ones found in ~/.gemini/agents, to antigravity-cli?

[FelixIsaac]

From https://antigravity.google/docs/gcli-migration:

Gemini CLI Extensions → Antigravity Plugins
Since Gemini CLI launched extensions (a way to extend the CLI by bundling and sharing capabilities), the industry has standardized on the term plugins. Antigravity plugins are supported in Antigravity CLI.

Users should be prompted on the first launch of Antigravity CLI to have their extensions automatically migrated to plugins. You can also run an explicit command from your terminal to migrate them:

$ agy plugin import gemini

[mystilleef]

That doesn't migrate subagents.

[FelixIsaac]

Oh right. I misread your question. I don't think they support it. Maybe you could ask the AGY CLI agent to make a subagent. Then find the file for the format of the subagent. Once you have that ask AGY to migrate your Gemini files to the AGY format.

https://antigravity.google/docs/subagents

[mystilleef]

Yeah, I tried that but the agent refuses to load the agent.json file in the agents folder. So I suspect the agent format might be slightly different.

~/.gemini/antigravity-cli/agents/love_poet/agent.json

{
  "name": "love_poet",
  "description": "A subagent specialized in writing poems about love.",
  "hidden": false,
  "config": {
    "customAgent": {
      "systemPromptSections": [
        {
          "title": "Agent System Instructions",
          "content": "You write beautiful, moving poems about love. Maintain an expressive and emotional tone. Keep poems concise but impactful."
        }
      ],
      "toolNames": [
        "send_message",
        "find_by_name",
        "grep_search",
        "view_file",
        "list_dir",
        "read_url_content",
        "search_web",
        "schedule"
      ],
      "systemPromptConfig": {
        "includeSections": [
          "user_information",
          "mcp_servers",
          "skills",
          "subagent_reminder",
          "messaging",
          "artifacts",
          "user_rules"
        ]
      }
    }
  }
}

[kharajch]

Global Agents Relocation

While gemini-cli looked specifically at ~/.gemini/agents, antigravity-cli moves its global agent configs underneath a specialized directory path structure, aligning with its new visual setting parameters.

Move your .md files containing your subagent definitions from your legacy folder to the new global skills path:

Create the target directory if it doesn't exist

mkdir -p ~/.gemini/antigravity-cli/skills/

Copy your custom markdown subagents over to the new global skills location

cp ~/.gemini/agents/*.md ~/.gemini/antigravity-cli/skills/

[aniruddhaadak80]

Great question. Subagents in the CLI are typically defined in markdown files with YAML frontmatter.

You can find full examples and documentation on how this works in our subagents guide and remote agents guide.

You can define them locally or connect to remote ones using the Agent to Agent protocol. Let us know if you run into any specific hurdles setting them up.