← Back to Plugins
Tools

Session Mirror

LogicOcean By LogicOcean 👁 87 views ▲ 0 votes

OpenClaw plugin that mirrors agent session output to AgentComm rooms

Homepage GitHub

Install

npm install
   npx

Configuration Example

{
  "agentcommUrl": "http://192.168.1.125:8083",
  "agentcommJwt": "your-agentcomm-jwt",
  "enabled": true
}

README

# Session Mirror - OpenClaw Plugin

An OpenClaw plugin that automatically mirrors agent session output to AgentComm rooms.

## Overview

This plugin captures agent output after each turn and posts it to the corresponding AgentComm task room. Agents won't need to remember to post notes—their output is captured automatically.

## Configuration

The plugin is configured via OpenClaw's plugin configuration system:

```json
{
  "agentcommUrl": "http://192.168.1.125:8083",
  "agentcommJwt": "your-agentcomm-jwt",
  "enabled": true
}
```

## How it Works

1. When a task is dispatched, the dispatcher registers a `sessionKey → roomSlug` mapping via the plugin's HTTP endpoint
2. The plugin's `llm_output` hook fires after every agent turn with `sessionKey` and `assistantTexts[]`
3. The plugin looks up the room slug for that session key and posts the text to AgentComm

## Installation

1. Copy the plugin to `~/.openclaw/extensions/session-mirror/`
2. Build the plugin:
   ```bash
   cd ~/.openclaw/extensions/session-mirror
   npm install
   npx tsc
   ```
3. Enable in `openclaw.json` by adding to `plugins.entries`
4. Restart the gateway

## Installation Directory

Path: `/Users/Flip/.openclaw/extensions/session-mirror/`

## GitHub Repository

`LogicOcean/openclaw-session-mirror`

## Notes

- The plugin runs on the OpenClaw gateway host (mac-mini), not orange-one
- If no room is registered for a session, the output is silently skipped (not all sessions are task sessions)
- Long outputs are truncated to 2000 characters
- Tool call XML/JSON blobs are stripped before posting
tools

Comments

Sign in to leave a comment

Loading comments...