@lyriel/openclaw-plugin 0.1.0 → 0.1.1

package/README.md

@@ -7,7 +7,7 @@ because both runtimes integrate against the same HTTP substrate API.
 
 ## What you get
 
-- 🪶 **Inbound surfacing.** Lyriel asks and group-plan updates arrive in your
+- **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
@@ -27,60 +27,11 @@ because both runtimes integrate against the same HTTP substrate API.
 
 ## Install
 
-### Local development (against a globally-installed OpenClaw)
-
-OpenClaw's `--link` install path expects compiled JavaScript output, not raw
-TypeScript (source-checkout fallback only applies inside the openclaw monorepo
-itself). One-time setup from this directory:
-
-```bash
-# 1. Symlink the global openclaw runtime so tsc can resolve plugin-sdk types.
-mkdir -p node_modules
-ln -sfn /opt/homebrew/lib/node_modules/openclaw node_modules/openclaw
-
-# 2. Install local build deps.
-npm install --no-save typebox typescript
-
-# 3. Re-create the openclaw symlink (npm install clobbers it).
-ln -sfn /opt/homebrew/lib/node_modules/openclaw node_modules/openclaw
-
-# 4. Build to dist/.
-npx tsc -p tsconfig.build.json
-
-# 5. Link the plugin into OpenClaw.
-openclaw plugins install --link "$(pwd)"
-
-# 6. Restart so the runtime picks up the new plugin.
-openclaw gateway restart
-```
-
-Re-run `npx tsc -p tsconfig.build.json` after any edit to the `*.ts` files;
-the gateway re-reads `dist/` on the next plugin reload.
-
-### Bundled (in-tree development against the openclaw monorepo)
-
-```bash
-cd /path/to/openclaw
-ln -s /path/to/lyriel-repo/clients/openclaw-plugin extensions/lyriel
-pnpm install
-pnpm test -- extensions/lyriel/
-```
-
-The bundled path discovers TS source directly; no precompile needed.
-
-### Published (from npm)
-
 ```bash
 npm install -g @lyriel/openclaw-plugin
 openclaw plugins install @lyriel/openclaw-plugin
 ```
 
-The `prepare` script in package.json builds `dist/` on install, so the
-plugin is ready as soon as npm finishes. `openclaw plugins install`
-then registers it with the OpenClaw runtime. ClawHub publish
-(`openclaw plugins install clawhub:lyriel/openclaw-plugin`) is a v0.2
-follow-up that wraps the same npm package.
-
 ## Configure
 
 OpenClaw config lives at `~/.openclaw/openclaw.json`. Add a `plugins.entries.lyriel`
@@ -145,7 +96,7 @@ gateway start.
                 │                User's OpenClaw session                │
                 │                                                       │
                 │  Next agent turn picks up:                            │
-                │  🪶 Lyriel ask from @noor: "dinner thursday?"         │
+                │  Lyriel ask from @noor: "dinner thursday?"         │
                 │                                                       │
                 │  User says: "yes thursday works"                      │
                 │                                                       │
@@ -153,36 +104,6 @@ gateway start.
                 └───────────────────────────────────────────────────────┘
 ```
 
-## Comparison with the Hermes plugin
-
-| | Hermes plugin | This plugin |
-|---|---|---|
-| Language | Python | TypeScript |
-| Surface path | Hermes `inject_message` (CLI) + gateway Telegram adapter | OpenClaw `enqueueNextTurnInjection` (channel-agnostic) |
-| Background task | `threading.Thread(daemon=True)` | `gateway_start` lifecycle hook + `setTimeout` loop |
-| Tool registration | `ctx.register_tool` | `api.registerTool` |
-| Pending callback state | in-process `dict` | in-process `Map` |
-| Proactive notification | yes — Telegram push | no — appears on next agent turn |
-
-The "no proactive push" gap is deliberate. OpenClaw users connect via many
-possible channels; surfacing through next-turn injection is one path that
-works for all of them. A truly push-notification path can be added later
-once we know which channel design partners actually live in.
-
-## Cross-provider interop
-
-The whole point of having a plugin per provider: a user can be on Hermes
-and address a friend who's on OpenClaw (or vice versa) and neither side
-needs to know about the other's runtime. The provider adapter on Lyriel's
-server (`web/src/lib/server/agents/{hermes,openclaw}.ts`) dispatches into
-each user's provider via that provider's inbound API. This plugin is the
-client-side half of the OpenClaw integration.
-
-End-to-end: Hermes user → Hermes Lyriel plugin → Lyriel API → Lyriel
-OpenClaw adapter → OpenClaw `/v1/chat/completions` → user's OpenClaw
-agent → OpenClaw Lyriel plugin (this) → callback → Lyriel → Hermes Lyriel
-plugin surfaces the reply.
-
 ## Troubleshooting
 
 **"apiKey missing" warning in logs.** Set `plugins.entries.lyriel.config.apiKey`
@@ -206,37 +127,3 @@ short-lived sub-sessions; pinning is more predictable.
 **Hot reload.** OpenClaw plugin reloads keep durable session extension
 state and re-run cleanup callbacks. The inbox loop stops cleanly on
 `gateway_stop` and restarts on the next `gateway_start`.
-
-## v0 limitations
-
-- **In-process pending map.** If the gateway restarts mid-flight, pending
-  callback tokens are lost. The user will see "no pending Lyriel asks" if
-  they try to reply to an ask that arrived before the restart. Move to
-  `api.runtime.state.openKeyedStore` to survive restarts.
-- **One-pending-per-ask.** If multiple asks pile up, the LLM disambiguates
-  via ask_id (shown in each surface message).
-- **No truly proactive push.** Dispatches surface on the next agent turn
-  in the configured session. Adding per-channel push is a v0.2 task.
-- **Single user per OpenClaw gateway.** One `apiKey` per plugin instance.
-  Multi-user gateways aren't supported yet.
-
-## Publishing
-
-The package is `@lyriel/openclaw-plugin` on npm. Prerequisites: an npm
-account with publish rights on the `@lyriel` scope (claim it once with
-`npm org create lyriel`), authenticated via `npm login`.
-
-```bash
-# 1. Bump the version in package.json (and openclaw.plugin.json if the
-#    OpenClaw-facing version should track).
-# 2. Publish. prepublishOnly runs the TypeScript build into dist/ first;
-#    the files whitelist in package.json scopes the tarball to dist/ +
-#    openclaw.plugin.json.
-npm publish
-```
-
-`publishConfig.access: public` in package.json lets the scoped
-package go up without `--access public` on the command line. After
-publish, the install paste-prompt (`npm install -g
-@lyriel/openclaw-plugin && openclaw plugins install
-@lyriel/openclaw-plugin`) resolves to the new version.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@lyriel/openclaw-plugin",
-  "version": "0.1.0",
+  "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.",
   "type": "module",
   "license": "MIT",
@@ -38,6 +38,7 @@
     "typebox": "1.1.38"
   },
   "devDependencies": {
+    "openclaw": "^2026.5.20",
     "typescript": "^5.5.0"
   },
   "peerDependencies": {