[MarkusNeusinger]

Summary

• Gemini works independent packages in parallel, in one PR (owner, 2026-10-30). When a brief task has two or more packages marked independent, Gemini in the owner's agy session acts as coordinator: one agy subagent per package (invoke_subagent), at most eight at a time (the owner says when the quota runs short), each in its own Git worktree on a package branch gemini/<slug>-<k> that it pushes before it ends, without a PR or changelog fragment. The coordinator then merges the package branches with git merge --no-ff into gemini/<slug>, runs every package's acceptance and the gates on the result, writes one fragment, and opens one draft PR, because every PR costs a Copilot round, a fragment, CI, a merge, and a deploy. Coupled packages still run one after another on gemini/<slug>. One start line, /gemini-task <slug>, covers every package. Claude reviews per merge commit, so a drifted package stands out, and deletes the package branches after the merge. Without worktree isolation Gemini falls back to sequential work instead of letting two agents share the clone.

• Basis: a multi-agent research run against the Antigravity docs (23 of 24 sampled claims verified against their sources). Subagents run concurrently, start without the parent's conversation, can each get an isolated Git worktree, and report back; agy deletes the worktree when the subagent ends, hence push-before-finish. /teamwork (fixed roles, paid plans) builds in ~/teamwork_projects/<project> with no branches or PRs in its docs, so the skill rules it out for this repository. The docs give no concurrency limit and no quota figures, so the cap of eight is a starting value. Parallel agents inside the owner's own session are a documented product feature; the FAQ's ban covers a third-party agent driving agy, which stays in force.

• agy-permissions.json gains the git -C <clone> allow and deny forms (Gemini runs Git with absolute paths, and agy matches prefixes word by word), [ and false, and git merge --no-ff for the coordinator, while merging main stays denied. Regex denies close pushes whose refspec destination is main (gemini/foo:main), bulk pushes, and remote deletions, which a gemini/ prefix allow would otherwise let through (Copilot, high). It equals the owner's live settings.

• Correction: the 2026-10-16 forum reply on topic 189905 is not marked as Google staff, so the skills, the guardrails, and the gemini_review.py docstring no longer call it one; Google's FAQ remains the authority.

• Two Copilot rounds addressed: coupled package agents continue on the shared branch, packages are matched by an exact <slug>-<number>.md, one coordinator session per task, single commands in the gate block, and the brief template's branch line by package kind.

Plan

N/A

Test plan

• tests/unit/test_agent_instructions.py: 36 passed
• ruff check and ruff format --check on gemini_review.py (docstring only)
• agy-permissions.json is valid JSON and equals the owner's live permissions block with the home path generalised
• uv run python -m tools.changelog check --base origin/main
• Unverified until the first multi-package brief: whether the CLI's invoke_subagent offers the worktree mode (the CLI docs do not describe it; the CLI changelog v1.2.10 mentions subagent worktrees)
• No Gemini Flash check: instruction files, a JSON reference, a docstring, and a changelog fragment only

🤖 Generated with Claude Code

[Copilot]

🟡 Changes recommended

Approval is blocked by an unaddressed critical permission-rule bypass that could allow pushes directly to the protected branch, along with several documentation and workflow inconsistencies.

5 open issues

• Prevent allowed push rules from bypassing protected branches · New
• Make template branch names conditional on package kind · New
• Align setup instructions with the single coordinator flow · New
• Restrict package fallback glob to numeric suffixes · New
• Update Copilot instructions for parallel package coordination · New

What changed in this PR

This PR expands the Gemini task workflow to run independent packages in parallel through isolated agy subagents while keeping coupled packages sequential. It also updates Git permissions, safety guidance, provenance wording, and changelog documentation.

Changes:

• Documents package classification, parallel coordination, isolated worktrees, branch naming, and draft PR handoffs.
• Extends agy Git permissions for the dedicated Gemini clone.
• Corrects the attribution of the 2026-10-16 forum reply across related guidance and documentation.
• Records the updated workflow in the changelog.

File	Description
CLAUDE.md	Updates agent-selection guidance for parallel Gemini packages.
changelog.d/​gemini-scale-out.md	Records the new Gemini package workflow.
.claude/​skills/​zweitmeinung/​SKILL.md	Corrects the forum-reply attribution in safety guidance.
.claude/​skills/​zweitmeinung/​gemini_review.py	Removes the incorrect staff-attribution claim from the module docstring.
.claude/​skills/​gemini-task/​SKILL.md	Defines package classification, parallel subagents, worktree handling, and multi-package startup.
.claude/​skills/​gemini-task/​agy-permissions.json	Adds path-qualified Git permissions and additional deny rules.
.claude/​guardrails.md	Documents parallel Gemini execution and the corrected forum-reply attribution.

_{Review effort: Lite}

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

[Copilot]

🟡 Changes recommended

Active critical and moderate findings remain in the task workflow and permission configuration, including unsafe package matching, incorrect coupled-branch handling, an unsplit approval-triggering gate, and an overly broad directory-change allow rule.

4 open issues

• Numeric suffix glob matches unrelated task files · New
• Coupled workers are assigned the wrong package branch · New
• Broad directory allow permits access to the wrong checkout · New
• Gate still chains commands and triggers approval prompt · New

5 resolved since last review

• Prevent allowed push rules from bypassing protected branches
• Update Copilot instructions for parallel package coordination
• Restrict package fallback glob to numeric suffixes
• Align setup instructions with the single coordinator flow
• Make template branch names conditional on package kind

_{Review effort: Lite}

[Copilot]

🟡 Changes recommended

Approval is blocked by an unresolved critical path-traversal permission issue and a missing documented package-branch integration step.

1 open issue

• Create the package integration branch before merging · New

1 previously missed issue

In code that hasn't changed since last review

Constrain git -C allows to the exact clone path

.claude/​skills/​gemini-task/​agy-permissions.json:89

The new git -C allow entries are prefix-based, so a command such as git -C /home/<user>/projects/anyplot-agy/../anyplot add ... begins with the allowed clone path but resolves to the shared checkout. That bypasses the dedicated-clone rule and reintroduces the path-traversal problem that was removed for cd ..; constrain these rules to the exact clone path (or explicitly deny traversal) before relying on them for isolation.

This issue also appears in the following locations of the same file:

• line 157
• line 159

4 resolved since last review

• Broad directory allow permits access to the wrong checkout
• Coupled workers are assigned the wrong package branch
• Numeric suffix glob matches unrelated task files
• Gate still chains commands and triggers approval prompt

_{Review effort: Lite}