SECTION · STORY · 06 / 20
OAuth, not API keys. Voice, not typing.
Telegram, day one.
Three things every other agent product makes you fight for. RHOBEAR ships them in the box.
OAUTH ORCHESTRATION
Sign in once. Done.
- Sign in once with your Claude, OpenAI, or Pi account — same flow you already use.
- No key files to manage, no .env to leak, no rotation calendar.
- Uses your existing subscription quotas, not your bank account.
- RHOBEAR routes OAuth tokens locally — they never leave your machine.
- Revoke from the provider's dashboard like any other connected app. RHOBEAR can't hold your account hostage.
BRING YOUR KEY OR USE OURS
Dispatcher, not brain.
- BRING YOUR OWN KEY: direct provider talk, lowest latency, your bill, your quota.
- USE OURS: RHOBEAR's tiny coordination AI passes messages between your workers — it does not think for them.
- Your Claude session writes the code. Your Codex session reviews it. Ours just routes the envelope between them.
- Routing metadata only — never your prompts, your code, or your diffs.
- Flip between modes per-role from the settings tab. No reinstall.
WHISPER VOICE
On-device dictation.
- Local on-device dictation. No audio leaves your machine.
- ggml-base.bin downloads on first mic-click (~145MB, one-time, with consent).
- One-click activate from the chat dock or any prompt.
- Animated listening pill confirms it's listening — never a silent hot mic.
- Transcript drops into your active input field. Edit, then send.
DAY-ONE TELEGRAM
Push from the lock screen.
- Bot auth handled in the setup wizard — paste the token once, done.
- Immediate push when a PR is ready, Architect is blocked, Spark render is done, or owner-pending escalates.
- Reply from your phone to approve, reject, or pause a lane.
- Works on the lock screen — no need to unlock to triage.
- Mute-per-channel respected. Quiet hours, quiet hub.
FROM ZERO TO FIRST TELEGRAM PUSH
Ninety seconds, no documentation.
$ cargo tauri dev
pops > welcome. let's wire you up.
setup > step 1/3 · sign in with claude
[oauth flow opens · 12s]
setup > step 1/3 · ✓ claude account connected (sub quota: ok)
setup > step 2/3 · paste your telegram bot token
[token captured · 4s]
setup > step 2/3 · ✓ bot wired · test message sent to your chat
setup > step 3/3 · what should the crew work on first?
you > finish the workbench polish
architect > goal accepted · lanes [a,b] · gate: strict
foreman > opened PR #42 · +108 -15 · 2 files
telegram > 📬 PR #42 ready for review · /approve /reject
[push received on your phone · 87s total]