Session Bridge

Keep context coherent across surfaces (Telegram / WhatsApp / TUI) and agents (Eddie ↔ Jon ↔ Cipher ↔ Sage ↔ Picasso) using lightweight topic capsules — without syncing full transcripts or adding load to the memory system.

Core Concept

Each active work thread gets a capsule — a small JSON file keyed by topic:

CODEBLOCK0

Capsules hold only what matters: goal, status, decisions, open questions, next action. They are transient working state, not long-term memory. They do not replace MEMORY.md, daily logs, or the ontology graph — they sit on top as a coordination layer.

Script

CODEBLOCK1

Commands

Create a capsule

Update a capsule (after decisions, handoffs, progress)

Get a briefing for session start (hydrate)

Output (~150–350 tokens):
CODEBLOCK5

Cross-agent handoff

python3 $SCRIPT handoff \
  --topic "session-bridge-design" \
  --to "agent:main:telegram:direct:7550791652"

See all active capsules

Clean up stale capsules

python3 $SCRIPT expire --max-age-hours 48

Bridging Surfaces (Telegram ↔ WhatsApp ↔ TUI)

Option A — Config routing (recommended first step)

Add identityLinks to openclaw.json to collapse the same human across surfaces into one canonical session per agent:

CODEBLOCK9

This makes Telegram-Eddie and WhatsApp-Eddie share the same session — no bridging needed. TUI uses a different mechanism (main session key).

Option B — Capsule hydration on surface switch

When the same canonical session is not possible (TUI ↔ Telegram, or different agent entirely):

1. 1. On the outgoing surface, refresh the relevant capsule:

   python3 $SCRIPT refresh --topic <topic> --next-action "..."
   

1. 2. On the incoming surface, hydrate at session start:

   python3 $SCRIPT hydrate --topic <topic>
   

1. 3. Inject the briefing as context before responding.

Bridging Agents (Jon → Eddie, Cipher → Eddie)

When finishing a delegation task, the completing agent should:

1. 1. Refresh the capsule with results:

1. 2. Generate a handoff and deliver via sessions_send:

Eddie reads the brief and continues — no re-explaining needed.

What Goes Where

Capsules are not a replacement for memory — they are short-lived working state that gets discarded when a topic concludes.

Token Cost

Hydration adds <0.2% of a 200k context window per session. Stale capsules add zero cost (they're just files).

Agent Protocol (Team Rules)

• - On delegation: create or refresh capsule before sessions_send-ing a task
• On completion: refresh capsule with outcome + next action, then handoff
• On surface switch: hydrate the relevant capsule at session start
• On topic close: set --status done, let expire cleanup handle it
• Never: dump full session transcripts into capsules (defeats the point)

Example: Full Cross-Agent Flow

CODEBLOCK14

Setup

No dependencies beyond Python 3.8+. Works immediately after install:

CODEBLOCK15