Repository navigation
v0.2.0 — Telegram-bot feature parity
Brings opencode-talk-bridge close to feature parity with grinev/opencode-telegram-bot, adapted to Nextcloud Talk (no inline buttons → numbered-text pickers; live streaming via message editing).
Phase 1 — streaming + core UX
- Live response streaming by editing one Talk message (
RESPONSE_STREAMING, throttled) - Tool / thinking service messages from the SSE stream
- Agent questions (
question.asked) answered by number or free text - Numbered pickers:
/sessions,/model,/agent
Phase 2 — breadth + i18n
/rename,/detach,/projects,/worktree,/commands,/mcps,/messages(revert/fork)- Per-conversation project/worktree directory binding
- Background-session notifications
- i18n (German + English) via
BOT_LOCALE
Phase 3 — voice & tasks
- File/image input inlined as OpenCode file parts
- Voice notes → STT (Whisper-compatible) into the prompt
- Spoken replies (TTS) shared as audio,
/ttsper conversation - Scheduled tasks:
/task,/tasklist, SQLite-backed daemon scheduler
143 tests, CI green on Python 3.10–3.13.
Out of scope (by design): /opencode_start|stop (the menubar app/launchd owns the OpenCode process) and Telegram-only plumbing.
Full diff: v0.1.1...v0.2.0