J.A.R.V.I.S. Protocol

Claude Code × Remote Interface Research

A comprehensive analysis of turning Claude Code into a personal AI assistant accessible from anywhere — voice, mobile, messaging, and home automation.

RESEARCH COMPILED 2026-04-11  ·  MIDAS TOUCH PROJECT  ·  CLASSIFICATION: OPEN_

Scroll to begin
Systems Index
  1. 01 Executive Overview
  2. 02 Remote Access from Mobile
  3. 03 Voice Interaction Layer
  4. 04 Messaging Bots & Channels
  5. 05 Home Automation
  6. 06 Headless & Daemon Mode
  7. 07 MCP Server Ecosystem
  8. 08 Architecture Patterns
  9. 09 Open-Source Landscape
  10. 10 Quick Start Guides
  11. 11 Cost Analysis
  12. 12 Final Verdict & Recommendation
6 Architecture Patterns
9+ Open-Source Projects
5 Remote Access Methods
$25-55 Monthly Operating Cost
70+ HA MCP Tools
8 Messaging Channels
01

Executive Overview

The Jarvis paradigm — an always-available, context-aware, voice-enabled personal AI — is no longer science fiction. Claude Code, combined with its MCP server ecosystem, headless mode, and remote control capabilities, provides every building block needed to construct a personal assistant that rivals the fictional original. This report synthesizes research across six domains: remote mobile access, voice interaction, messaging bridges, home automation, daemon orchestration, and the open-source tooling landscape.

Sid Bharath's "How I Built Jarvis"
Case Study
Built entirely through conversation with Claude Code. Daily ops: calendar planning, email triage, habit tracking, multi-client project management, personal CRM.
Feasibility
9.5/10
Expand details
  • No coding required — entire system built through natural language conversation
  • Built incrementally over weeks: task tracking first, then email, then daily planning
  • Key insight: "Claude Code is an AI agent with access to your computer" — not just a chatbot
  • Uses MCP servers for Gmail and Calendar integration
  • Manages fitness/health/relationship goals with weekly reviews
  • Maintains context across multiple client projects and follows up with contacts
↗ sidbharath.com
Always-On Agent Server
DIY Build
Hetzner VPS + Docker + Telegram bridge. Brain/body separation architecture with hot memory and self-deploy capability. $25-55/mo for 24/7 operation.
Feasibility
8.5/10
Expand details
  • Architecture: Immutable daemon (body) vs mutable instructions (brain)
  • telegram_daemon.py: Telethon client + event router + socket server (92 JSON-RPC methods)
  • Memory: Hot memory via memory.md + long-term storage in Obsidian vault synced with git
  • Self-deploy: Agent can modify its own CLAUDE.local.md, then trigger Coolify redeploy
  • Security: Access control matrix based on chat_id, not message content (prompt injection defense)
  • Scheduling: CRONTAB.md parsed every 60 seconds for scheduled tasks
  • Cost: Hetzner VPS ~$5/mo + Claude API usage $20-50/mo
↗ okhlopkov.com
02

Remote Access from Mobile

Five distinct pathways exist for accessing Claude Code from a phone or tablet — from Anthropic's official remote control to raw SSH tunnels. Each trades off convenience against control.

Claude Code Remote Control
Official
Run /rc to get a QR code. Scan with Claude app (iOS/Android) for full session control. No inbound ports opened — all traffic via Anthropic API over TLS.
Feasibility
9.2/10
Expand details
  • Available on Pro, Max, Team, Enterprise plans
  • Server mode: claude remote-control — stays running, waits for connections
  • Interactive mode: claude --remote-control — full local + remote session
  • --spawn worktree — each session gets its own git worktree
  • --capacity <N> — up to 32 concurrent sessions
  • Auto-reconnects after network drops (up to ~10 minutes)
  • Limitation: Can't START sessions from mobile, only continue existing ones
TERMINAL
# Start remote control server on desktop
claude remote-control

# Or with worktree isolation + multi-session
claude remote-control --spawn worktree --capacity 8

# Interactive: local + remote simultaneously
claude --remote-control
↗ code.claude.com/docs
SSH + Tailscale + Tmux
DIY
Desktop running Claude Code at home + Tailscale private network. Termux (Android) or Blink (iOS) for terminal. tmux/zellij for persistent sessions.
Feasibility
7.5/10
Expand details
  • Setup time: approximately 20 minutes
  • Use mosh instead of SSH for connection resilience across network hops
  • Pain points: SSH drops on phone sleep/network transitions, tiny screen
  • Tailscale creates a private mesh network — no port forwarding needed
  • tmux/zellij keeps sessions alive when terminal disconnects
SETUP
# Install Tailscale on both devices
curl -fsSL https://tailscale.com/install.sh | sh
tailscale up

# On desktop: start tmux with Claude Code
tmux new -s jarvis
claude

# From phone (Termux/Blink): connect
mosh user@desktop-tailscale-ip -- tmux attach -t jarvis
↗ builder.io
Termux + Tailscale Direct
DIY
Minimal setup: Tailscale on both devices, SSH from Termux to desktop, tmux for persistence. Lean and battle-tested.
Feasibility
7.0/10
Expand details
  • Android-specific approach using Termux terminal emulator
  • Tailscale handles NAT traversal automatically
  • tmux persistence means you can switch apps and reconnect
  • Lower overhead than web terminal solutions
↗ skeptrune.com
Web Terminal (ttyd / WeTTY / GoTTY)
Community
Share terminal over HTTP/HTTPS. Access Claude Code via any browser — no app install needed. Pair with Tailscale or ngrok for remote access.
Feasibility
7.2/10
Expand details
  • ttyd: Lightweight, shares terminal as web app — ttyd bash
  • WeTTY: Node.js-based, uses xterm.js, supports authentication
  • GoTTY: Go-based, single binary, easy deployment
  • Claude Code Skill for WSL2 Remote Web Terminal available on MCP Market
  • Best paired with reverse proxy (nginx/caddy) + TLS for security
TTYD SETUP
# Install ttyd
brew install ttyd   # macOS
apt install ttyd    # Ubuntu/Debian

# Start web terminal with Claude Code
ttyd -p 7681 -c user:pass bash -c "claude"

# Access at http://localhost:7681
# Use Tailscale or ngrok for remote access
↗ ttyd on GitHub ↗ WeTTY on GitHub
Third-Party Apps & Templates
Community
Mobile IDE for Claude Code (iOS), Railway one-click cloud deployment, The Vibe Companion web UI, and Takopi Telegram router.
Feasibility
6.8/10
Expand details
  • Mobile IDE for Claude Code (iOS): CloudKit sync between iPhone and Mac
  • Railway template: One-click claude-code-ssh cloud deployment
  • The Vibe Companion: Uses hidden -sdk-url flag, open-source web UI
  • Takopi: Routes Claude Code through Telegram for mobile interaction
↗ builder.io roundup
Method Setup Time Platform Latency Security Reliability
Official Remote Control 2 min iOS, Android, Web Low TLS via Anthropic Excellent
SSH + Tailscale + tmux ~20 min Any terminal Low-Med WireGuard Good
Termux + Tailscale ~15 min Android Low WireGuard Good
Web Terminal (ttyd) ~10 min Any browser Medium Depends on proxy Fair
Third-Party Apps Varies iOS / Web Varies Varies Varies
03

Voice Interaction Layer

The voice layer transforms Claude Code from a terminal tool into something that speaks. Five approaches exist, ranging from simple TTS overlays to full wake-word-activated conversational pipelines running entirely on-device.

Clarvis — Jarvis-Style Notifications
Community
"Sir, I have completed project auth. JWT implementation successful." TypeScript/Bun hook processor that summarizes Claude Code outputs into spoken Jarvis-style updates.
Feasibility
8.8/10
Expand details
  • Processes Claude Code "Stop" hooks to capture assistant messages
  • Summarizes with LLMs to create 1-3 sentence Jarvis-style updates
  • Speaks through lspeak with first-person JARVIS personality
  • Configurable per-project via TOML with mode-based behavior
  • Low-friction: add to existing Claude Code workflow as a hook
INSTALL
git clone https://github.com/nickpending/clarvis
cd clarvis
bun install
# Configure as Claude Code stop hook
↗ GitHub (7 stars)
Samantha — Voice Assistant MCP
Community
MCP server with wake word detection ("Hey Samantha"). Local Whisper STT + Kokoro TTS — fully private. Multiple personalities: Samantha, Jarvis, Alfred.
Feasibility
8.2/10
Expand details
  • Always listening with wake word activation
  • Natural conversation with automatic pause detection
  • Voice commands for interrupt, skip, sleep
  • Cross-platform: macOS, Linux, Windows
  • Privacy-first: all processing happens locally
INSTALL
pip install samantha-voice-assistant

# Add as MCP server to Claude Code
claude mcp add samantha -- samantha
↗ GitHub
Picovoice Voice Pipeline
Community
Full on-device voice pipeline: Porcupine wake word + Cheetah streaming STT + Orca streaming TTS. Zero cloud dependency for the voice layer.
Feasibility
8.5/10
Expand details
  • Wake Word: Porcupine (custom "Hey Claude", "Hey Jarvis", etc.)
  • STT: Cheetah Streaming Speech-to-Text (real-time)
  • TTS: Orca Streaming Text-to-Speech
  • All runs locally — no cloud dependency for the voice pipeline
  • Only the LLM call goes to Anthropic API
PYTHON
pip install pvporcupine pvcheetah pvorca pvrecorder pvspeaker anthropic

# Pipeline: Wake Word → STT → Claude API → TTS
# See picovoice.ai for full implementation guide
↗ picovoice.ai
AgentVibes — Simple TTS
Community
Minimal TTS plugin for Claude Code. Single npx install gives the assistant a voice. Good for quick experimentation.
Feasibility
9.0/10
Expand details
  • Lowest barrier to entry for voice output
  • npx install — no complex configuration
  • TTS only (no STT/wake word)
  • Good starting point before graduating to Samantha or Picovoice
↗ GitHub
Whisper + Kokoro Local Pipeline
DIY
Whisper MLX (Apple Silicon optimized) for STT + Kokoro TTS for output. Common open-source pattern. Caveat: Whisper struggles with accented speech.
Feasibility
7.2/10
Expand details
  • Whisper MLX: Apple Silicon optimized speech-to-text
  • Kokoro TTS: High-quality local text-to-speech
  • Pipeline: Whisper STT → Claude API → Kokoro TTS
  • Known issue: Whisper accuracy degrades with accented speech
  • More manual setup than Picovoice/Samantha but fully customizable
↗ Reddit discussion
Home Assistant + Voice
Experimental
Atom Echo with Claude and continuous conversation. Custom-trained wake word, streaming TTS to Sonos/Google speakers. Ambient smart home voice control.
Feasibility
6.5/10
Expand details
  • Atom Echo: ~$13 hardware for dedicated voice input
  • Custom wake words trainable via HA
  • Streams TTS output to existing Sonos/Google/Alexa speakers
  • Continuous conversation mode — no repeated wake words
  • Requires Home Assistant instance with Claude integration
↗ HA Community
04

Messaging Bots & Channels

Messaging apps provide the most natural "Jarvis" interface — you text your AI the same way you text a person. Claude Code now has native Telegram and Discord support, plus community bridges for WhatsApp, Signal, Slack, iMessage, and Teams.

Claude Code Channels
Official / Native
Native Telegram and Discord support baked into Claude Code. Create a bot via BotFather, link with /telegram:configure, and text your AI agent like a person.
Feasibility
9.5/10
Expand details
  • First-party support — most reliable integration path
  • Full Claude Code session accessible from the messaging app
  • Inherits all MCP server capabilities
  • Setup: create Telegram bot via BotFather, then run /telegram:configure
SETUP
# 1. Create bot via Telegram @BotFather
# 2. Get bot token
# 3. In Claude Code:
/telegram:configure
# 4. Paste token when prompted
# 5. Text your bot from any device
↗ Setup guide
ClawdBot / OpenClaw
Community
Multi-channel personal AI assistant: WhatsApp, Telegram, Slack, Discord, Signal, iMessage, MS Teams, and WebChat. Speaks and listens on macOS/iOS/Android. $6/mo server.
Feasibility
8.2/10
Expand details
  • 8 channels: WhatsApp, Telegram, Slack, Discord, Signal, iMessage, MS Teams, WebChat
  • Live Canvas rendering for rich visual responses
  • Multi-agent routing per channel — different behaviors per platform
  • Gateway daemon runs via launchd (macOS) or systemd (Linux)
  • Voice: can speak and listen on macOS/iOS/Android
  • Operating cost: approximately $6/month
↗ GitHub
Kai — Telegram Dev Assistant
Community
Telegram bot that turns Claude Code into a personal dev assistant. Send messages, get full tool-use responses. Home automation, translation, any REST endpoint.
Feasibility
8.0/10
Expand details
  • Claude Code runs in response to Telegram messages
  • Full tool use — file operations, git, terminal commands via chat
  • Home automation integration via REST API calls
  • Translation, research, anything accessible via command line
↗ Hacker News
05

Home Automation Integration

Home Assistant is the clear winner for smart home integration with Claude. The official MCP server exposes 70+ tools — lights, thermostats, switches, automations — all accessible via natural language through Claude Code.

Home Assistant MCP Server
Official
Official HA integration with 70+ tools. Full programmatic access via REST API and WebSocket. Claude Code supports remote MCP servers natively.
Feasibility
9.0/10
Expand details
  • Official integration at home-assistant.io/integrations/mcp_server/
  • 70+ tools covering all HA entities and automations
  • Claude Code supports remote MCP servers natively — no proxy needed
  • REST API + WebSocket for real-time state updates
  • Control lights, thermostats, locks, covers, media players, and more
↗ Home Assistant docs
homeassistant-mcp (Community)
Community
Community MCP server for Claude agents. Full HA instance access via REST API and WebSocket with 70+ tools. More flexibility than the official integration.
Feasibility
8.2/10
Expand details
  • Alternative to official integration with community maintenance
  • May have features ahead of the official server
  • Same 70+ tools covering HA entities
↗ GitHub
ha-claude Smart Home Addon
Community
HA addon with multi-provider support. Create automations, debug configs, manage smart home through natural language. Full automation authoring.
Feasibility
7.5/10
Expand details
  • HA addon — installs directly within Home Assistant
  • Multi-provider AI support (not locked to Claude)
  • Create and debug automations via natural language
  • Config file management and debugging
↗ GitHub
Claude Code Plugin for HA
Community
SSH access for commands + SSHFS mount for config files + custom MCP for HA API. Create automations and debug configurations via natural language.
Feasibility
7.0/10
Expand details
  • SSH access: run commands directly on HA host
  • SSHFS mount: edit config files as local filesystem
  • Custom MCP: HA API access for entity control
  • Full "vibe-coding" workflow for smart home configuration
↗ HA Community
06

Headless & Daemon Mode

The key to an always-on Jarvis is daemon operation — Claude Code running headless, responding to events rather than interactive prompts. Headless mode (--print) is production-ready. A combined remote-control + headless mode is the missing piece for true cloud-native agents.

Headless Mode (--print / -p)
Official
Run without interactive terminal. Output formats: text, json, stream-json. Tool control, model selection, budget limits. Perfect for scripting and daemon wrappers.
Feasibility
9.5/10
Expand details
  • Output formats: text, json, stream-json
  • Tool control: --allowedTools, --disallowedTools, --tools
  • Model/limits: --model, --max-turns, --max-budget-usd
  • MCP support: --mcp-config
  • Perfect for CI pipelines, cron jobs, event-driven wrappers
USAGE
# Simple headless call
claude -p "Summarize today's unread emails"

# JSON output with tool restrictions
claude -p "Check server status" \
  --output-format json \
  --allowedTools "Bash,Read" \
  --max-turns 5

# With MCP servers and budget cap
claude -p "Turn off all lights" \
  --mcp-config ~/.mcp/ha.json \
  --max-budget-usd 0.50
↗ Headless docs
Remote Control + Headless Combined
Feature Request
GitHub issue #30447: combining remote control with headless mode. Would unlock cloud-first, always-on agent scenarios. The missing piece for true Jarvis.
Feasibility
4.0/10
Expand details
  • Currently remote control requires interactive mode on the host
  • Headless mode cannot accept remote control connections
  • Combining them would enable: cloud VPS → headless daemon → phone control
  • This is the most-requested feature for always-on agents
  • Status: open feature request, no implementation timeline
↗ GitHub Issue #30447
Internal Projects (Leaked)
Leaked/Unconfirmed
"Chyros" — persistent always-on background agent. "Conway" — unreleased always-on background AI. "DAEMON" mode — persistent background process. All unconfirmed.
Feasibility
???
Expand details
  • Chyros: Persistent, always-on background agent — leaked project name
  • Conway: Unreleased always-on background AI — likely internal codename
  • DAEMON mode: Persistent background process — natural evolution of headless mode
  • All sourced from leaks/reports — no official confirmation
  • Suggests Anthropic is actively working on this problem space
Background Tasks & Subagents
Official
Claude Code can keep long-running processes active, spawn subagents for parallel workflows, and trigger actions via hooks. The autonomous agent foundation.
Feasibility
8.8/10
Expand details
  • Background processes persist beyond individual prompts
  • Subagents enable parallel development workflows
  • Hooks system for automatic pre/post actions
  • Anthropic is explicitly investing in autonomous agent capabilities
↗ Anthropic announcement
07

MCP Server Ecosystem

MCP (Model Context Protocol) servers are the "hands and feet" of a Jarvis system. They extend Claude Code with structured access to external services — voice I/O, smart home control, browser automation, and system management.

Jarvis MCP
Community
Browser-based voice I/O for AI conversations. 30+ languages for speech recognition. Remote access from phone/tablet. Zero extra software — runs in browser.
Feasibility
8.5/10
Expand details
  • 30+ languages for speech recognition
  • Remote access from phone/tablet via browser
  • Optional Whisper streaming for low-latency transcripts
  • One-command setup
INSTALL
npx @shantur/jarvis-mcp --install-claude-code-config --local
↗ GitHub (75 stars)
Browser Control MCP (Playwright)
Built-in
Full browser automation: navigate, click, fill forms, screenshot, evaluate JS. Part of the Claude Code ecosystem. Enables web-based task automation.
Feasibility
9.2/10
Expand details
  • Navigate to URLs, click elements, fill forms
  • Screenshot pages for visual verification
  • Evaluate JavaScript in page context
  • Handle dialogs, file uploads, network request interception
  • Built into Claude Code MCP ecosystem — no additional setup
Home Assistant MCP
Official
Control lights, thermostats, switches, automations. 70+ tools available through the official HA MCP server integration.
Feasibility
9.0/10
Expand details
  • 70+ tools for smart home entity control
  • REST API + WebSocket for real-time state
  • Automation creation and management
  • Scene activation, script execution
↗ Official docs
System Control MCPs
Community
File management, git operations, terminal commands, Docker management. The "hands" that let Jarvis interact with your system infrastructure.
Feasibility
9.0/10
Expand details
  • File management: read, write, search, organize
  • Git operations: commit, branch, merge, review
  • Terminal commands: execute with output capture
  • Docker: container management, logs, deployment
↗ pulsemcp.com
08

Architecture Patterns

Six reference architectures, ordered by complexity. Each is a viable path to a Jarvis-like system. Most real deployments combine elements from multiple patterns.

Pattern 1: Terminal-First (Simplest)
Desktop
Claude Code
— SSH / Tailscale →
Phone
Termux / Blink
— tmux →
Persistent
Session
Complexity
Low
Pattern 2: Official Remote Control
Desktop
Claude Code
— Anthropic API / TLS →
Phone
Claude App

QR code scan initiates connection. No inbound ports. Auto-reconnect on network drops.

Complexity
Minimal
Pattern 3: Telegram / Discord Bridge
Phone
Telegram
→ Bot API →
Server
Claude Code -p
→ Response →
Phone
Telegram
Complexity
Medium
Pattern 4: Full Voice Assistant
Microphone
Wake Word
Porcupine / Vosk
STT
Whisper
Claude API
TTS
Kokoro / Orca
Speaker
Complexity
Medium-High
Pattern 5: Always-On Server Agent
VPS (Docker)
telegram_daemon.py
Claude Code
CLI -p
←→
CRONTAB.md
Scheduled tasks
MCP Servers
Telegram, HA, Coolify
Memory
Hot + Long-term
Complexity
High
Pattern 6: Full Jarvis Stack (Ultimate)
Voice In
Whisper STT
Claude Code
+ MCP Servers
Voice Out
TTS
Home Assistant MCP
Lights, Thermostat, Locks
Telegram MCP
Messaging Bridge
Browser Control MCP
Playwright Automation
File / System MCP
Git, Docker, Terminal
Complexity
Very High

All patterns converge here. This is the endgame. Each MCP server is independently deployable.

09

Open-Source Landscape

Project Stars Description Category Status
ClawdBot / OpenClaw High Multi-channel personal AI assistant (8 platforms) Messaging Active
Jarvis MCP 75 Browser-based voice I/O for AI tools Voice Active
Clarvis 7 Jarvis-style voice notifications via hooks Voice Beta
Samantha 4 Voice assistant MCP with wake word detection Voice Beta
isair/jarvis 100% private AI voice assistant Voice Experimental
AgentVibes Simple TTS plugin for Claude Code Voice Active
ha-claude Smart home AI assistant addon for HA Home Auto Beta
homeassistant-mcp HA MCP server for Claude agents Home Auto Active
awesome-claude-code-toolkit 135 agents, 35 skills, 42 commands Meta Active
10

Quick Start Guides

Copy-paste commands to get each component running. Start with Path A (fastest), then layer on additional capabilities.

Path A — Fastest
Official Remote Control
Access Claude Code from your phone in 2 minutes flat.
TERMINAL
# On your desktop/laptop
claude remote-control

# Scan QR code with Claude app
# Done. Full session from phone.
Setup: ~2 minutes
Path B — Always-On Messaging
Telegram Bot Bridge
Text your AI like you text a friend. Native Claude Code integration.
SETUP
# 1. Open Telegram, message @BotFather
# 2. Send: /newbot
# 3. Follow prompts, get token
# 4. In Claude Code:
/telegram:configure

# Paste your bot token
# Text the bot from any device
Setup: ~5 minutes
Path C — Voice Output
Jarvis-Style Voice (Clarvis)
Claude speaks to you: "Sir, deployment complete."
INSTALL
git clone https://github.com/nickpending/clarvis
cd clarvis && bun install

# Or for simpler TTS:
npx agent-vibes
Setup: ~10 minutes
Path D — Full Voice Loop
Wake Word + STT + TTS
"Hey Jarvis" activation with spoken responses.
INSTALL
# Option 1: Samantha MCP (recommended)
pip install samantha-voice-assistant
claude mcp add samantha -- samantha

# Option 2: Picovoice pipeline
pip install pvporcupine pvcheetah pvorca \
  pvrecorder pvspeaker anthropic

# Option 3: Browser-based (Jarvis MCP)
npx @shantur/jarvis-mcp \
  --install-claude-code-config --local
Setup: ~15-30 minutes
Path E — Smart Home
Home Assistant Integration
"Turn off all lights" from Claude Code. 70+ HA tools.
SETUP
# In Home Assistant:
# Settings → Integrations → Add → MCP Server

# In Claude Code MCP config:
# Add your HA instance URL + token
# See: home-assistant.io/integrations/mcp_server/
Setup: ~10 minutes (with existing HA)
Path F — Full Stack
Always-On VPS Agent
24/7 autonomous agent with scheduled tasks, memory, and self-deploy.
DOCKER
# 1. Provision Hetzner VPS (~$5/mo)
# 2. Install Docker + Coolify
# 3. Deploy telegram_daemon.py
# 4. Configure:
#    - CLAUDE.local.md (brain)
#    - CRONTAB.md (schedule)
#    - memory.md (hot memory)
#    - MCP server configs
# 5. Set access control matrix

# See: okhlopkov.com/always-on-ai-agent-server-setup/
Setup: ~2-4 hours
11

Cost Analysis

Minimal Setup
$20/mo
  • Claude Pro subscription ($20/mo)
  • Official Remote Control (included)
  • Telegram bot bridge (free)
  • AgentVibes TTS (free, open-source)
  • Local desktop only
Full Jarvis
$55-100/mo
  • Claude Max ($100/mo) or API ($20-50)
  • Dedicated VPS ($10-20/mo)
  • ClawdBot multi-channel ($6/mo)
  • Picovoice pipeline (free tier)
  • Home Assistant + dedicated hardware
  • Custom domain + TLS
  • Coolify for self-deploy

Recommended Stack Breakdown

Claude Pro subscription $20/mo
Hetzner VPS (CX22) $5/mo
Tailscale $0/mo
Telegram Bot API $0/mo
Samantha / Clarvis $0/mo
Home Assistant $0/mo
Total (Recommended) $25/mo
12

Final Verdict & Recommendation

System Assessment: Operational

The Jarvis interface is buildable today. Every component exists in production-ready or near-production form. The critical path has no blockers — only tradeoffs between convenience and control.

The recommended starting point is a three-layer stack: (1) Official Remote Control for immediate mobile access with zero infrastructure, (2) Telegram bot bridge for always-available messaging that survives desktop power-offs, and (3) Samantha or Clarvis for voice personality. This gives you 80% of the Jarvis experience at $25/month.

The missing piece is the combined remote-control + headless mode (GitHub issue #30447). Once Anthropic ships this, true cloud-native Jarvis becomes trivial: a $5 VPS running Claude Code in daemon mode, accessible from any device via Telegram, voice, or the Claude app. The leaked codenames (Chyros, Conway, DAEMON) suggest this is actively being developed.

For Galen's Midas Touch project specifically: the existing Telegram-based orchestrator architecture already implements Pattern 5 (Always-On Server Agent). Adding voice output via Clarvis hooks and Home Assistant MCP would complete the Jarvis analogy without architectural changes.

Recommended Implementation Order

Phase 1: Immediate (This Week)
Enable Official Remote Control (claude remote-control). Set up Telegram bot via native Claude Code Channels. Install Clarvis or AgentVibes for voice output. Total cost delta: $0 (uses existing Pro subscription).
Phase 2: Near-Term (This Month)
Add Samantha MCP for wake-word voice input. Configure Home Assistant MCP server for smart home control. Set up Tailscale mesh for secure remote access to all devices. Cost: +$0-5/mo.
Phase 3: Evolution (Next Quarter)
Deploy always-on VPS agent with Docker + Coolify. Implement CRONTAB.md scheduling for autonomous tasks. Add ClawdBot for multi-channel coverage (WhatsApp, Signal, iMessage). Build custom memory system with hot/long-term separation. Cost: +$5-15/mo.