22 Commits

• fix: markdownToHtml multiline bold — [\s\S] instead of dot

  GLM outputs multi-line **bold** blocks in essays. The dot regex .+?
  does not match newlines, so multiline bold rendered as raw **.

  admin · 2026-05-05 16:28:35 +00:00
  316f3115f6
• fix: delete+resend streaming draft instead of edit with HTML parse_mode switch

  Telegram rejects parse_mode changes on existing messages.
  Old: editMessageText with HTML on a plain-text message → silent fail, raw ** shown.
  New: deleteMessage + sendFormatted (fresh HTML) → always renders bold/italic correctly.

  admin · 2026-05-05 16:24:32 +00:00
  5cc00aa4fe
• fix: delete raw-markdown draft and resend formatted on final edit failure

  When streaming produces a long essay that exceeds Telegram's edit limit,
  the final HTML edit silently fails, leaving the user with raw ** markers.
  Now: delete the draft message and send fresh formatted message(s) via
  sendFormatted which handles HTML conversion, splitting, and fallback.

  admin · 2026-05-05 15:25:49 +00:00
  a076ae2d6d
• debug: add send logging to sendStreamingMessage
  admin · 2026-05-05 14:58:10 +00:00
  60ed5375de
• fix: bulletproof command handler + auto-restart + README overhaul

  - sendStreamingMessage: replaced broken simulated streaming with reliable
    HTML send + stripped plain text fallback (was silently failing)
  - Added global unhandledRejection guard (catches async errors that
    sequentialize middleware would swallow)
  - restart.sh: auto-restart loop on crash (3s delay) instead of bare node
  - README: comprehensive update with self-learning memory, curiosity engine,
    memory architecture diagram, updated command table, updated comparison

  admin · 2026-05-05 14:49:49 +00:00
  050dc6ebe3
• fix: beautiful Telegram formatting via HTML (no more raw **)

  - Add markdownToHtml() converter: **bold**, *italic*, code blocks, links, headings, quotes, lists
  - StreamConsumer: intermediate edits stay plain text, FINAL message gets full HTML formatting
  - sendFormatted() now uses HTML parse_mode with fallback to stripped plain text
  - stripMarkdown() for plain-text fallback (no raw syntax chars)
  - All Telegram sends now use HTML instead of legacy Markdown mode

  admin · 2026-05-05 14:22:55 +00:00
  a0549ac641
• feat: real-time SSE streaming via StreamConsumer (adapted from Hermes Agent)

  - StreamConsumer class: queued token buffer → rate-limited editMessageText loop
  - Adaptive flood control backoff (3 strikes → fallback to plain send)
  - Cursor indicator (▉) during typing, stripped on completion
  - chatWithAI now supports onDelta callback for SSE token streaming
  - Uses native fetch() for SSE (Node 18+), falls back to non-streaming on error
  - Message handler wires StreamConsumer into the chat pipeline
  - Graceful fallback: if streaming fails entirely, sends as plain message

  admin · 2026-05-05 14:13:03 +00:00
  ed4a4c35e8
• fix: sentence-level streaming with proper Telegram rate limit throttling
  admin · 2026-05-05 14:04:04 +00:00
  78d4932b63
• debug: log sentMsg raw and Reflect.ownKeys
  admin · 2026-05-05 13:58:26 +00:00
  70815a73d2
• debug: check sentMsg constructor and result property
  admin · 2026-05-05 13:53:25 +00:00
  a4a9e31e79
• debug: check for 'result' wrapper in Telegram API response
  admin · 2026-05-05 13:51:40 +00:00
  fbc6b9a377
• debug: log response structure and try multiple access patterns
  admin · 2026-05-05 13:49:44 +00:00
  98b8d0cca8
• fix: use bracket notation for Telegram API response
  admin · 2026-05-05 13:47:44 +00:00
  f6d470c51c
• fix: handle Telegram API array-like response format
  admin · 2026-05-05 13:46:42 +00:00
  8ac88fc4ad
• fix: use ctx.api.sendMessage instead of ctx.reply for streaming
  admin · 2026-05-05 13:45:45 +00:00
  e839f513de
• debug: add detailed logging for streaming IDs
  admin · 2026-05-05 13:44:47 +00:00
  f8a6edf4c7
• fix: use cached chatId and messageId for editMessageText
  admin · 2026-05-05 13:43:49 +00:00
  429b8a1633
• debug: add streaming logs and faster delays
  admin · 2026-05-05 13:42:55 +00:00
  494596c0a9
• feat: implement real-time message editing streaming (like OpenClaw)
  admin · 2026-05-05 13:41:26 +00:00
  100ac4e5e8
• feat: implement word-by-word streaming typing effect
  admin · 2026-05-05 13:38:31 +00:00
  0d96c4fb7f
• feat: enable streaming responses like OpenClaw

  - Add sendStreamingMessage() to message-sender.js with typing indicators
  - Enable stream: true in chatWithAI() with SSE parsing
  - Replace all ctx.reply() calls with sendStreamingMessage()
  - Real-time text streaming with 50ms delay between chunks

  admin · 2026-05-05 13:18:32 +00:00
  e658842458
• feat: full service exposure with grammy bot + claudegram patterns

  - Rewrote bot/index.js using grammy (@grammyjs/auto-retry + runner)
  - Added deduplication.js (adapted from claudegram)
  - Added request-queue.js (per-chat sequential processing)
  - Added message-sender.js (chunking + Markdown fallback)
  - Wired all JS-shim services: tools, skills, agents, config, RTK
  - Added function calling support to ZAIProvider.chat()
  - Added dynamic command routing (tools, skills, agents, model, stats)
  - Added per-agent delegation commands (/agent_coder, /agent_architect, etc.)
  - Added dedup + queue patterns from claudegram's battle-tested codebase
  - Updated zcode.js to pass agents to initBot()
  - Updated README feature comparison table to reflect real capabilities

  admin · 2026-05-05 12:41:15 +00:00
  cbe816a421