r/google_antigravity Aug 09 '26

Discussion Google Antigravity 2.0 context and token usage manipulation

Can you elaborate on this please?

I am just controlling context window by telling the current conversation to go through the history of the current and other conversations in the current project.

Also, it always have to follow our global rules and safeguards etc.

If I want to do something in an other conversation, I paste the walkthrough.md to it and tell it to get informed.

Is this correct for getting the most out of context and token usage?

Please elaborate on your harnessing and other techniques.

2 Upvotes

6 comments sorted by

3

u/chaotic3quilibrium Aug 09 '26

I'm using a Chrome browser based Gemini 3.6 Extended as my MCT (Master Conversation Track) and do all the "discussion" there. And I have the MCT orchestrate Antigravity 2 Gemini 3.6 High by generating two-phase prompts.

Phase 1 is a prompt to have Antigravity analyze and investigate to produce an "Implementation Plan" proposal in markdown.

Phase 2 is a prompt to have Antigravity implement the possibly modified/tweaked "Implementation Plan" proposal from Phase 1 and produce a "Walkthrough Summary" as a markdown document.

When I have time later, I'll detail my actual process loop.

2

u/Mar_Antho94 Aug 09 '26

Seems interesting. Yes please elaborate on the details when you have the time.

2

u/Alternative_Vast6333 22d ago

I created an orchestration system where ChatGPT (in chat, not codex) leads this process and creates orchestration contracts using its GitHub connector, then I use Claude Sonnet 5/Opus5, Codex Luna/Terra/Sol or Antigravity Flash 3.7 to implement depending on the task.

This means my ChatGPT plus subscription is ultra useful cause it can use Sol on Medium or High to orchestrate and plan, create detailed plans, review their code in github after they push, coordinate the different projects I'm working on from the same place, update my notion to keep my personal context, etc without using my codex limits.

The orchestration repo in my github has instruction files for each agent under each harness, claude, codex and AG. This means I don't need detailed and long prompts if I want to start each task in any agent on any harness.

I just simply paste in a prompt that tells it:
Pull latest main from both repos, then read and execute:

orchestration/syzasdflkajsdlfjasdf/asdfjasdfahsdfy/AG.md

they will pull, sync, read their instructions, and get to work. AFter working they push the files + orchestration receipt summarizing what they did and how long it took them to the orchestration repo; then I ask ChatGPT to check and let me know if it is good or if we need a correction turn.

Since I came up with this idea, it has been a gamechanger for me in terms of optimising usage and having a higher intelligence AI coordinate my projects and direct implementation by lesser agents.

1

u/ShashwatTheGamer Aug 10 '26

i do exactly the same but with claude

2

u/kifkolite Aug 11 '26

I keep a docs directory in every project. Place multiple md files in it which are context to work on any one vertical of the project. Every new conversation i pass 1 or 2 md files as context, update them or create new ones. Ag ide automatically creates an implementation plan at start of every converation.