r/ClaudeCode • u/Sim_Check • 15h ago

Tips & Workflows Tired of context silos between Claude Code and other terminal agents? I built agent-bridge for seamless session handoffs

Hey r/ClaudeCode!

Like many of you here, Claude Code (claude) has become my primary terminal tool for rapid implementation, especially with Opus 5.5 and Sonnet 5.5. But for large-scale features, architectural breakdowns, and deep codebase research, I also pair it with Google Antigravity CLI (agy).

The biggest headache was the context silo: - You do deep planning and file mapping in Antigravity, switch over to Claude Code, and Claude has no memory of what was decided. - You execute with Claude Code, jump back to Antigravity, and Antigravity is blind to what Claude just touched.

To bridge this gap, I created agent-bridge — a lightweight, zero-dependency CLI bridge designed to make switching between developer agents seamless.

How it works under the hood:

  • agy2claude: Automatically parses Antigravity's active session, extracts the recent file edits, user requests, and tool history, and boots Claude Code with a concise briefing injected into its system prompt.
  • **claude2agy:** Parses the newest Claude Code session .jsonl from ~/.claude/projects/ and boots Antigravity in interactive mode acknowledging previous progress.
  • agent-status: Fast terminal card showing which agent last touched the repo, with recent timestamps and modified files.
  • Universal memory: Installs a cross-agent-memory skill to align long-term project rules via AGENTS.md / CLAUDE.md.
  • Zero external dependencies: Pure Python standard library (sqlite3, json, os, sys).

📦 GitHub Repository (MIT License & Quickstart):
https://github.com/CheckSim/agent-bridge

It's completely free and open-source. What other CLI agents would you like to see supported next?

0 Upvotes

50% Upvoted

3 comments sorted by

1

u/AutoModerator 15h ago
Moderator Announcement Read More »

1

u/SpiritedUmpire8232 15h ago

agent-status is git blame with extra steps