2 Commits

Author	SHA1	Message	Date
javis-bot	2c38e7576d	perf: unify Ollama num_ctx so a voice turn keeps one resident model ... Ollama keeps a separate loaded model instance per (model, num_ctx). The main agentic chat used num_ctx=8192 while the router/enrichment/digest passes used 4096, so every voice turn forced at least one cold reload (~3.4s) when switching context sizes — the dominant per-turn latency (measured: resident chat call 0.27s vs cold 3.4s). Introduce a single OLLAMA_NUM_CTX (default 8192, env-tunable for tight VRAM) used by call_llm_direct, chat_with_messages, call_llm_streaming and the planner, collapsing a turn to one resident instance. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>	2026-06-14 00:19:53 +09:00
javis-bot	c4abf63f38	Add Discord-native hybrid front-end for Jarvis (bot + bridge) ... Transform isair/jarvis into a Discord-controlled voice assistant running on the Ubuntu VNC desktop, keeping the mature ~39k-line Python brain intact. - bot/ (Node + bun, discord.js): /자비스 slash commands (ephemeral), voice channel join + voice receive/playback, pluggable VNC screen broadcast (selfbot live / noVNC / screenshot) - bridge/ (Python, Flask): wraps jarvis STT + run_reply_engine + Piper TTS behind a thin localhost HTTP API - .env.example, scripts/ (start_bridge/start_bot/dev), README rewrite, docs/language-comparison.md and docs/vnc-xfce-setup.md Language decision: hybrid (Python brain + Node/bun Discord layer) because Discord blocks bot video; native screen broadcast only works via a Node selfbot library.	2026-06-09 14:51:05 +09:00