@notjustyou/antigravity-plugin

Not Just You Antigravity Plugin

Plugin for Antigravity CLI, Antigravity, and Antigravity IDE.

What It Provides

• A Not Just You status skill for AI service status checks.
• A bundled Not Just You MCP server configuration for status lookup and explicit local reporting setup.
• Public status lookups for community reports, installed-client signal aggregates, and official status summaries.
• Optional metadata-only local hook reporting for coarse Antigravity Stop error events.

Install

Install the published package by unpacking it into a local plugin directory, then install that directory with Antigravity:

PLUGIN_TMP="$(mktemp -d)"
npm pack @notjustyou/antigravity-plugin@0.2.3 --pack-destination "$PLUGIN_TMP"
mkdir -p "$PLUGIN_TMP/notjustyou"
tar -xzf "$PLUGIN_TMP/notjustyou-antigravity-plugin-0.2.3.tgz" -C "$PLUGIN_TMP/notjustyou" --strip-components=1
agy plugin install "$PLUGIN_TMP/notjustyou"

Do not use npm install -g for this plugin. Antigravity loads plugin directories, not global npm package locations.

From a workspace checkout:

agy plugin install /path/to/notjustyou/packages/notjustyou-antigravity-plugin

Then start Antigravity CLI or open the Antigravity desktop app and ask a status question:

Is Antigravity CLI down?

You can also ask about a specific Not Just You service id:

Check Not Just You status for google-antigravity-cli.

Manual Plugin Locations

Antigravity can also discover manually placed plugins.

Workspace level:

.agents/plugins/notjustyou/

Global Antigravity 2.0 or IDE level:

~/.gemini/config/plugins/notjustyou/

Antigravity CLI stages installed plugins under:

~/.gemini/antigravity-cli/plugins/notjustyou/

Privacy Boundary

Install-only status lookup does not enable reporting. Antigravity hook reporting is optional and requires explicit setup through the bundled setup MCP tools or CLI fallback.

It does not collect prompt text, request or response bodies, headers, API keys, cookies, source files, diffs, clipboard content, transcript files, exact IP addresses, account emails, machine names, workspace paths, file paths, or local usernames.

The local Not Just You config contains collector credentials. The plugin skills must not read, print, summarize, or display raw config JSON, collectorToken, collector token values, or collectorId. Use the bundled reporting setup tools for state summaries instead of inspecting config files.

Antigravity hook input can include conversation ids, workspace paths, transcript paths, artifact paths, tool arguments, and error strings. This plugin checks local opt-in config before reading hook stdin. After opt-in, the hook script forwards only an allowlisted local envelope to the localhost Not Just You receiver:

• hook_event_name
• service_id
• termination_reason
• has_error
• fully_idle
• client_version

Raw Antigravity hook payloads are not stored, logged, queued, or sent to Not Just You. Public /api/signals is reached only through the local receiver after collector-token, source, service, and opt-in readiness checks pass.

Reporting Setup

Ask Antigravity to set up Not Just You reporting; the setup-reporting skill explains the privacy boundary and asks for confirmation before enabling or disabling reporting.

Each setup request changes only the confirmed Antigravity surface while preserving other already-enabled Claude Code or Cursor reporting surfaces. Within the Antigravity family, choose one active surface at a time: antigravity-cli, antigravity, or antigravity-ide.

Fallback CLI commands:

njy enable antigravity-cli --quiet
njy enable antigravity --quiet
njy enable antigravity-ide --quiet
njy disable antigravity-cli --quiet
njy disable antigravity --quiet
njy disable antigravity-ide --quiet

Keep the local hook receiver running while you want automatic Antigravity reports.