Antigravity
Apothem harness adapter for Antigravity (Preview).
Vendor: Antigravity
Install name: antigravity
Status: Preview
Native config: ~/.gemini/GEMINI.md plus
~/.gemini/antigravity-cli/plugins/apothem/
Installation
apothem install --harness antigravityThe adapter renders the shared profile to ~/.gemini/GEMINI.md and installs
Apothem support cohorts as an Antigravity CLI plugin.
Files written: ~/.gemini/GEMINI.md,
~/.gemini/antigravity-cli/plugins/apothem/plugin.json,
~/.gemini/antigravity-cli/plugins/apothem/skills/,
~/.gemini/antigravity-cli/plugins/apothem/rules/,
converted local helper definitions inside the plugin,
~/.gemini/antigravity-cli/plugins/apothem/.apothem/support/templates/, and
~/.gemini/antigravity-cli/plugins/apothem/.apothem/support/hooks/.
The Apothem block in ~/.gemini/GEMINI.md ends with an Apothem support files
section that names the absolute directory each repository-style citation
resolves against: rules/<name>.md under the plugin's rules/, and
templates/... and hooks/... under the plugin's .apothem/support/.
Plugin rules. Antigravity discards any file in a plugin's rules/
directory that does not open with a valid trigger
(Antigravity rules documentation), so
each Apothem rule is converted on install. A rule that always applies gets
trigger: always_on; a rule scoped to paths gets trigger: glob with the same
patterns in globs; any other rule gets trigger: model_decision. Every rule
keeps its description. Five rules always apply: agnostic-posture,
authority-inquiry, session-closure, context-management, and the rule index
apothem-rule-index, which names every other rule and when to read it. The other
rules carry trigger: glob. Antigravity shares a 20,000-token budget across
always-on rules and turns the largest into on-demand pointers past it; the five
rules come to about 11,000 tokens, so none is turned into a pointer.
Plugin manifest. plugin.json carries only name and description, the
two keys Antigravity's plugin schema admits.
Plugin helpers. Helper definitions in the plugin's agents/ directory
carry name and description. Antigravity's tools list uses its own tool
names, and the docs warn that an unknown name can hang the subagent, so no tool
list is emitted and helpers inherit the parent's tools. Because nothing on
Antigravity enforces a read-only limit, those helpers' descriptions drop the
"read-only" label.
Shared user anchor. ~/.gemini/GEMINI.md is also the user-scope anchor for
Gemini-family tooling. The Antigravity adapter keeps its extra Apothem material
inside the apothem plugin under ~/.gemini/antigravity-cli/plugins/ so it
does not claim generic Gemini CLI project directories. Because more than one
tool loads ~/.gemini/GEMINI.md, the Apothem block there is written as global
guidance that names no single tool as its reader.
Profile-to-native-config mapping
The adapter reads Apothem's shared profile and renders the instruction anchor
plus support cohorts on every apothem install or apothem update run.
Compatibility notes
Preview adapter. The GEMINI.md anchor is active instruction content; the
Antigravity plugin preserves converted command skills, reusable skills, local
helper definitions, rules, templates, and hook support material in a clear
Apothem-owned namespace.
Hook files are not registered as active Antigravity hook events until the
adapter owns a schema translation layer for Antigravity hooks.json.
Verification
apothem verify --harness antigravityThe verify command confirms that:
- The native context file exists at the expected path.
- The plugin manifest
plugin.jsonexists, is non-empty, and parses as JSON. Verify does not check the plugin name; inspect that field yourself after changing it.
Updating
apothem update --harness antigravityRe-derives the native config from the current shared profile state. Run after
editing ~/.config/apothem/profile.yaml or upgrading the installed Apothem
package.
Uninstalling
apothem uninstall --harness antigravityRemoves the Apothem block from ~/.gemini/GEMINI.md and keeps any other text
in it. The file is deleted only when nothing else remains in it. Also removes
Apothem's keys from plugin.json in the plugin folder
~/.gemini/antigravity-cli/plugins/apothem/ and keeps yours, and removes the
Apothem files in that folder's skills/, rules/, agents/, and
.apothem/support/ subfolders; other files there stay. Each file is backed up
under ~/.apothem/backups/ before it is changed or removed. The shared profile
YAML and Apothem engine are unaffected.
Conformity gate
python -m apothem.conformity.gate --all .Troubleshooting
| Symptom | Fix |
|---|---|
| Config file not found | Re-run apothem install --harness antigravity |
| Verification failed | Run apothem update --harness antigravity, then verify again |
| Unexpected config content | Check ~/.config/apothem/profile.yaml or --profile PATH, then re-run apothem update --harness antigravity |
Configuration knobs
| Flag | Default | Description |
|---|---|---|
--dry-run | false | Preview install without writing files. |
See also
- All harnesses — the full catalog of supported tools
- Install guide — install Apothem into this harness
apothem harnessesreference — list and inspect adapters from the CLI