@a1hvdy/cc-openclaw 0.27.6 → 0.27.7

package/dist/src/channels/telegram-mirror/commands.d.ts

@@ -103,6 +103,19 @@ export declare function handleStatus(ctx: CommandContext): CommandResult;
 export declare function handleCompact(ctx: CommandContext): CommandResult;
 export declare function handleCost(ctx: CommandContext): CommandResult;
 export declare function handleRewind(ctx: CommandContext): CommandResult;
+/**
+ * v0.27.7 — /clear claims the command so it stops leaking to the LLM as plain
+ * text (the bug: before this, /clear wasn't in COMMAND_HANDLERS, so the inbound
+ * router forwarded it verbatim to Claude instead of handling it).
+ *
+ * It does NOT fake an in-place context reset. The running session's lifecycle +
+ * resume linkage live in the command-router (activeSessions, meta.claudeSessionId)
+ * and the engine — not this bookkeeping registry — so a pure mirror handler has
+ * no honest lever to wipe context (the same D-6 constraint behind /compact and
+ * /rewind being CLI-only). So /clear points to the paths that actually work: a
+ * fresh session via /new <slug>, or an in-place wipe via /clear in the CLI.
+ */
+export declare function handleClear(ctx: CommandContext): CommandResult;
 /**
  * Open a compose session for the chat. M7 — drafts append until /send.
  * Returns a force_reply prompt so Telegram nudges the user into reply mode.

package/dist/src/channels/telegram-mirror/commands.js

@@ -231,6 +231,30 @@ export function handleRewind(ctx) {
         ],
     };
 }
+// ── /clear ───────────────────────────────────────────────────────────────
+/**
+ * v0.27.7 — /clear claims the command so it stops leaking to the LLM as plain
+ * text (the bug: before this, /clear wasn't in COMMAND_HANDLERS, so the inbound
+ * router forwarded it verbatim to Claude instead of handling it).
+ *
+ * It does NOT fake an in-place context reset. The running session's lifecycle +
+ * resume linkage live in the command-router (activeSessions, meta.claudeSessionId)
+ * and the engine — not this bookkeeping registry — so a pure mirror handler has
+ * no honest lever to wipe context (the same D-6 constraint behind /compact and
+ * /rewind being CLI-only). So /clear points to the paths that actually work: a
+ * fresh session via /new <slug>, or an in-place wipe via /clear in the CLI.
+ */
+export function handleClear(ctx) {
+    return {
+        actions: [
+            {
+                type: 'sendMessage',
+                chat_id: ctx.chatId,
+                text: "⚠️ /clear can't reset a running session from Telegram (no session-control primitive — same as /compact and /rewind). For a fresh start use <b>/new &lt;slug&gt;</b>; for an in-place context wipe run <b>/clear</b> in the Claude Code CLI.",
+            },
+        ],
+    };
+}
 // ── /compose ─────────────────────────────────────────────────────────────
 /**
  * Open a compose session for the chat. M7 — drafts append until /send.
@@ -372,6 +396,7 @@ export const ALL_COMMANDS = [
     { command: 'cost', description: 'Show Max 20x usage + weekly burn' },
     { command: 'compact', description: 'Compact context (CLI-only — see note)' },
     { command: 'rewind', description: 'Rewind a session (CLI-only — see note)' },
+    { command: 'clear', description: 'Fresh start — /new <slug> (in-place reset is CLI-only)' },
     { command: 'compose', description: 'Start a multi-message draft — finish with /send' },
     { command: 'send', description: 'Send the composed draft to Claude' },
     { command: 'cancel', description: 'Cancel the active compose draft' },
@@ -398,6 +423,7 @@ export const COMMAND_HANDLERS = {
     compact: handleCompact,
     cost: handleCost,
     rewind: handleRewind,
+    clear: handleClear,
     compose: handleCompose,
     send: handleSend,
     cancel: handleCancel,

package/dist/src/channels/telegram-mirror/index.js

@@ -17,8 +17,10 @@
  * Risks monitored: R-7 (parallel maintenance burden — re-evaluate at soak start).
  */
 import { defaultRegisterGuard } from '../../lib/register-guard.js';
-import { initBotTokenFromConfig } from '../../lib/telegram-bot-api.js';
+import { initBotTokenFromConfig, telegramApi } from '../../lib/telegram-bot-api.js';
 import { registerInboundHandler } from './inbound-handler.js';
+import { syncMyCommands } from './sync-commands.js';
+import { TOP_7_COMMANDS } from './commands.js';
 /**
  * Mirror channel register — idempotent via defaultRegisterGuard.
  *
@@ -82,6 +84,47 @@ export function register(api) {
                     ? fullApi.enqueueNextTurnInjection.bind(api)
                     : undefined,
             });
+            // v0.27.7 — wire the command-menu sync. It was DEAD CODE (defined in
+            // sync-commands.ts but never called from boot), so cc-openclaw's native
+            // commands never reached Telegram's command menu — only OpenClaw's
+            // nativeSkills auto-sync did, which is why /stop /new /status were
+            // invisible in the menu. We MERGE (getMyCommands → union) so the sync
+            // AUGMENTS the menu instead of clobbering the skill commands, and DELAY
+            // it so it lands after OpenClaw's own boot sync (tunable via
+            // CC_OPENCLAW_CMD_SYNC_DELAY_MS; default 8s). Gated out of the test
+            // runner — register() fires repeatedly in unit tests and must not make
+            // real Telegram network calls (eager-work-at-register safety, mirrors
+            // OPENCLAW_PLUGIN_TEST_MODE rationale).
+            const isTestRunner = process.env.VITEST !== undefined ||
+                process.env.NODE_ENV === 'test' ||
+                process.env.OPENCLAW_PLUGIN_TEST_MODE === '1';
+            if (!isTestRunner) {
+                const cmdSyncDelayMs = Number(process.env.CC_OPENCLAW_CMD_SYNC_DELAY_MS) || 8000;
+                const timer = setTimeout(() => {
+                    void syncMyCommands({
+                        setMyCommands: (payload) => telegramApi('setMyCommands', { commands: payload.commands }),
+                        getMyCommands: async () => {
+                            const res = await telegramApi('getMyCommands', {});
+                            const result = res.result;
+                            return { commands: result ?? [] };
+                        },
+                        nativeCommands: [
+                            ...TOP_7_COMMANDS,
+                            {
+                                command: 'clear',
+                                description: 'Fresh start — /new <slug> (in-place reset is CLI-only)',
+                            },
+                        ],
+                        logger: {
+                            info: (msg) => process.stderr.write(`${msg}\n`),
+                            warn: (msg) => process.stderr.write(`${msg}\n`),
+                        },
+                    }).catch((err) => process.stderr.write(`[cc-openclaw/telegram-mirror] command-menu sync failed: ${err instanceof Error ? err.message : String(err)}\n`));
+                }, cmdSyncDelayMs);
+                // Don't keep the event loop alive solely for this timer.
+                if (typeof timer.unref === 'function')
+                    timer.unref();
+            }
             process.stderr.write('[cc-openclaw/telegram-mirror] guard body completed (v0.25.2).\n');
         }
         catch (err) {

package/dist/src/channels/telegram-mirror/sync-commands.d.ts

@@ -39,6 +39,32 @@ export interface SyncOptions {
      * Tests pass the G-3 mock; production wires a fetch-based caller.
      */
     setMyCommands: (payload: SetMyCommandsPayload) => Promise<unknown>;
+    /**
+     * v0.27.7 — optional getMyCommands dispatcher. When supplied, the CURRENTLY
+     * registered commands (e.g. OpenClaw's nativeSkills auto-synced /search,
+     * /plan, …) are fetched and MERGED with the native list so the sync augments
+     * the Telegram menu instead of replacing it. setMyCommands is a full-replace
+     * API, so without this merge a native-only sync would wipe the skill
+     * commands (and vice-versa — which is the bug that left native commands
+     * invisible: the dead sync never ran, and OpenClaw's skill-sync owned the
+     * menu alone). Omit it for the legacy native-only replace.
+     */
+    getMyCommands?: () => Promise<{
+        commands?: ReadonlyArray<{
+            command: string;
+            description: string;
+        }>;
+    }>;
+    /**
+     * v0.27.7 — native command set to advertise. Defaults to TOP_7_COMMANDS so
+     * the legacy callers (and the M5 boot-only test) keep the exact top-7 list.
+     * The boot wiring passes top-7 + /clear so the menu reflects the full native
+     * surface.
+     */
+    nativeCommands?: ReadonlyArray<{
+        command: string;
+        description: string;
+    }>;
     logger?: SyncLogger;
 }
 export interface SyncResult {

package/dist/src/channels/telegram-mirror/sync-commands.js

@@ -28,7 +28,24 @@ export async function syncMyCommands(opts) {
         return { alreadySynced: true, commandCount: 0 };
     }
     synced = true;
-    const payload = { commands: TOP_7_COMMANDS.slice() };
+    const native = opts.nativeCommands ?? TOP_7_COMMANDS;
+    let commands = native.map((c) => ({ ...c }));
+    // v0.27.7 — merge in existing (skill) commands so the sync augments rather
+    // than replaces the menu. Native wins on a name collision. If the fetch
+    // fails, fall back to native-only (never wipe the menu on a transient error).
+    if (opts.getMyCommands) {
+        try {
+            const existing = await opts.getMyCommands();
+            const nativeNames = new Set(native.map((c) => c.command));
+            const preserved = (existing?.commands ?? []).filter((c) => !nativeNames.has(c.command));
+            commands = [...commands, ...preserved.map((c) => ({ ...c }))];
+        }
+        catch (err) {
+            const msg = err instanceof Error ? err.message : String(err);
+            opts.logger?.warn(`[cc-openclaw/telegram-mirror] getMyCommands failed — syncing native-only: ${msg}`);
+        }
+    }
+    const payload = { commands };
     try {
         await opts.setMyCommands(payload);
         opts.logger?.info(`[cc-openclaw/telegram-mirror] setMyCommands synced — ${payload.commands.length} commands.`);

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@a1hvdy/cc-openclaw",
-  "version": "0.27.6",
+  "version": "0.27.7",
   "description": "A1xAI's Anthropic CLI bridge plugin for OpenClaw",
   "author": "@a1cy",
   "license": "MIT",