← Back to Skills Marketplace
Context Bridge - No more re-explaining things on model change.
by
Loud Mouthed Media
· GitHub ↗
· v1.0.1
· MIT-0
133
Downloads
0
Stars
0
Active Installs
2
Versions
Install in OpenClaw
/install context-bridger
Description
Maintains and transfers context across sessions, models, and time to avoid repeating information on every new interaction or model switch.
README (SKILL.md)
Context Bridge
The unified continuity system for OpenClaw.
Ensures context persists across sessions, models, and time. Prevents "starting from zero" on every /new.
Version: 1.0
Created: 2026-04-03
Quick Start
Installation
# 1. Install the skill
openclaw skills install https://github.com/loudmouthedmedia/context-bridge
# 2. Run setup to create registry files
cd ~/.openclaw/workspace/skills/context-bridge/scripts
./setup.sh
# 3. Update AGENTS.md (see below)
Setup Script
The setup.sh script auto-discovers and populates all existing skills, crons, and agents:
- Scans
~/.openclaw/workspace/skills/for local skills - Scans
~/.openclaw/skills/for system skills - Checks
openclaw cron listfor active cron jobs - Checks
openclaw agents listand~/.openclaw/agents/for agents - Creates and populates all registry files with actual data
What It Does
Before Context Bridge:
You: /new
Model A: "Hello! How can I help?" [blank slate]
You: [re-explain everything]
You: /new
Model B: "Hello! How can I help?" [blank slate again]
You: [re-explain everything again]
After Context Bridge:
You: /new
Model C: "📧 [email-skill] available, 📈 [analytics-skill] ready.
Working on [Your Project]. Previous model
(GPT-X) scheduled a meeting 30 min ago.
Ready to continue."
Components
1. Registries (The "What Exists")
| Registry | File | Tracks |
|---|---|---|
| Skills | ~/.openclaw/skills-registry.json |
All installed skills |
| Crons | ~/.openclaw/cron-registry.json |
Active scheduled jobs |
| Agents | ~/.openclaw/agents/*/agent.md |
Agent configurations |
| Discovery | ~/.openclaw/skills-discovery.json |
Skill capabilities |
2. Handoff Memory (The "What Happened")
File: ~/.openclaw/model-agnostic-memory/model-handoff.md
- Session-to-session context
- What previous models did
- Active projects
- Recent actions
3. SOPs (The "Rules")
Documentation: ~/.openclaw/workspace/notes/openclaw-reliability-issues.md (Issue #9)
- File responsibility assignments
- Before-adding-content checklist
- Cross-reference comments
Session Startup Protocol
Required by AGENTS.md:
1. Read SOUL.md
2. Read USER.md
3. Read memory files
4. READ CONTEXT BRIDGE FILES:
- ~/.openclaw/skills-discovery.json
- ~/.openclaw/model-agnostic-memory/model-handoff.md
- ~/.openclaw/cron-registry.json
- ~/.openclaw/skills-registry.json
5. ACKNOWLEDGE context in first response
File Responsibilities (SOP)
| File | Responsibility | Must NOT |
|---|---|---|
| AGENTS.md | Session startup rules | Periodic checks |
| HEARTBEAT.md | Periodic health checks | Session setup |
| SOUL.md | Personality/vibe | Technical instructions |
| Context Bridge | Registries & discovery | Implementation |
Usage
Automatic
On /new or model switch: Registries auto-load via AGENTS.md
Manual Fallback
If needed, say: load context
Update Workflow
When adding skills/crons/agents:
- Update appropriate registry
- Update discovery (if new capabilities)
- Update handoff (log the change)
- Git commit
Why "Context Bridge"?
- Context = What the model knows
- Bridge = Connection between isolated sessions/Models
Builds bridges across the memory gap.
Usage Guidance
Before installing or running setup.sh: (1) Inspect scripts/setup.sh yourself (don't run blind). The script uses jq and optionally the openclaw CLI — install jq or expect failures. (2) Verify which repository URL is authoritative (packaged files contain inconsistent GitHub links). (3) Backup ~/.openclaw and review current agent/crons/skill files — the setup will read and aggregate data from those locations and write registry files; those sources may contain secrets or cron payloads. (4) Consider running the script in a sandbox or on a copy of your ~/.openclaw tree first to see what it creates. (5) If you accept it, avoid blindly adding the recommended AGENTS.md startup lines until you confirm the registries contain only the information you want models to see. (6) If you have sensitive tokens in agent workspaces or cron payloads, remove or redact them before running the setup.
Capability Analysis
Type: OpenClaw Skill
Name: context-bridger
Version: 1.0.1
The Context Bridge skill is designed to provide session continuity by managing registries of installed skills, cron jobs, and agent configurations. The primary logic resides in `scripts/setup.sh`, which performs local discovery within the `~/.openclaw` directory and uses `jq` to generate JSON metadata files. The instructions in `SKILL.md` and `README.md` are consistent with the stated purpose of context persistence and do not contain malicious prompt injections or unauthorized data exfiltration commands.
Capability Tags
Capability Assessment
Purpose & Capability
The SKILL.md and scripts implement registries, discovery, and a model-handoff memory which is coherent with the stated 'context bridge' purpose. However, metadata inside the packaged files (clawhub.json) declares 'jq' as required while the skill registry metadata at the top of the review said 'required binaries: none' — an inconsistency. There are also multiple different GitHub repository hostnames referenced (loudmouthedmedia, loudmoutclawmedia, openclaw), which suggests sloppy packaging or incorrect links.
Instruction Scope
Runtime instructions and the setup.sh script explicitly scan and read many user-local paths (~/.openclaw/workspace/skills, ~/.openclaw/skills, ~/.openclaw/agents, openclaw cron/agents output) and then create registry files under ~/.openclaw. Reading and aggregating SKILL.md, agent files, and cron payloads is functionally needed for a global registry, but it also means the skill will collect and write local configuration and any data contained there (which may include sensitive payloads or credentials). The SKILL.md also instructs maintainers to modify AGENTS.md to force session startup behavior, which changes agent startup semantics globally.
Install Mechanism
There is no formal install spec (instruction-only), lowering risk. But a provided scripts/setup.sh is intended to be run by users; the script depends on jq (and optionally the 'openclaw' CLI) even though top-level metadata omitted required binaries. The script will create and modify files under ~/.openclaw, so users must run it intentionally and inspect it before execution.
Credentials
The skill does not request environment variables or external credentials, which is appropriate. However, the setup process pulls data from local agent workspaces and cron payloads (via openclaw commands and file scans). Those sources can contain secrets or tokens; aggregating them into registries/discovery files may inadvertently centralize sensitive data. Because no explicit filters or redaction are visible, this is a proportionality/privacy concern.
Persistence & Privilege
The skill is not force-enabled (always: false) and is user-invocable. It recommends editing AGENTS.md so agents load the created registry files on startup — a legitimate integration point but one that changes agent startup behavior. The skill's ability to be invoked autonomously (disable-model-invocation: false) is the platform default and not flagged alone, but combined with broad file scanning it raises the blast radius if enabled without review.
How to Use
- Make sure OpenClaw is installed (local or Docker)
- Run the install command in chat:
/install context-bridger - After installation, invoke the skill by name or use
/context-bridger - Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.0.1
- Added .gitignore file to manage untracked files in the repository.
- Added LICENSE file to clarify project licensing.
- No changes to functionality or documentation content.
v1.0.0
Context Bridge ensures context persists across sessions, models, and time. Prevents "starting from zero" on every /new or model switch. Provides registries for skills/crons/agents, discovery system, handoff memory, and SOPs to prevent duplication.
I personally HATE explaining what I am doing with the previous model after a change. So this takes care of that.
Metadata
Frequently Asked Questions
What is Context Bridge - No more re-explaining things on model change.?
Maintains and transfers context across sessions, models, and time to avoid repeating information on every new interaction or model switch. It is an AI Agent Skill for Claude Code / OpenClaw, with 133 downloads so far.
How do I install Context Bridge - No more re-explaining things on model change.?
Run "/install context-bridger" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.
Is Context Bridge - No more re-explaining things on model change. free?
Yes, Context Bridge - No more re-explaining things on model change. is completely free, licensed under MIT-0. You can download, install and use it at no cost.
Which platforms does Context Bridge - No more re-explaining things on model change. support?
Context Bridge - No more re-explaining things on model change. is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).
Who created Context Bridge - No more re-explaining things on model change.?
It is built and maintained by Loud Mouthed Media (@loudmouthedmedia); the current version is v1.0.1.
More Skills