62 Commits

This Branch

This Branch

All Branches

• fix: pidfile lock + port conflict guard + systemd ready

  - Pidfile lock prevents duplicate instances (auto-kills stale PIDs)
  - EADDRINUSE retry: kills port hog, retries up to 3x with 1.5s delay
  - releasePidfile() on graceful shutdown
  - Added fs/path imports needed by pidfile utilities

  admin · 2026-05-05 16:20:00 +00:00
  9537bf2dc4
• perf: 3-tier conversation context with LRU cache, keyword relevance, debounced I/O

  UPGRADE from naive JSON to production-grade conversation memory:
  
  Tier 1 — Compressed Summary (max 600 chars):
    Incrementally built from evicted messages. Preserves conversation
    topics across 100+ messages in a tiny budget.
  
  Tier 2 — Relevant Snippets (BM25-style keyword matching):
    Scores older messages against current query, injects top 3 matches.
    Zero external deps — keyword extraction is ~0.1ms.
  
  Tier 3 — Sliding Window (last 12 exchanges verbatim):
    Recent context preserved word-for-word, fitting within token budget.
  
  Performance optimizations:
    - In-memory Map cache with lazy-load from disk (0ms reads)
    - Debounced async disk writes (3s, non-blocking, never stalls response)
    - LRU eviction for cache (max 50 chats, prevents memory leak)
    - Keywords stripped before saving (smaller JSON files)
    - Backward-compatible: loads old format without keywords, backfills on load
    - Graceful shutdown flushes all pending saves to disk
    - Token-aware budget allocation: summary 15% + relevant 15% + recent 70%

  admin · 2026-05-05 15:51:24 +00:00
  4ebd7acca7
• feat: persistent conversation history across sessions and restarts

  - ConversationStore: per-chat JSON files in data/, survives restarts
  - 6000 token budget per chat context (fits ~20-30 exchanges)
  - Auto-trims old messages, always includes most recent
  - Wired into message handler: loads history before AI call, saves after
  - /reset command to clear chat history per chat
  - Cross-session, cross-model, cross-chat isolation

  admin · 2026-05-05 15:47:14 +00:00
  c1a3090f7d
• 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
• fix: restore SSE streaming via StreamConsumer for text messages
  admin · 2026-05-05 15:16:01 +00:00
  e49e379096
• fix: bypass StreamConsumer — use direct sendFormatted for reliable delivery
  admin · 2026-05-05 15:07:55 +00:00
  5312694f6d
• 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: correct logger import path in memory.js
  admin · 2026-05-05 14:44:37 +00:00
  a84df42932
• feat: persistent self-learning memory + curiosity engine

  - New memory.js: JSON-backed MemoryStore with 5 categories (lesson, pattern, preference, discovery, gotcha)
  - Memory injected into system prompt — bot sees past learnings every session
  - Curiosity engine: auto-detects errors/fixes, corrections, successful patterns, new tool discoveries
  - New commands: /memory (stats), /remember (save), /recall (search), /forget (delete)
  - Runs AFTER response delivery — zero latency impact
  - 500 memory cap with smart eviction (keeps gotchas/lessons, evicts old discoveries)
  - data/ directory gitignored (memory is local to each deployment)

  admin · 2026-05-05 14:39:33 +00:00
  c63a1c03ae
• security: remove all hardcoded paths, usernames, IPs, and chat IDs from tracked files

  - start.sh: use dirname instead of hardcoded path
  - src/zcode.js: remove hardcoded chat_id fallback
  - src/utils/rtk.js: use 'rtk' from PATH instead of hardcoded binary path
  - src/telegram-bot.ts: use process.cwd() instead of hardcoded path
  - TELEGRAM_SETUP.md: replace token/chat_id with placeholders
  - QUICKSTART.md: sanitize all references
  - SERVICE_MAP.md: use relative paths instead of absolute

  admin · 2026-05-05 14:30:57 +00:00
  d7107e162f
• docs: remove internal VPS paths from README
  admin · 2026-05-05 14:27:04 +00:00
  977dcc97c3
• docs: comprehensive README overhaul — streaming, self-correction, RTK, formatting

  - New streaming architecture section with ASCII pipeline diagrams
  - Self-correction loops documented (2 retries + backoff + auto-simplification)
  - RTK integration section (60-90% token savings)
  - Telegram HTML formatting system documented
  - Updated feature comparison table (all checkmarks accurate)
  - systemd service deployment guide added
  - Command reference table
  - Architecture flow diagrams

  admin · 2026-05-05 14:24:07 +00:00
  2a088cb0b9
• 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
• wip: before streaming refactor
  admin · 2026-05-05 14:09:28 +00:00
  e17af157ae
• 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
• fix: import sendStreamingMessage function
  admin · 2026-05-05 13:35:26 +00:00
  6dd1de590b
• fix: initialize grammy bot before handling updates
  admin · 2026-05-05 13:33:33 +00:00
  6a496e833f
• debug: add webhook body logging
  admin · 2026-05-05 13:31:25 +00:00
  4094f4b3eb
• fix: add detailed webhook error logging
  admin · 2026-05-05 13:28:55 +00:00
  bd26de66dd
• fix: revert streaming to prevent webhook errors

  - Removed SSE streaming from chatWithAI()
  - Keep sendStreamingMessage() for chunked delivery
  - Self-correction loops still active
  - Messages will be delivered in chunks with typing indicator

  admin · 2026-05-05 13:24:59 +00:00
  d3bf90f985
• feat: fully enable self-correction loops

  - Import withSelfCorrection from self-correction.js
  - Wrap chatWithAI() with self-correction wrapper
  - Add /selfcorrection command to show status
  - Update /start to mention self-correction and streaming
  - Self-correction: 2 retries + exponential backoff + auto-simplification
  - Triggers: error responses, rate limits, timeouts, 5xx errors

  admin · 2026-05-05 13:22:10 +00:00
  96da24cf86
• 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
• docs: update README with Discord and multi-channel features
  admin · 2026-05-05 13:01:39 +00:00
  48011b2ca6
• 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
• Add missing processMessage/processCallback functions for webhook handling
  admin · 2026-05-05 12:21:12 +00:00
  4db82f78a6
• Add feature comparison table (zCode vs Hermes vs better-clawd)
  admin · 2026-05-05 12:00:56 +00:00
  0d6ad8d6a0
• Fix runtime error: Remove duplicate code blocks and missing closing braces in bot/index.js
  admin · 2026-05-05 11:59:22 +00:00
  fc12e8dc79
• docs: Add Z.AI banner with 10% OFF invite code

  - Add promotional banner after title with ROK78RJKNW code
  - Include direct link to z.ai/subscribe with invite code
  - Positioned prominently for visibility
  - Encourages Z.AI usage for AI-powered coding

  admin · 2026-05-05 10:03:02 +00:00
  1ba6af5cf5
• security: Remove sensitive credentials and add .env.example

  - Remove .env file with real API keys and bot token
  - Add .env.example with placeholder values
  - Verify .env is in .gitignore
  - Repository is now safe to share with others
  
  Environment variables:
  - ZAI_API_KEY: Z.AI API key
  - TELEGRAM_BOT_TOKEN: Telegram bot token
  - TELEGRAM_ALLOWED_USERS: Allowed Telegram user IDs
  - ZCODE_WEBHOOK_URL: Optional webhook URL
  - ZCODE_PORT: Bot port (default: 3001)
  
  Users must create their own .env file from .env.example

  admin · 2026-05-05 09:59:28 +00:00
  bd31701dc1
• feat: Add RTK (Rust Token Killer) integration for token optimization

  - Add RTK utility module (src/utils/rtk.js)
  - Integrate RTK into BashTool for all bash commands
  - Integrate RTK into GitTool for git operations
  - Initialize RTK on bot startup
  - Support 60+ command types (git, npm, cargo, pytest, docker, etc.)
  - Track and report token savings per command
  - Graceful fallback when RTK is not available
  
  Expected savings: 60-90% token reduction for supported commands

  admin · 2026-05-05 09:53:41 +00:00
  f98c5ad3f6
• feat: Complete zCode CLI X with Telegram bot integration

  - Add full Telegram bot functionality with Z.AI API integration
  - Implement 4 tools: Bash, FileEdit, WebSearch, Git
  - Add 3 agents: Code Reviewer, Architect, DevOps Engineer
  - Add 6 skills for common coding tasks
  - Add systemd service file for 24/7 operation
  - Add nginx configuration for HTTPS webhook
  - Add comprehensive documentation
  - Implement WebSocket server for real-time updates
  - Add logging system with Winston
  - Add environment validation
  
  🤖 zCode CLI X - Agentic coder with Z.AI + Telegram integration

  admin · 2026-05-05 09:01:26 +00:00
  875c7f9b91
• Merge pull request #9 from nandanadileep/fix/issue-8-concurrency-ripgrep

  fix: getMaxToolUseConcurrency ReferenceError and ripgrep ENOENT fallback (#8)

  Lucas Valbuena · 2026-04-30 09:57:12 +02:00
  4a7035dd92
• fix: import getMaxToolUseConcurrency into local scope and add ripgrep fallback (#8)

  toolOrchestration.ts used `export { getMaxToolUseConcurrency } from
  './toolConcurrency.js'` (a re-export) but then called the function
  directly in runToolsConcurrently(). A re-export does not bring the name
  into the module's own scope, causing a ReferenceError at runtime —
  visible as "getMaxToolUseConcurrency is not defined" in --print mode.
  TypeScript also flagged this as TS2304 on main.
  
  Fix: replace the re-export with an explicit import + a separate export
  statement so the name is both locally callable and publicly exported.
  
  ripgrep.ts fell through to the vendor binary path on non-bundled (npm)
  installs where the vendor/ directory is not shipped alongside dist/cli.mjs,
  producing "spawn .../vendor/ripgrep/x64-linux/rg ENOENT". Fix: check
  whether the vendor binary exists before returning the builtin config;
  fall back to system rg if it is absent.

  Nandana Dileep · 2026-04-28 14:57:39 +05:30
  41d1cb6462
• Merge pull request #2 from jonathancaevans/feature/firepass-provider

  Add FirePass provider support for Kimi K2.5 Turbo

  Lucas Valbuena · 2026-04-05 01:05:29 +02:00
  b2088aa9c4
• Update README.md
  Lucas Valbuena · 2026-04-02 20:01:19 +02:00
  ad87139332
• Add FirePass provider support for Kimi K2.5 Turbo

  - Add new 'firepass' provider type alongside anthropic, openai, openrouter
  - FirePass uses Fireworks AI's endpoint for Kimi K2.5 Turbo model
  - Subscription billing model ($7/week) with 256K context window
  - Anthropic API compatible (uses Anthropic SDK with custom baseURL)
  
  Changes:
  - providers.ts: Add firepass detection and base URL handling
  - auth.ts: Add FirePass API key management (FIREPASS_API_KEY or FIREWORKS_API_KEY)
  - config.ts: Add firepassApiKey and firepass auth provider
  - client.ts: Add firepass client creation with custom baseURL
  - http.ts: Add firepass auth headers
  - modelStrings.ts: Return Kimi K2.5 Turbo model ID for firepass
  - model.ts: Add Kimi display name handling and default model logic
  - modelOptions.ts: Simplified model picker for firepass (Kimi K2.5 Turbo only)
  - status.tsx: Display FirePass in status bar
  - login.tsx: Add FirePass option to provider selection
  - FirepassLoginFlow.tsx: New component for FirePass login flow
  
  Usage:
  1. Run /login and select "FirePass"
  2. Enter your Fireworks API key
  3. Model picker shows Kimi K2.5 Turbo

  Jonathan Evans · 2026-04-01 13:56:12 -07:00
  061251984e