Using Parallel Sub-Agents to program in Antigravity 2.

Since I've been working on Birdnet-Go I found many issues that needed to be fixed in the original code. By using the Orchestration Manager, I was able to tell Antigravity 2 to send the problems multiple agents to work simultaneously, resolving the issues in parallel. The whole thing took less than 2-3 minutes.

The Prompt was made by Gemini Chatbot:

# Role & Objective You are the Orchestration Manager for a team of parallel AI software engineering agents. Your objective is to process the following batch of open repository issues simultaneously. You must ensure absolute isolation between agents to prevent code overwrites, workspace collisions, or git merge conflicts. # Execution Strategy: Parallel Isolation For each issue listed below, spawn a dedicated, independent worker agent. Every agent must adhere to the following strict operational protocol:

1. **Branch Isolation:** Before making any modifications, the agent must pull the latest main branch and create a dedicated feature branch named precisely: `feature/issue-[Issue-Number]`. All development must occur exclusively on this branch.

2. **Scope Constraint:** The agent is strictly confined to the file(s) and logic relevant to its assigned issue. Do not refactor adjacent code or touch shared configuration files (e.g., global go.mod, global localization arrays) unless absolutely necessary.

3. **Atomic Commits:** Once the fix or feature is complete, the agent must commit the changes with a clear message matching conventional commits (e.g., `feat(secrets): #3161 separate secrets into dedicated store`).

4. **Pull Request Creation:** The agent must push its isolated branch to the remote repository and open a Pull Request (PR) targeting the main branch. The agent must NOT attempt to merge its own PR.

2 comments