$ ./claude-voice-network-pack --init

Tell your phone Claude what to build.
Your desktop builds it while you walk.
The vault is the inbox.

Voice-mode dispatcher on your phone. Headless Claude Code worker on your desktop. Connected by a markdown task queue in your vault. Built once, runs while you sleep.

Get the pack — FREE

VERSION 2.0 / MAC ONLY / NO CREDIT CARD

01 / HOW IT WORKS

Voice conversation in. Real work out.

You talk to phone Claude in voice mode

Walking. Driving. At work. Voice conversation about what you're building. When the conversation reaches a doable next step, you say go.

Phone Claude writes a task to your vault

Single markdown file dropped in AI Hub/Task Queue/pending/ via the bridge. Plain text. Versioned. You can read it from any device.

Your desktop picks it up automatically

launchd watches the pending folder. New file fires the task-queue-worker. Task moves to in-progress/. Notification on your Mac.

Claude Code executes it headless

Full agentic loop. Read files. Write code. Run commands. Test. Inside your vault context. No babysitting. Built-in budget cap.

Voice-friendly result lands in completed/

Short sentences. No markdown. Phone Claude reads it to you on your next check-in. Conversation continues. More tasks queue. Loop.

02 / WHY THIS EXISTS

The gap nothing else closes.

Phone Claude voice mode can already think with you. It can't reach your vault. It can't fire your desktop. It can't run a build while you walk.

Anthropic's enterprise MCP Tunnels solves the bridge piece for Managed Agents customers. Doesn't reach consumer Claude.ai. Doesn't ship a worker. Doesn't ship the Playbook that makes the worker useful. This pack is the consumer-Claude version plus the methodology plus the async-worker pattern.

Built once. Used daily. Survives reboot, network blips, and the user habit of closing apps. Ships with 9 silent failures already solved — so you don't lose the 3 hours.

03 / WHAT YOU GET BACK

The walk that built the feature

You leave the laptop, voice-mode through a build session, agree on the next ship. Phone Claude writes the task. Desktop builds it. You walk home to a passing test suite and a voice readback of what landed.

Five specialist Projects, one vault

Discovery Co-pilot knows your current thinking. Build Co-pilot defends your scope. Sales Co-pilot remembers Monday's call. Content Co-pilot has your voice fingerprint. Personal-Memory Co-pilot is the mirror. None of them ask 'what are you working on?'

One tunnel, every tool

Obsidian, Stripe, GitHub, Supabase, custom MCPs — exposed through one phone. Same launchd pattern, different ports. Your phone becomes the remote for your whole stack.

Self-healing infrastructure

launchd KeepAlive on every daemon. cloudflared auto-reconnect on network blips. Obsidian keepalive auto-relaunches if you closed it by habit. Worker concurrency lock prevents stacked invocations. 9 silent-failure modes documented + solved.

04 / WHAT'S IN THE PACK

Five layers. Bridge + worker + playbook + vault + Projects.

01 / BRIDGE

bridge/INSTALL.md — 5-step Mac install (~20 min)
bridge/wrapper-template.sh — generic wrapper for any stdio MCP
bridge/mcp-obsidian-wrapper.example.sh — worked Obsidian example
bridge/plists/com.YOURNAME.mcp-proxy.plist + cloudflared-mcp.plist
bridge/smoke-test.sh — 5-layer health check (auto-detects URL)
bridge/troubleshooting.md — 9 silent-failure modes documented
bridge/named-tunnel-setup.md — permanent URL via your subdomain

02 / ASYNC WORKER

worker/task-queue-worker.sh — headless Claude Code execution
worker/com.YOURNAME.task-queue-watcher.plist — launchd WatchPaths
worker/obsidian-keepalive-check.sh — 4-layer disconnect prevention
worker/com.YOURNAME.obsidian-keepalive.plist — 30-sec interval
worker/voice-friendly-system-prompt.md — output format enforcement

03 / PLAYBOOK

playbook/Project-Design-Playbook.md — full methodology (13 sections, 2200 words)

04 / VAULT TEMPLATE

vault-template/README.md — install + why this structure works
vault-template/Atomic-Node-Spec.md — decision/inference/context/test schema
vault-template/Relay-Protocol.md — session activity feed rules
vault-template/Handoff-Pattern.md — per-project handoff format
vault-template/AI Hub/Task Queue/ — pending/in-progress/completed folders
vault-template/AI Hub/ — 8 starter folders + Active-Work-Log stub + atomic-node-template

05 / STARTER PROJECTS

templates/01-discovery — voice-driven discovery + ideation
templates/02-build — sprint planning + scope-defending
templates/03-sales — outreach + reply triage
templates/04-content — long-form + social fanout
templates/05-personal-memory — personal-knowledge mirror
(each = 4 files following canonical pattern: system-instructions / context-bundle / questions-bank / session-end-template)

05 / THE 9-FAILURE LIBRARY

Nine silent failures. Documented nowhere else in one place.

Building this stack hit each of these. Generic error messages, no stack traces, no path forward. The troubleshooting library lists symptom, root cause, and fix for all nine — including the two that emerged from the async-worker pattern (TCC + Obsidian disconnect).

Self-signed TLS cert rejection

Fix: NODE_TLS_REJECT_UNAUTHORIZED=0 in wrapper

Transport mismatch (/sse vs /mcp)

Fix: Claude.ai connectors expect StreamableHTTP at /mcp

launchd-spawned env stripped of PATH

Fix: Absolute paths + explicit PATH in plist EnvironmentVariables

Keychain miss under launchd context

Fix: Match -a $USER in add + lookup; unlock keychain at boot

Tunnel URL rotation on restart

Fix: Named tunnel + DNS CNAME (free Cloudflare tier)

Claude.ai client cached old tool schema

Fix: Delete + recreate connector (toggle doesn't clear cache)

Wrong-package endpoint paths (404 on every tool)

Fix: Pick MCP server actively maintained in last 60 days

macOS TCC blocks launchd from Desktop folder

Fix: Grant Full Disk Access to worker script + /bin/bash

Obsidian closes mid-session — phone Co-pilot tools vanish

Fix: 4-layer keepalive stack: login items + launchd interval + URI scheme launch + 3-strike escalation

06 / FAQ

What does the async-worker pattern actually do?

Phone Claude voice mode can already talk. With the bridge, it can read your vault. With the worker, it can dispatch real work. Conversation hits a doable next step → phone Claude writes a markdown task file into your vault → desktop launchd watcher fires → Claude Code executes headless inside your vault context using all its tools (Read, Write, Edit, Bash) → voice-friendly result lands in completed/. Your phone reads it back on your next check-in. The vault is the inbox. The worker is the hands. The bridge is the wire.

Why is this free? You used to charge $79.

Distribution matters more than price for a niche operator product. Free unlocks GitHub stars + Reddit + Hacker News + awesome-lists distribution that the $79 SKU blocked. The pack stands on its own. If you want it installed for you with custom Project setup, the SDS Operator Install ($2,500) is the revenue tier.

Mac only. What about Linux / Windows?

v1 is Mac only because launchd is Mac-specific. Linux (systemd) and Windows (scheduled tasks) are banked for v2. If you're on a Mac, install today.

Anthropic just announced MCP Tunnels. Why not wait?

Anthropic shipped MCP Tunnels for Managed Agents enterprise customers on 2026-05-19. Doesn't extend to consumer Claude.ai yet. Likely will in 6-12 months. When it does, the bridge piece sunsets cleanly — point your Claude.ai connector at Anthropic's hosted endpoint instead. The Playbook, the vault structure, the async-worker pattern, the 5 starter Projects don't go away. The methodology + worker pattern are the durable assets.

What stops the worker from running away with my time or money?

Three guardrails ship in the worker script. (1) Concurrency lock — only one worker runs at a time, max 30-min lock age before stale clear. (2) Per-task budget cap — --max-budget-usd 2 by default, configurable. (3) Voice-friendly output system prompt forces final response to be the readback, no work logs or technical traces. Worker failures get logged to completed/ as a failure note so phone Claude can report it; the task file stays in in-progress/ so you can retry.

What about disconnects? Obsidian closes and the pack breaks?

Solved. v2 ships a 4-layer keepalive stack: macOS Login Items (auto-boot on startup) + launchd agent firing every 30 sec + URI scheme launch (`obsidian://open?vault=NAME` forces vault to open, not just app process) + 3-strike escalation (kill + force-relaunch after 3 consecutive REST failures). Verified: kill Obsidian, REST API back to 200 in 20 sec. Documented as silent failure #9 in bridge/troubleshooting.md.

What stdio MCPs does the bridge work with?

Any of them. The wrapper template is generic — swap the MCP_SERVER_BINARY path + Keychain service name and you're done. Worked Obsidian example included. The async-worker pattern depends on the vault being writable from phone Claude, so Obsidian is the canonical case, but the bridge itself is service-agnostic.

Security — anyone with the tunnel URL can read my data?

Yes, until you add auth. The pack covers two hardening paths: named subdomain (eliminates URL rotation pain) + bearer-token middleware + OAuth 2.1 gateway (forces auth on every request). All shipped. Until you wire them, you have URL-secrecy only (random 4-word subdomain, ~30 bits entropy). Fine for low-risk vaults; harden before exposing financial / health / customer data.

Want this installed for you?

$2,500 Starter — SDS Operator Install. One-on-one install call, bridge + worker + keepalive stack provisioned, Full Disk Access verified, custom Project setup, vault structure migration, 30-day support. Two-week engagement, end to end. Reply to dailenhuntley@gmail.com with 'Operator Install' in the subject if interested.

07 / GET THE PACK

FREE. No credit card. Install today.

Mac only (Monterey+). Full pack on GitHub. Workshop tier of the SDS Operator System. If you want it installed for you, the SDS Operator Install ($2,500) is the next tier — but the pack stands on its own.

Get the pack — FREE Install service — $2,500 + Stack (advanced) — $497

If you operate multiple AI tools daily and want the voice-dispatcher pattern: the pack is free, install when you're ready. If you want it set up for you: Operator Install. If you're building serious agentic software: add the Stack.