2 Commits

Author	SHA1	Message	Date
javis-bot	ddebdd7542	feat(stream): single-account Go-Live — broadcast on the conversation's session ... Proven approach: the conversation (hear+speak) runs on @discordjs/voice; the Go-Live broadcast is a SEPARATE stream connection created on the SAME selfbot session (exactly like a real Discord client), so ONE account hears, speaks, AND broadcasts — no second login, no self_deaf, no voice conflict. - voice.ts captures its own voice session_id (adapter wrap) and exposes getSharedSession() {client, guildId, channelId, sessionId, botId}. - broadcast.ts threads it into the StreamContext. - selfbot.ts: when a shared session is present, build the Streamer on the conversation client and create the stream on its session_id (no login/joinVoice/ humanPause); teardown only stops the stream (never leaves voice/destroys the shared client). Falls back to the dedicated-account path otherwise. Verified live: Go-Live connected in ~7s while the conversation voice stayed ready, and the broadcast was visible in Discord — all on one account. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>	2026-06-13 22:37:26 +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