agent-bridge

Extract agent work state into a normalized context capsule for handoffs.

Updated Mar 29, 2026
One-click install
npx skills add https://github.com/songlairui/agent-monad --skill agent-bridge-songlairui
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: agent-bridge
Source: https://github.com/songlairui/agent-monad/tree/main/skills/agent-bridge
Command: npx skills add https://github.com/songlairui/agent-monad --skill agent-bridge-songlairui

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill preserves work when switching between AI agents so intent, progress, decisions, and blockers are not lost during handoffs, session saves, or tool changes.

Core Features & Use Cases

  • Context Recovery: Extracts the current task, completed work, unfinished items, and useful discoveries from the active session.
  • Monadic Handoff Updates: Refreshes the standardized .agent-monad/ capsule by writing intent, progress, conventions, and handoff state.
  • Target Agent Adaptation: Generates agent-specific configuration files when moving to Claude Code, Cursor, Codex, or Aider.
  • Use Case: A developer finishes backend work in one agent, then bridges to another agent to continue frontend changes without re-explaining the project state.

Quick Start

Use the agent-bridge skill to save the current agent state and prepare a clean handoff for the next tool or model.

Frequently Asked Questions about agent-bridge

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

FAQPage Schema
How do I preserve context when switching between Claude Code and Cursor?

To preserve context when switching between Claude Code and Cursor, extract intent, progress, decisions, and blockers into a normalized capsule. This captures the active session state so the destination agent receives a clean handoff without losing prior work.

What is the best way to save agent work state before a context window exit?

Saving agent work state before a context window exit involves writing current intent, progress, conventions, and blockers to a standardized capsule. This ensures workflow continuity and prevents data loss when the active session terminates unexpectedly.

Can I generate agent-specific configuration files when moving work to Codex or Aider?

Yes, you can generate agent-specific configuration files when moving work to Codex or Aider. By specifying a target agent during the handoff process, the tool adapts the extracted state into destination-specific formats for immediate use.

How does multi-agent workflow continuity handle blockers and discoveries across sessions?

Multi-agent workflow continuity handles blockers and discoveries by extracting them from the active session and writing them into a shared artifact directory. This standardized context capsule synchronizes state so subsequent agents immediately see unfinished items and useful findings.

What do I need to extract from an active session to ensure workflow continuity across AI agents?

To ensure workflow continuity across AI agents, you need to extract the current task, completed work, unfinished items, and useful discoveries. These elements form a normalized context capsule that refreshes the handoff state for the next model.