Send a WhatsApp message. Your Mac starts coding. The agent asks questions. You answer from bed. Ship features in your pajamas.
Every message from every platform hits a single front door. From there, the router decides: cloud AI, local Orchestrator, or full agentic coding session.
You send a message from WhatsApp, Slack, Telegram, Discord, or SMS.
The intelligent-message-router classifies your intent against the skill manifest.
Orchestrator tasks → A2A WebSocket. General queries → Cloud AI. Everything agent goes through A2A.
Your Mac Orchestrator receives the task, reasons, acts, and reports back.
Prefix your message with a hyper symbol for instant, deterministic routing. No AI classification needed. No ambiguity. Just precision.
Route directly to your IDE's coding brain via A2A protocol
Dispatch a task requiring browser interaction via Computer Use
Direct coding session control — goals, files, heartbeats
Messages without a hyper symbol are classified by GPT against the skill manifest (60+ intents). This works great for natural conversation, but symbols give you instant, deterministic control when you know exactly what you want.
The Orchestrator isn't one monolith — it's a stack of specialized layers, each doing one thing exceptionally well.
Coding Session Manager
Agent-to-Agent Protocol
Code Intelligence
Universal Platform Bridge
Browser Automation
Model Context Protocol
Not 1,000 small connections — two clean, purpose-built communication channels. A2A for every agent conversation. MCP for every tool action.
Every agent speaks A2A. WhatsApp, Slack, Alexa, Google Home, Gemini Live, the web IDE — they all connect to the Orchestrator through one universal WebSocket protocol. Tasks, questions, progress, safety checks — all flow through this single artery.
Agents don't touch tools directly. When the Orchestrator needs to read a file, run a terminal command, search your knowledge base, or push to GitHub — it invokes MCP tools internally. This keeps the tool layer isolated, secure, and composable.
Why not HTTP? HTTP (port 8080) exists only for the Link Code Pro web IDE bridge — a user-facing UI, not an agent. All agent-to-Orchestrator communication goes through A2A.
Instead of building separate HTTP endpoints for every feature (status, search, diagnostics, goals, files...), we funnel everything through two clean channels. A2A handles the conversation. MCP handles the tools. No fragmentation. No confusion.
Monaco editor. File tree. Terminal. Git. AI chat with 5 modes. All connected to your Mac via the Orchestrator bridge.
Full VS Code editing experience with syntax highlighting, IntelliSense, and multi-tab support
Run shell commands on your Mac remotely via the Orchestrator bridge
Stage, commit, push, diff — full version control without leaving the browser
Code, Architect, Ask, Debug, Edit — each tuned for a different workflow
Vector-powered search that understands meaning, not just keywords
AI auto-fixes diagnostics: generates patch → applies → re-checks until clean
Token-aware context window: target file + imports + semantic chunks + repo map
Ghost text completions powered by your chosen LLM provider
Real-time error and warning feed from the Orchestrator Intel Layer
Every messaging platform becomes a coding terminal. Same commands, same brain, same results.
Voice Agents — All via A2A
Install the Orchestrator on your Mac. Connect your messaging apps. Start shipping from anywhere.