session-sync

Synchronizes Antigravity CLI conversation sessions across machines using Git remote refs.

9|Updated Jul 8, 2026
One-click install
npx skills add https://github.com/jerrylin96/dotgemini --skill session-sync-jerrylin96
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: session-sync
Source: https://github.com/jerrylin96/dotgemini/tree/main/skills/session-sync
Command: npx skills add https://github.com/jerrylin96/dotgemini --skill session-sync-jerrylin96

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve? Continuing an AI coding conversation on a different computer is normally impossible because session transcripts, artifacts, and uncommitted workspace changes live only on the local machine. This Skill packages the entire session state and syncs it through a shared Git remote so work can resume anywhere. ## Core Features & Use Cases - Push Sessions: Archive the conversation transcript, brain directory, metadata, and uncommitted changes into a tarball stored as a Git blob under refs/gemini-sessions/<session-id> and push it to origin. - Pull and Restore: Fetch a session by Conversation ID, align the local branch to the recorded commit, apply the workspace patch, and restore conversation files, with interactive handling for dirty workspaces (abort, stash, or overwrite). - List and Clear: Enumerate all synced sessions with local/remote status, and delete session refs locally and on the remote, individually or in bulk. - Use Case: You start a debugging session with the Antigravity CLI on your desktop, push the session before leaving, then pull it on your laptop at home and continue the exact conversation with the same code state. ## Quick Start Ask the agent to push the current conversation session to the Git remote so you can restore it on another machine.

Frequently Asked Questions about session-sync

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I sync an AI CLI conversation session to another computer?

Run the sync script's push command on the source machine to archive the transcript, metadata, and uncommitted changes into a Git ref pushed to origin. On the destination machine, run pull with the Conversation ID to restore the session and workspace state.

How do I restore a Git-backed conversation session with uncommitted changes?

Use the pull command with the session ID. If your workspace has uncommitted changes, the script returns a dirty status and you can rerun with --on-dirty stash to stash them or --on-dirty overwrite to discard them before applying the session.

Does session sync require a Git remote repository?

Yes, pushing and pulling sessions requires a configured origin remote since refs are transferred via git push and fetch. Listing and clearing can inspect local refs, but cross-machine sync depends on the shared remote.

What happens to my local commits when pulling a synced session?

The pull operation runs git reset --hard to align your branch to the session's recorded commit, which discards committed local work ahead of that commit. The dirty-state check only protects uncommitted changes, so verify your branch has no unpushed commits first.

How do I delete synced session data from the Git remote?

Run the clear command with a specific Conversation ID to delete that session's refs locally and on origin, or use the --all flag to remove every synced session. The script reports which refs were deleted locally and remotely.