@mulmobridge/line 1.1.1 → 1.2.0

package/README.md

@@ -91,6 +91,7 @@ Recommended: at least 32 characters of random data (the server logs a warning at
 
 - LINE reply tokens expire in **1 minute**. Since Claude responses can take longer, the bridge uses **push messages** instead of reply messages. This requires your bot to be a verified/certified account for push to work with all users, OR the user must have added the bot as a friend first.
 - LINE limits messages to 5 per push call and ~5000 chars per message. Long replies are automatically chunked.
+- **Loading animation** — while MulmoClaude works on a reply, the bot shows LINE's loading animation (`/v2/bot/chat/loading/start`), refreshed until the reply is pushed. LINE shows it only in one-on-one chats while the user has the chat open, so the bridge does not request it in groups or rooms. No extra setting or permission is needed.
 - **Inbound media** — text and image messages are forwarded to the agent. Image bytes are downloaded via the LINE Data API (`/v2/bot/message/<id>/content`) using the same channel access token; the actual format (JPEG / PNG / HEIC depending on sender) is preserved via the response Content-Type. The photo-EXIF auto-capture flow ([#1222](https://github.com/receptron/mulmoclaude/issues/1222)) writes a sidecar at `data/locations/...` when GPS data is present. Video / audio / file / sticker messages are not forwarded yet.
 
 ## Detailed Setup Guide

package/dist/index.js

@@ -14,9 +14,10 @@
 //                               With none published the client waits (#3078)
 //   MULMOCLAUDE_AUTH_TOKEN    — bearer token
 import "dotenv/config";
-import { createBridgeClient, chunkText, formatAckReply, installProcessGuards } from "@mulmobridge/client";
+import { createBridgeClient, chunkText, formatAckReply, installProcessGuards, replyAfterProcessingIndicator } from "@mulmobridge/client";
 import { createWebhookApp, createWebhookRateLimit, verifyHmacSignature, listenWebhook } from "@mulmobridge/webhook-runtime";
 import { extractIncomingLineMessage, parseLineWebhookBody } from "./parse.js";
+import { LINE_LOADING_REFRESH_MS, loadingSenderFor, startLineLoading } from "./loading.js";
 const TRANSPORT_ID = "line";
 installProcessGuards({ name: TRANSPORT_ID });
 function readRequiredEnv() {
@@ -112,38 +113,36 @@ app.post("/webhook", webhookRateLimit, async (req, res) => {
         const incoming = extractIncomingLineMessage(event);
         if (!incoming)
             continue;
+        const sendLoading = loadingSenderFor(event.source, () => startLineLoading(fetch, channelAccessToken, incoming.userId));
         try {
-            if (incoming.kind === "text") {
-                console.log(`[line] message user=${incoming.userId} len=${incoming.text.length}`);
-                const ack = await client.send(incoming.userId, incoming.text);
-                await pushMessage(incoming.userId, formatAckReply(ack));
-                continue;
-            }
-            // kind === "image"
-            console.log(`[line] image user=${incoming.userId} messageId=${incoming.imageMessageId}`);
-            const image = await downloadLineImage(incoming.imageMessageId);
-            if (!image) {
-                await pushMessage(incoming.userId, "Sorry, I couldn't fetch that image.");
-                continue;
-            }
-            // chat-service's `parseMessagePayload` rejects empty `text`
-            // (`text is required`) so attachment-only messages need a
-            // placeholder body. Mirror the Telegram convention (see
-            // `packages/bridges/telegram/src/router.ts`) — an instructive
-            // prompt rather than a caption, so the agent treats the
-            // attachment as the subject and produces a useful response.
-            // The post-save EXIF hook (#1222 PR-A) writes a sidecar if
-            // GPS data is present. (Codex review on PR #1255 / #1263.)
-            const attachments = [{ mimeType: image.mimeType, data: image.bytes.toString("base64") }];
-            const placeholderText = "Describe / analyze this file.";
-            const ack = await client.send(incoming.userId, placeholderText, attachments);
-            await pushMessage(incoming.userId, formatAckReply(ack));
+            await replyAfterProcessingIndicator(sendLoading, { produce: () => produceReply(incoming), post: (replyText) => pushMessage(incoming.userId, replyText) }, { refreshMs: LINE_LOADING_REFRESH_MS, label: TRANSPORT_ID, log: console });
         }
         catch (err) {
             console.error(`[line] message handling failed: ${err}`);
         }
     }
 });
+async function produceReply(incoming) {
+    if (incoming.kind === "text") {
+        console.log(`[line] message user=${incoming.userId} len=${incoming.text.length}`);
+        return formatAckReply(await client.send(incoming.userId, incoming.text));
+    }
+    console.log(`[line] image user=${incoming.userId} messageId=${incoming.imageMessageId}`);
+    const image = await downloadLineImage(incoming.imageMessageId);
+    if (!image)
+        return "Sorry, I couldn't fetch that image.";
+    // chat-service's `parseMessagePayload` rejects empty `text`
+    // (`text is required`) so attachment-only messages need a
+    // placeholder body. Mirror the Telegram convention (see
+    // `packages/bridges/telegram/src/router.ts`) — an instructive
+    // prompt rather than a caption, so the agent treats the
+    // attachment as the subject and produces a useful response.
+    // The post-save EXIF hook (#1222 PR-A) writes a sidecar if
+    // GPS data is present. (Codex review on PR #1255 / #1263.)
+    const attachments = [{ mimeType: image.mimeType, data: image.bytes.toString("base64") }];
+    const placeholderText = "Describe / analyze this file.";
+    return formatAckReply(await client.send(incoming.userId, placeholderText, attachments));
+}
 listenWebhook(app, { envVar: "LINE_BRIDGE_PORT", fallback: 3002 }, (port) => {
     console.log("MulmoClaude LINE bridge");
     console.log(`Webhook listening on http://localhost:${port}/webhook`);

package/dist/loading.d.ts

@@ -0,0 +1,12 @@
+export declare const LINE_LOADING_URL = "https://api.line.me/v2/bot/chat/loading/start";
+export declare const LINE_LOADING_SECONDS = 10;
+export declare const LINE_LOADING_REFRESH_MS = 8000;
+export type FetchFn = (url: string, init: RequestInit) => Promise<Response>;
+export declare function startLineLoading(fetchFn: FetchFn, channelAccessToken: string, chatId: string): Promise<void>;
+export declare function isOneOnOneSource(source: {
+    type?: string;
+} | undefined): boolean;
+/** LINE refuses the loading request outside a one-on-one chat, so there the bridge sends nothing. */
+export declare function loadingSenderFor(source: {
+    type?: string;
+} | undefined, startLoading: () => Promise<void>): () => Promise<void>;

package/dist/loading.js

@@ -0,0 +1,30 @@
+// LINE's loading animation (POST /v2/bot/chat/loading/start). One-to-one chats
+// only; it disappears after `loadingSeconds` or when the bot's next message arrives.
+export const LINE_LOADING_URL = "https://api.line.me/v2/bot/chat/loading/start";
+// Kept short: a request that crosses the reply re-shows the animation for this long.
+export const LINE_LOADING_SECONDS = 10;
+export const LINE_LOADING_REFRESH_MS = 8_000;
+const LOADING_REQUEST_TIMEOUT_MS = 10_000;
+export async function startLineLoading(fetchFn, channelAccessToken, chatId) {
+    const res = await fetchFn(LINE_LOADING_URL, {
+        method: "POST",
+        headers: {
+            "Content-Type": "application/json",
+            Authorization: `Bearer ${channelAccessToken}`,
+        },
+        body: JSON.stringify({ chatId, loadingSeconds: LINE_LOADING_SECONDS }),
+        signal: AbortSignal.timeout(LOADING_REQUEST_TIMEOUT_MS),
+    });
+    if (!res.ok) {
+        const body = await res.text().catch(() => "");
+        throw new Error(`loading/start ${res.status} ${body.slice(0, 200)}`);
+    }
+}
+const skipLoading = async () => { };
+export function isOneOnOneSource(source) {
+    return source?.type === "user";
+}
+/** LINE refuses the loading request outside a one-on-one chat, so there the bridge sends nothing. */
+export function loadingSenderFor(source, startLoading) {
+    return isOneOnOneSource(source) ? startLoading : skipLoading;
+}

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@mulmobridge/line",
-  "version": "1.1.1",
+  "version": "1.2.0",
   "description": "LINE bridge for MulmoBridge — connect a LINE bot to MulmoClaude",
   "type": "module",
   "main": "./dist/index.js",
@@ -15,24 +15,24 @@
   "scripts": {
     "build": "tsc",
     "prepack": "yarn build",
-    "typecheck": "tsc --noEmit",
+    "typecheck": "tsc -p tsconfig.typecheck.json",
     "test": "tsx --test test/test_*.ts",
     "lint": "eslint src test"
   },
   "license": "MIT",
   "author": "Receptron Team",
   "dependencies": {
-    "@mulmobridge/client": "^1.3.0",
-    "@mulmobridge/protocol": "^1.0.1",
+    "@mulmobridge/client": "^1.5.0",
+    "@mulmobridge/protocol": "^1.1.0",
     "@mulmobridge/webhook-runtime": "^1.2.0",
-    "dotenv": "^17.0.0",
-    "express": "^5.1.0",
-    "express-rate-limit": "^8.7.0"
+    "dotenv": "^18.0.8",
+    "express": "^5.3.0",
+    "express-rate-limit": "^8.7.1"
   },
   "devDependencies": {
     "@types/express": "^5.0.0",
-    "@types/node": "^26.5.1",
-    "tsx": "^4.23.13",
+    "@types/node": "^26.6.5",
+    "tsx": "^4.23.15",
     "typescript": "^6.0.3"
   },
   "homepage": "https://github.com/receptron/mulmoclaude/tree/main/packages/bridges/line#readme",