Skip to content

v2.10.0

Choose a tag to compare

@omnigentx omnigentx released this 29 Jun 03:21
· 190 commits to main since this release
61b0563

This release adds Telegram & Zalo messaging gateways and fixes a significant memory-recall latency regression.

✨ Features

Messaging Gateways — Telegram & Zalo (#113)
Chat with a Jarvis agent directly from Telegram and Zalo.

  • Long-polling Bot APIs — no public domain or webhook required.
  • Inbound images are passed to the agent as multimodal input.
  • In-chat slash commands: /new (/reset, /clear), /agent <name>, /whoami (/id), /help.
  • Secure onboarding: unauthorized senders never reach the agent — the bot replies with only their user id, so you can allow-list it without ever opening access to everyone.
  • Configurable live from Settings → Messaging Gateways (no restart); the UI warns when the allow-list is set to *, and bot tokens are always redacted from logs.

Memory — retrieval telemetry (#108)

  • Real retrieval-latency measurement and a redesigned "Recent searches" panel.

⚡ Performance & Fixes

Memory — reranking latency on CPU (#112)

  • Fixes a multi-second recall stall when reranking the top 20 candidates. The previous default reranker (Qwen/Qwen3-Reranker-0.6B, a 600M causal LM) measured ~0.87 s/candidate on CPU — about 17 s to rerank the top 20 for a one-line query. The default is now BAAI/bge-reranker-v2-m3, a multilingual (VI + EN) cross-encoder roughly 10× cheaper on CPU, and rerank_top_k is reduced from 20 → 5 (each candidate is a forward pass, so latency scales with it). Recall now stays well under ~1 s.
  • Reranker-model switches now stream real-time download progress in Settings instead of hanging silently on the first recall.
  • The chat "tools used" panel now shows each tool's own result.

🔧 Maintenance

  • Bump actions/checkout 6 → 7 (#110) and actions/cache 5 → 6 (#109).

Full changelog: v2.9.0...v2.10.0