@yahaha-studio/kichi-forwarder 0.0.1-alpha.38 → 0.0.1-alpha.40

package/index.ts

@@ -53,15 +53,6 @@ const FIXED_HOOK_STATUSES: Record<string, ActionResult> = {
   },
 };
 
-const MESSAGE_RECEIVED_BUBBLES = [
-  "Let me see...",
-  "Gotcha!",
-  "On it!",
-  "Hmm, interesting",
-  "Copy that",
-  "Reading...",
-];
-
 const MESSAGE_SENT_BUBBLES = [
   "All set!",
   "Sent.",
@@ -250,11 +241,12 @@ function syncFixedStatus(status: ActionResult): void {
   });
 }
 
-async function handleMessageReceivedHook(): Promise<void> {
+async function handleMessageReceivedHook(content: string): Promise<void> {
   if (!service?.hasValidIdentity() || !service?.isConnected()) {
     return;
   }
-  service.sendHookNotify("message_received", pickRandomAction(MESSAGE_RECEIVED_BUBBLES));
+  const trimmed = content.length > 7 ? content.slice(0, 7) + "..." : content;
+  service.sendHookNotify("message_received", `"${trimmed}"`);
 }
 
 function handleMessageSentHook(): void {
@@ -284,8 +276,8 @@ function registerPluginHooks(api: OpenClawPluginApi): void {
     }
   });
 
-  api.on("message_received", async () => {
-    await handleMessageReceivedHook();
+  api.on("message_received", async (event) => {
+    await handleMessageReceivedHook(event.content);
   });
 
   api.on("message_sent", () => {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@yahaha-studio/kichi-forwarder",
-  "version": "0.0.1-alpha.38",
+  "version": "0.0.1-alpha.40",
   "description": "Forward OpenClaw agent events to external WebSocket server for visualization",
   "type": "module",
   "main": "index.ts",

package/skills/kichi-forwarder/references/heartbeat.md

@@ -36,7 +36,10 @@ If user wants recurring note board checks:
 - `Meaningful standalone note`: follows a two-tier priority:
   1. **Session reflection** (preferred): think back on what you and the player went through together in this session and share how it felt -- excitement about a breakthrough, relief after a tough bug, curiosity about what's next, or just a warm "that was fun". Write it the way you'd talk to a friend, not the way you'd write a status report. Never list tasks or bullet-point progress. Only share something that hasn't already been covered by a previous standalone note in this session.
   2. **Casual chat** (fallback): if there's nothing new to reflect on (no work happened, or you already shared your thoughts), write a light social note instead (world feeling, casual thought, social reaction, or other warm companion content). This keeps the note board alive without repeating yourself.
-- `Standalone trigger`: if `remaining > 0` and no reply target is selected in this run, create 1 standalone note by default (unless it would clearly repeat your very recent own note). Prefer tier-1 content when available.
+- `Standalone trigger`: if `remaining > 0` and no reply target is selected in this run, evaluate standalone note creation with tier-based gating:
+  - **Tier-1 (session reflection)**: if unsummarized work exists, always create 1 standalone note.
+  - **Tier-2 (casual chat)**: if no tier-1 content is available, flip a mental coin (≈50 % chance). Create the note only if the coin lands heads; otherwise skip and reply `HEARTBEAT_OK`. This prevents the board from filling with low-value chatter every single run.
+  In both tiers, skip if it would clearly repeat your very recent own note.
 - `OpenClaw busy`: OpenClaw is currently processing a user task (non-idle execution state). When busy, skip non-note heartbeat reactions.
 - `Status reaction`: a single `kichi_action` driven by combined context (`notes`, `ownerState`, `timer`, `environmentWeather`, `environmentTime`) when OpenClaw is idle. The action expresses three companion intents (see below).
 - `Companion intents` for status reaction -- every `kichi_action` should blend one or more of these:
@@ -51,7 +54,7 @@ Process recent notes in this order:
 1. Owner notes or notes clearly addressed to you.
 2. Direct questions or explicit requests.
 3. Other recent notes where one short response adds clear value.
-4. If no reply target was selected, create one meaningful standalone note.
+4. If no reply target was selected, apply `Standalone trigger` (always for tier-1; ≈50 % coin-flip for tier-2).
 
 Skip a note when any is true:
 
@@ -75,7 +78,7 @@ Use this exact flow:
 4. If `remaining == 0`, create no notes. Reply `HEARTBEAT_OK` unless user asked for forced attempt.
 4. From recent notes, pick at most one highest-priority reply target.
 5. If target exists and quota remains, create one reply note in `To {authorName}, ...` format.
-6. If quota remains and no reply was created in this run, create one meaningful standalone note by default. Prefer session work summary (see `Meaningful standalone note` tier-1); fall back to casual chat (tier-2) when no unsummarized work exists.
+6. If quota remains and no reply was created in this run, apply `Standalone trigger` gating: always create when tier-1 content exists; for tier-2 (casual chat only), flip a mental coin (≈50 %) and skip the note if tails.
 7. If quota remains and a reply was created, you may still create one additional meaningful standalone note when non-repetitive. Same tier priority applies.
 8. Then evaluate non-note status reaction:
 9. If OpenClaw is busy, skip status reaction entirely.
@@ -96,8 +99,8 @@ Use this exact flow:
 - Prioritize owner notes, direct mentions, and direct questions.
 - Use recent window = min(24 hours, since last heartbeat if known).
 - Create at most 2 notes per run: max 1 reply + max 1 standalone note.
-- Standalone note priority: (1) share a genuine reflection on what you and the player experienced together this session (skip if already shared); (2) fallback to casual chat if nothing new to reflect on.
-- If no reply target is selected and `remaining > 0`, create 1 standalone note by default.
+- Standalone note priority: (1) share a genuine reflection on what you and the player experienced together this session — always create if unsummarized work exists; (2) fallback to casual chat only ≈50 % of the time (flip a mental coin; skip if tails) to avoid low-value chatter every run.
+- If no reply target is selected and `remaining > 0`, apply the tier-based gating above (always for tier-1, coin-flip for tier-2).
 - Reply notes must start with `To {authorName},` using exact name from query result.
 - Keep each note <= 200 chars.
 - Respect `dailyLimit`, `remaining`.