> For the complete documentation index, see [llms.txt](https://ai-os-and-trend-finder.gitbook.io/ai-os-and-trend-finder-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ai-os-and-trend-finder.gitbook.io/ai-os-and-trend-finder-docs/.spec_system/archive/phases/phase_22/session_02_antigravity_usage_consumers.md).

# Session 02: Antigravity Usage Consumers

**Session ID**: `phase22-session02-antigravity-usage-consumers` **Status**: Complete **Estimated Tasks**: \~14-20 **Estimated Duration**: 2-3 hours

***

## Objective

Wire the validated Antigravity data from Session 01 into the usage panel and home ROI strip so free Antigravity work is visible without weakening existing Codex, Claude, ChatGPT, and OpenRouter usage semantics.

***

## Source Reference Detail

### A6 Usage Panel Antigravity Row

* v2.3 Antigravity "free - no quota" service row: [V23/src/components/usage-panel.tsx:143](https://github.com/moshehbenavraham/ai-os/blob/main/home/aiwithapex/projects/claudeos/claude-os-v2.3/src/components/usage-panel.tsx:143) through `:179`.
* v2.3 logo map: [V23/src/components/usage-panel.tsx:301](https://github.com/moshehbenavraham/ai-os/blob/main/home/aiwithapex/projects/claudeos/claude-os-v2.3/src/components/usage-panel.tsx:301) through `:305`.
* aios service list currently includes `Claude`, `ChatGPT`, `Codex`, and `OpenRouter`: [AIOS/src/components/usage-panel.tsx:23](https://github.com/moshehbenavraham/ai-os/blob/main/home/aiwithapex/projects/aios/src/components/usage-panel.tsx:23).

### A7 Home ROI Chip

* v2.3 adds `antigravity.usage.savedEquivalent` into the ROI or "Tokens used" headline and a purple attribution chip: [V23/src/routes/index.tsx:16560](https://github.com/moshehbenavraham/ai-os/blob/main/home/aiwithapex/projects/claudeos/claude-os-v2.3/src/routes/index.tsx:16560) through `:16600`.
* aios ROI strip lives in `AIOS/src/routes/index.tsx` and `AIOS/src/lib/home-transforms.ts`.

***

## Scope

### In Scope (MVP)

* Add an Antigravity usage-panel row gated on `detection.apps.antigravity.usage`.
* Add or reuse an Antigravity logo asset/map entry without disturbing the existing Codex split from ChatGPT.
* Display "free" and "no quota" semantics consistent with v2.3 while using aios copy and component conventions.
* Add `antigravity.usage.savedEquivalent` to home ROI math through `home-transforms`.
* Render a gated Antigravity attribution chip on the home ROI strip.
* Add tests for absent Antigravity data, present Antigravity usage, zero saved-equivalent, and existing service rows.

### Out of Scope

* Creating Antigravity detection data; Session 01 owns that.
* Changing Claude, ChatGPT, Codex, or OpenRouter usage calculations.
* Hardcoding ROI values in the UI without validated live data.

***

## Prerequisites

* [ ] Phase 22 Session 01 complete.
* [x] Phase 22 Session 01 complete.
* [x] Confirm `usage.savedEquivalent` shape and fallback defaults.
* [x] Confirm current usage-panel logo/import conventions.

***

## Deliverables

1. Antigravity service row in the usage panel.
2. Home ROI saved-equivalent integration.
3. Gated Antigravity attribution chip.
4. Focused UI and transform tests.

***

## Success Criteria

* [x] Antigravity row appears only when validated data supports it.
* [x] Existing service rows remain intact, including Codex as separate from ChatGPT.
* [x] ROI totals include Antigravity saved-equivalent value when present.
* [x] The attribution chip is hidden for absent or zero-value Antigravity data.
* [x] Tests cover present, absent, and zero-value states.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://ai-os-and-trend-finder.gitbook.io/ai-os-and-trend-finder-docs/.spec_system/archive/phases/phase_22/session_02_antigravity_usage_consumers.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.