Pending: Chat bot platform (Telegram vs Discord vs other)
User Tasks
Summary
Access the Opus system from a phone via terminal and/or voice interface.
Problem / Motivation
Currently the system is only accessible from a desktop terminal. Being able to
interact on the go — capture ideas, check status, give commands — is essential
for a true “second brain” experience.
Proposed Solution
Set up mobile-friendly access to the system, starting with terminal access
and expanding to voice interaction.
Phase 1 is simple if VPS (FR-019) is set up — just SSH from phone.
Telegram bot is probably the best Phase 2 approach for Android.
Voice is a stretch goal but would be very powerful.
Open Questions
⇒
No open questions.
Phase Overview
Phase
Description
Status
Phase 1
Terminal Access
—
Phase 2
Telegram/Chat Bot
—
Phase 3
Voice Interface
—
Phase 1: Terminal Access —
Goal: Enable basic SSH access to Opus from a phone.
File / Feature
Details
Owner
Status
SSH client on phone
Termux on Android / Blink on iOS
mv
—
VPS SSH access
VPS accessible via SSH (depends on FR-019)
opus
—
Quick-command aliases
Aliases for common operations
opus
—
Phase 2: Telegram/Chat Bot —
Goal: Enable conversational access to Opus via a chat platform.
File / Feature
Details
Owner
Status
Telegram bot
Forwards messages to Claude Code sessions
opus
—
Session mapping
Each Telegram chat maps to a Claude Code session ID in SQLite. /newchat clears the mapping. See session-mapping-pattern.
opus
—
Proactive pitches
Claude detects pain points or improvement opportunities and sends a pitch via Telegram (Problem → Proposal). User approves/rejects inline.
mv
—
Delivery notifications
Claude sends a summary via Telegram when a task is completed. Spec auto-closed, ready for review.
mv
—
Receive briefings
Receive briefings and notifications via Telegram
opus
—
Quick capture
Send quick capture notes to vault/90_inbox/
opus
—
Progress notify script
Simple shell script to send status updates during long tasks. See ClaudeClaw Rebuild Prompt (scripts/notify.sh)
—
Messaging Command Routing:
Incoming chat messages (via Telegram bot) are parsed for structured commands and routed to the appropriate internal skill or agent:
Command
Routes To
/feature <text>
Features specialist agent → creates FR
/approve FR-XXX
Workflow state machine → advance to “go”
/reject FR-XXX
Workflow state machine → archive
/go FR-XXX
Complexity routing → dispatch
/go FR-XXX --team
Force team routing
/go FR-XXX --phases 1,2
Scope-limited dispatch
/status
Status skill → reply with summary
/features
Feature dashboard query → reply with list
Free text
Nexie/Claude interprets intent
The routing layer maps chat commands to internal skills/agents, handles unknown commands gracefully, and replies with structured responses.
Batch Decision Parsing: When the system sends open questions with numbered/lettered options (e.g., “1. Sources: a) WA only b) WA + newsletters”), the user can reply with a compact batch answer like “1a 2c 3c”. The parser:
Extracts question-option pairs from the reply
Looks up the corresponding FR and its open questions
Applies each decision to the FR file (marks chosen option, moves to “Decided”)
Advances the workflow if all decisions are resolved
Phase 3: Voice Interface —
Goal: Enable hands-free voice interaction with Opus.
File / Feature
Details
Owner
Status
Voice-to-text input
Whisper or similar STT
opus
—
Text-to-voice output
TTS for briefings
opus
—
Hands-free mode
Hands-free interaction mode
opus
—
Prerequisites / Gap Analysis
Requirements
Requirement
Description
REQ-1
Can send a command to Opus from phone and receive a response
REQ-2
Can capture a quick note from phone that lands in the vault
REQ-3
Daily briefings are accessible from phone
Current State
Component
Status
Details
VPS
—
FR-019 not yet started
Phone SSH client
—
Not configured
Gap (What’s missing?)
Gap
Effort
Blocker?
VPS deployment (FR-019)
High
Yes (Phase 1)
Telegram bot setup
Med
No
Test
Manual tests
Test
Expected
Actual
Last
SSH from phone to VPS
Successful connection
pending
-
Run Opus command from phone
Receives response
pending
-
Quick capture from phone
Note appears in vault/90_inbox/
pending
-
AI-verified tests
Scenario
Expected behavior
Verification method
…
…
…
E2E tests
Scenario
Assertion
…
…
Integration tests
Component
Coverage
…
…
Unit tests
Component
Tests
Coverage
…
…
…
History
Date
Event
Details
2026-02-26
Created
Created as part of Phase 1 foundation
2026-02-27
Renumbered
From FR-032 to FR-022
2026-02-28
Rewritten
Aligned to feature-request template
2026-03-04
Updated
Added messaging command routing and batch decision parsing (inspired by Nexie)
References
FR-019 (VPS Deployment) — required for SSH access from phone
FR-024 (Text to Speech) — voice interface overlaps with Phase 3