Skip to content

Add Antigravity 2 Support#281

Closed
pawelad wants to merge 3 commits into
pbakaus:mainfrom
pawelad:pawelad/add-antigravity-2-support
Closed

Add Antigravity 2 Support#281
pawelad wants to merge 3 commits into
pbakaus:mainfrom
pawelad:pawelad/add-antigravity-2-support

Conversation

@pawelad

@pawelad pawelad commented Jun 20, 2026

Copy link
Copy Markdown

Summary

Adds Antigravity 2.0 (https://antigravity.google) as a 14th first-class harness alongside Cursor, Claude Code, Gemini, Codex, Copilot, Kiro, OpenCode, Pi, Qoder, Trae, Trae China, and Rovo Dev.

Antigravity ships a documented Agent Skills system at .agent/skills/{name}/SKILL.md (per https://antigravity.google/docs/skills), so it slots onto the existing transformer pipeline. We target the legacy .agent/ singular path rather than .agents/ (Antigravity's stated current default) deliberately: .agents/skills/impeccable/ is already Codex-flavored content owned by the existing agents provider (GPT naming, $-prefixed commands baked into the body), and reusing it would clobber that output. See docs/HARNESSES.md's Skill Directory Structure section for the full trade-off.

Antigravity Workflows (.agent/workflows/, description-only frontmatter, slash-invoked saved prompts run in the main thread) aren't an equivalent to Claude's isolated, tool-restricted subagent dispatch, so no workflow file is generated for manual-edit-applier; Antigravity ships skills only for now.

Fixes #51

Type of change

  • New / updated skill reference (new harness target)
  • Documentation update
  • Build system / tooling
  • New command
  • New anti-pattern guidance
  • Bug fix
  • Other:

What changed

  • scripts/lib/utils.js - antigravity added to PROVIDER_PLACEHOLDERS.
  • scripts/lib/transformers/providers.js - antigravity provider entry: configDir: '.agent', spec-standard frontmatterFields (license, compatibility, metadata, allowed-tools) per Antigravity's own documented field constraints.
  • cli/bin/commands/skills.mjs - .agent added to PROVIDER_DIRS/PROVIDER_ALIASES/PROVIDER_DISPLAY/PROVIDER_INPUT_ORDER; three GLOBAL_HARNESS_HINTS entries for Antigravity's nested global homes (~/.gemini/antigravity{,-cli,-ide}).
  • cli/lib/download-providers.js - .agent added to the file-download allowlist.
  • skill/scripts/pin.mjs - .agent added to HARNESS_DIRS.
  • .github/workflows/sync-generated-output.yml - .agent added to GENERATED_PATHS so future skill/** changes keep this harness in sync post-merge.
  • docs/HARNESSES.md - Antigravity added to all relevant tables, including confirmed (not TBD) support for license/compatibility/metadata/allowed-tools per Antigravity's own spec docs.
  • README.md, AGENTS.md, docs/DEVELOP.md, .github/ISSUE_TEMPLATE/feature_request.md, .github/PULL_REQUEST_TEMPLATE.md - Antigravity added to provider lists/checklists.
  • .agent/skills/impeccable/ - full skill tree (SKILL.md, 28 reference files, 64 scripts) committed, matching how other harness output dirs are tracked.

Checklist

  • Source files updated in source/
  • bun run build ran successfully
  • bun test passes
  • Tested with at least one provider (Cursor / Claude Code / Gemini CLI / Codex / Copilot / Kiro / OpenCode / Qoder)
  • README / DEVELOP.md updated if needed

Note

Low Risk
Changes are additive harness/build and committed generated assets; no auth, data, or production runtime paths. Main risk is maintainability from a large synced tree and path confusion between .agent and .agents.

Overview
Adds Antigravity 2.0 as a first-class harness so Impeccable installs under .agent/skills/impeccable/, matching Antigravity’s Agent Skills layout while deliberately avoiding .agents/ (already used for Codex-flavored output).

The build and distribution path is extended: an antigravity provider in the transformer pipeline, CLI skills / download / pin wiring, sync workflow coverage, and docs/README/checklist updates. The PR commits the generated skill tree (SKILL.md, reference command docs, scripts) like other harness output dirs.

Antigravity Workflows are not generated for flows that depend on isolated subagent dispatch (e.g. manual-edit-applier); this harness ships skills only for now.

Reviewed by Cursor Bugbot for commit 285b11a. Bugbot is set up for automated code reviews on this repo. Configure here.

@pawelad pawelad requested a review from pbakaus as a code owner June 20, 2026 10:57
@greptile-apps

greptile-apps Bot commented Jun 20, 2026

Copy link
Copy Markdown

Too many files changed for review. (121 files found, 100 file limit)

@@ -21,6 +21,7 @@ concurrency:

env:
GENERATED_PATHS: >-
.agent

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

CI omits generated agent path

Medium Severity

The sync workflow now regenerates and commits .agent, but the CI “Verify generated tracked outputs” step never runs git diff on .agent. Pull requests can pass while .agent/skills/impeccable is out of date with bun run build, unlike .agents, .claude, and the other checked paths.

Fix in Cursor Fix in Web

Reviewed by Cursor Bugbot for commit 47322cb. Configure here.

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

As far as I understand, .agent was a symptom of a bigger gap: the verify step's been a no-op since the build was split source-first/release in 972f5b1 (nothing in that CI job touched the root harness dirs at all). Fixed in 285b11a: Build step now runs build:release, and the path list matches GENERATED_PATHS in full.

bun run build:release had only partially regenerated the already-tracked
provider pin.mjs files after the .agent HARNESS_DIRS addition; this finishes
that sync so all provider copies agree with skill/scripts/pin.mjs.

Also fixes ci.yml's "Verify generated tracked outputs" step, which has been
a no-op since 972f5b1 switched the Build step to source-first (skip-root-sync):
nothing in that job touched the checked-out root harness dirs, so the git diff
check could never fail. Points the Build step at build:release and brings the
path list in line with sync-generated-output.yml's GENERATED_PATHS (adds
.agent, .kiro, .opencode, .pi, .qoder, .rovodev, .trae, .trae-cn, which were
all missing).

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

@cursor cursor Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Cursor Bugbot has reviewed your changes using default effort and found 1 potential issue.

There are 2 total unresolved issues (including 1 from previous review).

Fix All in Cursor

❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.

Reviewed by Cursor Bugbot for commit 285b11a. Configure here.


You MUST do these steps before proceeding:

1. Run `node .agent/skills/impeccable/scripts/context.mjs` once per session. If you've already seen its output in this conversation, do not re-run it. The script either prints the project's PRODUCT.md (and DESIGN.md when present) as a markdown block, or tells you it's missing. Follow whatever it prints. **If it reports `NO_PRODUCT_MD`, stop and follow `reference/init.md` before doing anything else.** If the output ends with an `UPDATE_AVAILABLE` directive, follow it (ask the user once about updating, then continue). It never blocks the current task.

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Allowed tools block setup scripts

High Severity

Antigravity’s generated skill frontmatter restricts tools to Bash(npx impeccable *), but mandatory setup and routing tell the agent to run bundled helpers via node .agent/skills/impeccable/scripts/*.mjs. If Antigravity enforces allowed-tools, those required steps cannot run and the skill breaks at session start.

Fix in Cursor Fix in Web

Reviewed by Cursor Bugbot for commit 285b11a. Configure here.

@pbakaus

pbakaus commented Jun 21, 2026

Copy link
Copy Markdown
Owner

Thanks for this! It would be great if you could fix or dismiss (in case of false positives) the code review. I'll take a look afterwards.

@pbakaus pbakaus added the waiting on contributor Waiting for the PR author to respond or make changes label Jul 8, 2026 — with ChatGPT Codex Connector
@github-actions github-actions Bot added blocked: ci Latest commit has failing required checks blocked: review threads Unresolved review feedback or requested changes remain stale Inactive PR that may be closed soon blocked: merge conflicts PR cannot merge until conflicts are resolved labels Jul 9, 2026
@github-actions github-actions Bot closed this Jul 10, 2026
Repository owner deleted a comment from github-actions Bot Jul 10, 2026
Repository owner deleted a comment from github-actions Bot Jul 10, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

blocked: ci Latest commit has failing required checks blocked: merge conflicts PR cannot merge until conflicts are resolved blocked: review threads Unresolved review feedback or requested changes remain stale Inactive PR that may be closed soon waiting on contributor Waiting for the PR author to respond or make changes

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Feature] Add support for Google Antigravity Skills

2 participants