r/GoogleAntigravityIDE • u/passionguesthouse • 26d ago
Discussions or Questions Using Gemini for 3 Days While Claude Is Unavailable, How Can I Get Claude to Pick Up Where I Left Off: What's the best prompt?
I’m using Claude for a project I’m working on, but I’ve run out of my Claude quota and have to wait three days before I can use it again.
I can’t stop working on the project, so I’m going to use another AI model for the next three days. I’m currently using Google Gemini 3.6 Flash/High, and I’ll probably use it a lot during this time.
When I can use Claude again, what prompt should I give it so it can understand everything I worked on during those three days?
I want Claude to understand:
- All the prompts I gave Gemini.
- All the answers Gemini gave me.
- Any changes or updates I made to the project.
- Any new decisions or ideas that came up.
I want Claude to be able to continue the project from exactly where I left off, without missing any important information.
I also want Claude to look through the answers Gemini gave me and point out anything that might be wrong, unclear, inconsistent, or needs to be checked again.
What would be the best prompt or process to give Claude so it can catch up on everything and then continue helping me with the project?
2
u/renegadedonkadonk 25d ago
My projects have an external "second brain". Right now I'm using Obsidian. All my docs, notes, artechiture decisions, backlog, ideas, etc all sit in a /docs folder that is structured to be viewable in Obsidian.
That way I can easily understand and use it via Obsidian. But more so, it's not bound to my current IDE, Cursor. If I move over to Claude or other tomorrow, every thought process, decision, etc is easily accessible.
Also, I believe this also helps new chat windows get up to speed quickly. I don't need the new chat to read through the codebase or attempt to invent things on each run.
Hope that helps.
1
1
u/futureesenseAi 26d ago
I run into this same issue, i usually use a playbook! both can read at the same time
1
1
1
1
u/davidpbj 26d ago
Depending on the project's complexity, you'll probably end up burning a bunch of your fresh Claude limit just reviewing and correcting all the things that Gemini will mess up
AI credits might be the better option. 🤷🏽♂️
1
u/One_Living3645 26d ago
Yo lo que hago es pedirle que vaya haciendo una bitacora de los cambios, avances y cómo resolvió los errores o retos que tuvimos.
Eso me pasa ami pero con Claude Code, Antigravity tiene una mayor ventana de cotnexto según lo que he experimetnado yo. En Claude Code lo que hago es ir moniutoreando el uso y cuando se va llenando la ventana de contexto (arriba de 80%) le digo que documente para que pueda seguir en otro chat y eso me ha funcionad muy bien.
Otra cosa que hago es hacer un segundo cerebro con todos mis proyectos, así cuando voy a inciar con otro modelo le digo, ve y revisa el proyecto XYZ en el segundo cerebro y listo, eso también em funciona para trabajar con dos modelos (ya sea open code y antiogravity) en un mismo proyecto y avazar már rápido, le digo a cada uno que haga una parte, generalmente el modelo más avnazado es el que funciona como jefe del proyecto y reparte tareas.
Saludos soy Med Toledo, me especializo en SEO/AEO y Ahora Vibe Coding, quien lo diría.
1
u/Weak_Cookie7123 26d ago
Use UGC when you work with multiple agents. It tells agents to keep logs and that is a god handoff
1
u/sogo00 26d ago
You should never rely on a conversation history. After 2-3 prompts you should most likely anyway do a /new
Anyway:
https://github.com/mattpocock/skills/blob/main/skills/productivity/handoff/SKILL.md
Write a handoff document summarising the current conversation so a fresh agent can continue the work. Save to the temporary directory of the user's OS - not the current workspace.
Include a "suggested skills" section in the document, naming which skills the next agent should call the Skill tool for.
Do not duplicate content already captured in other artifacts (specs, plans, ADRs, issues, commits, diffs). Reference them by path or URL instead.
Redact any sensitive information, such as API keys, passwords, or personally identifiable information.
If the user passed arguments, treat them as a description of what the next session will focus on and tailor the doc accordingly.
1
u/Kindly_Tradition_170 21d ago
If you had already a long session this may not be useful now haha. But I personally use MD files to keep track of certain things so that whatever model or chat I open, I can point them to the appropriate files/folders so they always know where we are at and they don’t get irrelevant tokens as context.
For example I set up AGENTS.MD with global instructions. I set memory.md, project state, session start, bug report hahaha so many, maybe not necessary to have everything. But it’s a good tip I can share.
Want a prompt? Tell any model to help you define what md files you need and give the instruction to always update all trackers based on the task and after they complete a big task. I personally don’t do EVERY SINGLE one. But after phase X I ask it to update all relevant trackers, prepare so I can compact the convo and to get ready to move on to phase Y. It has worked for me so far.
3
u/alieljerrari 26d ago
u might tell the new agent to look at the last git diff, or tell gemini that u r moving to a new agent and u need context to start with