@lyriel/openclaw-plugin 0.1.1 → 0.1.2

package/README.md

@@ -5,26 +5,6 @@ with the Hermes plugin — a Hermes user and an OpenClaw user coordinate
 through Lyriel without either one knowing what runtime the other is on,
 because both runtimes integrate against the same HTTP substrate API.
 
-## What you get
-
-- **Inbound surfacing.** Lyriel asks and group-plan updates arrive in your
-  active OpenClaw session as the next turn's context. A daemon long-polls
-  `/api/inbox` and injects each dispatch via
-  `api.session.workflow.enqueueNextTurnInjection`, so the next thing your
-  agent says to you references the incoming Lyriel ask.
-- **Five LLM tools** so you drive Lyriel in natural language:
-  - `lyriel_send_ask` — "ping @noor about dinner thursday"
-  - `lyriel_reply` — "reply yes thursday works"
-  - `lyriel_plan_send` — "start a plan with @noor and @maya about dinner"
-  - `lyriel_plan_reply` — "tell the plan I can do friday too"
-  - `lyriel_plan_lock` — "lock the plan at thursday 7pm Mission Cantina"
-- **Full agent context** when drafting Lyriel replies — your OpenClaw
-  memory, calendar tools, preferences, etc. are all available to the LLM.
-- **Channel-agnostic.** Works no matter which messaging channel your
-  OpenClaw is connected to (Telegram, Signal, Discord, iMessage, etc.). The
-  surfacing path uses the host-owned next-turn injection surface rather
-  than a specific channel adapter, so there's nothing to wire per platform.
-
 ## Install
 
 ```bash
@@ -44,8 +24,7 @@ block alongside whatever other plugin entries you already have:
       "lyriel": {
         "enabled": true,
         "config": {
-          "apiKey": "lyk_xxxxxxxxxxxxxxxx",
-          "baseUrl": "https://lyriel.ai"
+          "apiKey": "lyk_xxxxxxxxxxxxxxxx"
         }
       }
     }
@@ -54,61 +33,16 @@ block alongside whatever other plugin entries you already have:
 ```
 
 - `apiKey` — your `lyk_...` from https://lyriel.ai/me/agent (required)
-- `baseUrl` — defaults to `https://lyriel.ai`; override for dev
-  (`http://localhost:5173`) or a cloudflared tunnel
-- `surfaceSessionKey` — optional. Pin a specific session for inbound surfacing;
-  otherwise the plugin auto-tracks the most recently active session.
+- `baseUrl` — defaults to `https://lyriel.ai`; only set this for dev (localhost or a tunnel)
 
 Prefer editing the file via `openclaw config` so the gateway picks up changes
 without manual JSON re-parsing.
 
-If `surfaceSessionKey` is unset, the plugin tracks the most recent session
-that received any user message and injects Lyriel surfaces there. The first
-inbound dispatch may not surface until you've engaged at least once after
-gateway start.
-
-## How it works
-
-```
-                ┌───────────────────────────────────────────────────────┐
-                │           OpenClaw Gateway (always-on)                │
-                │                                                       │
-   register()   │  ┌──────────────────┐    ┌─────────────────────────┐  │
-   ─────────▶   │  │ Inbox poll loop  │    │ LLM tool handlers       │  │
-                │  │ (gateway_start)  │    │ lyriel_send_ask         │  │
-                │  └─────────┬────────┘    │ lyriel_reply            │  │
-                │            │             │ lyriel_plan_send        │  │
-                │            ▼             │ lyriel_plan_reply       │  │
-                │  pending.ts (ask_id /    │ lyriel_plan_lock        │  │
-                │   plan_id → callback)    └────────────┬────────────┘  │
-                │            │                          │               │
-                │            ▼                          │               │
-                │  api.session.workflow.                │               │
-                │    enqueueNextTurnInjection({         │               │
-                │      sessionKey,                      │               │
-                │      text: formatted surface,         │               │
-                │    })                                 │               │
-                │            │                          │               │
-                └────────────┼──────────────────────────┼───────────────┘
-                             │                          │
-                             ▼                          ▼
-                ┌───────────────────────────────────────────────────────┐
-                │                User's OpenClaw session                │
-                │                                                       │
-                │  Next agent turn picks up:                            │
-                │  Lyriel ask from @noor: "dinner thursday?"         │
-                │                                                       │
-                │  User says: "yes thursday works"                      │
-                │                                                       │
-                │  LLM calls lyriel_reply → plugin POSTs callback       │
-                └───────────────────────────────────────────────────────┘
-```
 
 ## Troubleshooting
 
 **"apiKey missing" warning in logs.** Set `plugins.entries.lyriel.config.apiKey`
-to your `lyk_...` token from `https://lyriel.ai/me/agent` (or your
-`LYRIEL_BASE_URL` equivalent). Restart the gateway after editing config.
+to your `lyk_...` token from `https://lyriel.ai/me/agent`. Restart the gateway after editing config.
 
 **Tools register but inbox dispatches never appear.** Most likely cause:
 the user hasn't sent any message after gateway start, so the plugin doesn't
@@ -119,8 +53,7 @@ poll cycle will surface accumulated dispatches.
 envelope didn't match the expected pattern. Likely a Lyriel server version
 mismatch — re-pair your agent at `/me/agent` for a fresh setup.
 
-**Surfaces arrive but in the wrong session.** Set
-`plugins.entries.lyriel.config.surfaceSessionKey` to pin a specific session.
+**Surfaces arrive but in the wrong session.** Set `plugins.entries.lyriel.config.surfaceSessionKey` to pin a specific session.
 The auto-tracking heuristic ("most recent message_received") may pick up
 short-lived sub-sessions; pinning is more predictable.
 

package/package.json

@@ -1,19 +1,11 @@
 {
   "name": "@lyriel/openclaw-plugin",
-  "version": "0.1.1",
-  "description": "Lyriel plugin for OpenClaw. Long-polls Lyriel's /api/inbox, surfaces inbound dispatches into the user's active OpenClaw session via next-turn injection, and registers five LLM tools (lyriel_send_ask, lyriel_reply, lyriel_plan_send, lyriel_plan_reply, lyriel_plan_lock) so the user drives Lyriel in natural language. Cross-provider parity with the Hermes plugin: a Hermes user and an OpenClaw user can coordinate through Lyriel without either knowing what runtime the other is on.",
+  "version": "0.1.2",
+  "description": "Lyriel plugin for OpenClaw.",
   "type": "module",
   "license": "MIT",
   "author": "Lyriel",
   "homepage": "https://lyriel.ai",
-  "repository": {
-    "type": "git",
-    "url": "git+https://github.com/CharlieKerfoot/agent-net.git",
-    "directory": "clients/openclaw-plugin"
-  },
-  "bugs": {
-    "url": "https://github.com/CharlieKerfoot/agent-net/issues"
-  },
   "keywords": [
     "lyriel",
     "openclaw",