Skip to content

docs(skills): match agy (Antigravity) panes in swarm-cleanup greps (ag-ni1b #agy-swarm-cleanup-grep)#788

Merged
boshu2 merged 3 commits into
mainfrom
docs/ag-ni1b-agy-swarm-cleanup-grep
Jun 6, 2026
Merged

docs(skills): match agy (Antigravity) panes in swarm-cleanup greps (ag-ni1b #agy-swarm-cleanup-grep)#788
boshu2 merged 3 commits into
mainfrom
docs/ag-ni1b-agy-swarm-cleanup-grep

Conversation

@boshu2
Copy link
Copy Markdown
Owner

@boshu2 boshu2 commented Jun 6, 2026

What

ntm now maps its gemini agent slot to agy --dangerously-skip-permissions (Antigravity), so the gemini-family pane runs as an agy process. The system-tuning swarm-cleanup reference discovered and counted swarm agents with grep -E 'claude|codex|gemini' in two places:

  • the confused-long-horizon-agent finder (ps ... | grep -E ...)
  • the post-cleanup verification count (pgrep -af ... | wc -l)

Both silently miss agy panes post-migration → confused-agent cleanup skips them and the agent count under-reports.

Change

Add agy|antigravity to both matchers and a one-line note explaining the slot mapping. Keep gemini for older sessions that still launch it.

Scope

In-repo slice of ag-ni1b (gemini-cli → Antigravity migration). This advances the bead but does not close it — the bulk (external/user-global skills, both-host verification, dueling-idea-wizards + code-review-swarm end-to-end agy node) remains.

Verification

scripts/pre-push-gate.sh --fast → passed (the 2 WARNs are pre-existing, unrelated: unknown-flag noise in executable-spec link-integrity).

Closes-scenario: ag-ni1b#agy-swarm-cleanup-grep
Bounded-context: BC5-Runtime
Evidence: skills/system-tuning/references/agent-swarm-cleanup.md

…greps (ag-ni1b #agy-swarm-cleanup-grep)

ntm now maps its `gemini` agent slot to `agy --dangerously-skip-permissions`,
so the gemini-family pane runs as an `agy` process. The agent-swarm-cleanup
reference discovered and counted swarm agents with `grep -E 'claude|codex|gemini'`,
which silently misses agy panes post-migration — confused-long-horizon-agent
cleanup and the post-cleanup agent count would both under-report.

Add `agy|antigravity` to both matchers (the confused-agent finder and the
verification count) and note why, keeping `gemini` for older sessions that
still launch it. In-repo slice of ag-ni1b (gemini-cli -> Antigravity migration);
the external/both-host skill edits remain.

Closes-scenario: ag-ni1b#agy-swarm-cleanup-grep
Bounded-context: BC5-Runtime
Evidence: skills/system-tuning/references/agent-swarm-cleanup.md
… #agy-swarm-cleanup-grep)

Mirror the agy/antigravity grep change into the skills-codex twin and
refresh generated hashes. Source skill reference was updated in the
prior commit; this propagates it to the codex artifacts so the
codex-hash and codex-artifact-metadata gates pass.

Closes-scenario: ag-ni1b#agy-swarm-cleanup-grep
Bounded-context: BC5-Runtime
Evidence: skills-codex/system-tuning/references/agent-swarm-cleanup.md
@boshu2 boshu2 merged commit 242fc16 into main Jun 6, 2026
16 checks passed
@boshu2 boshu2 deleted the docs/ag-ni1b-agy-swarm-cleanup-grep branch June 6, 2026 12:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant