---
title: "Continue an Antigravity session in Codex"
canonical: "https://agentdrive.sh/resume/antigravity-to-codex"
---
# Continue an Antigravity session in Codex

> For the complete documentation index, see [llms.txt](https://agentdrive.sh/llms.txt). Every docs page is also served as markdown at its URL plus `.md`, and the full docs are in one file at [llms-full.txt](https://agentdrive.sh/llms-full.txt).

[Resume across agents](https://agentdrive.sh/resume)

To continue an Antigravity session in Codex, install AgentDrive once with `curl -fsSL agentdrive.sh/install | sh`. After that, a hook in `~/.gemini/config` syncs each Antigravity session. Open Codex in the same project and ask it to resume your session, or mention the AgentDrive skill with `$agentdrive`. Codex loads a handoff brief with the goal, the files touched and the recent turns.

## Steps

1. ### Install AgentDrive

   Run `curl -fsSL agentdrive.sh/install | sh`. It signs you in and wires session sync and resume into every agent it finds on this machine, Antigravity and Codex included. Setup approves the AgentDrive hooks in Codex for you. On an older Codex, approve them once via `/hooks`.

   ```
   curl -fsSL agentdrive.sh/install | sh
   ```

2. ### Work in Antigravity as usual

   A hook in `~/.gemini/config/hooks.json` fires on `SessionStart` and `Stop`. Antigravity has no session-end event, so a session counts as finished after 30 minutes idle. The sync uploads the redacted transcript, plus files the agent wrote that git doesn't track, to `sessions/<project>/antigravity/<session>.md` in your workspace. Before you switch, leave a clear goal and next step in the session; the brief carries them over.

3. ### Resume in Codex

   Open Codex in the same project and ask it to resume your session, or mention the AgentDrive skill with `$agentdrive`. It calls `drive_resume`, which loads the latest session in this project from a different agent. If you run several agents, ask for the session from Antigravity by name, or list sessions with a plain request such as "list my AgentDrive sessions" and pass an id.

   ```
   $agentdrive resume my last AgentDrive session
   ```

4. ### Check the files before continuing

   Ask Codex to check the files on disk before it continues: the brief says what happened, the repo says what is true now.

From a shell, `adrive resume --list` lists this project's sessions and `adrive resume <id>` prints the brief for one.

## Before you switch from Antigravity to Codex

- Antigravity transcripts don't record the project directory, so the AgentDrive hook records it while the session runs. An Antigravity session that ended before the hook was installed has no recorded directory: it is filed under an unknown project and can't be matched to this one.
- Antigravity has no session-end event. Turn-end events re-sync at most every two minutes, and a session is marked finished after 30 minutes idle.
- With auto-context on, Codex is told at session start about up to three recent sessions in this project, the newest from each other agent first, so the Antigravity session shows up before you ask.

In Codex you call a skill by name by typing $ to mention it, so $agentdrive invokes the AgentDrive skill that setup installs. Codex has replaced custom prompts with skills, and current Codex no longer runs the /prompts:agentdrive-resume prompt that setup also writes. [Source](https://learn.chatgpt.com/docs/build-skills).

## What carries over

- The goal, the files touched and the most recent turns, as a compact brief (12,000 characters by default).
- Files the Antigravity agent wrote that git doesn't track, such as plans and notes.
- The full redacted transcript, which stays in your workspace and is searchable later.
- Sessions encrypted with Private Workspace resume with `adrive resume <id>` on a machine that holds your key.

## Frequently asked questions

### How do I pick a specific Antigravity session in Codex?

List sessions with a plain request such as "list my AgentDrive sessions". It calls `drive_sessions`, which takes a platform filter, so asking for `antigravity` sessions shows only Antigravity's. Then resume with the session id.

### Do Antigravity and Codex need to be on the same machine?

No. Signed-in sessions sync to your workspace, so Codex can resume an Antigravity session from another machine with the same AgentDrive account. With a git remote, the project is keyed by the normalized remote, so any clone of the repo matches. Without an account, `adrive resume` reads only this machine's local transcripts.

### Why can't Codex find an older Antigravity session?

Antigravity transcripts don't store the project directory, and the AgentDrive hook records it only for sessions that ran after setup. Older Antigravity sessions sync under an unknown project, so a resume from this project can't match them.

### Can I hand the work back from Codex to Antigravity?

Yes. Sync runs in both directions: Codex sessions sync too, and in Antigravity you ask it to resume your session (the `agentdrive-resume` skill) to load the latest session from another agent.

## Related guides

- [Continue a Codex session in Antigravity](https://agentdrive.sh/resume/codex-to-antigravity), the same handoff in reverse
- [AgentDrive for Antigravity](https://agentdrive.sh/integrations/antigravity) and [AgentDrive for Codex](https://agentdrive.sh/integrations/codex): setup details for each agent
- [Quick start](https://agentdrive.sh/docs/quick-start): install, sign in and run your first handoff

### Other handoffs

- [Continue a Claude Code session in Codex](https://agentdrive.sh/resume/claude-code-to-codex)
- [Continue an OpenCode session in Codex](https://agentdrive.sh/resume/opencode-to-codex)
- [Continue a Cursor session in Codex](https://agentdrive.sh/resume/cursor-to-codex)
- [Continue an Antigravity session in Claude Code](https://agentdrive.sh/resume/antigravity-to-claude-code)
- [Continue an Antigravity session in OpenCode](https://agentdrive.sh/resume/antigravity-to-opencode)
- [Continue an Antigravity session in Cursor](https://agentdrive.sh/resume/antigravity-to-cursor)
