HeyZoku

Product Introduction

1. Definition: HeyZoku (branded as Zoku) is a native macOS application that functions as a voice-first, agentic development environment. Technically, it is a multi-terminal orchestration layer that manages and controls multiple AI-powered coding agent CLIs (Command Line Interfaces) simultaneously on a single visual canvas.
2. Core Value Proposition: It exists to solve the cognitive overhead and inefficiency of managing multiple AI coding assistants in parallel. Its primary value is enabling developers to orchestrate an "army" of agents (like Claude Code, Cursor, and OpenAI Codex) through on-device voice commands, eliminating context switching, tab management, and manual agent babysitting.

Main Features

1. Multi-Agent Canvas: Zoku provides a unified workspace where up to ten different coding agent CLIs run as live, interactive terminal sessions side-by-side. Each agent is visually distinct and assigned a unique, spoken name (e.g., "Atlas," "Sage"). The canvas manages window layout, workspace switching, and persistent agent state even when the app is closed.
2. On-Device Voice Control: The system uses the Parakeet speech recognition engine to transcribe voice commands entirely on the user's Mac. This enables instant, private, and unlimited command input via a global keyboard shortcut (⌥⌘). Commands include spawning new agents, directing specific agents by name, switching workspaces, and interrupting tasks.
3. Integrated Git Worktree Management: For each spawned agent, Zoku can automatically create and manage an isolated Git worktree based on a named branch. This ensures code changes from parallel agents are kept separate and do not overwrite each other, providing a version-controlled sandbox for each AI assistant.
4. Agent-to-Agent Orchestration: Zoku facilitates direct communication between agents. For example, a Claude agent can spawn a Codex agent to review its plan, wait for the result, and then process the feedback. This automates complex workflows without requiring the developer to act as an intermediary.
5. Status Awareness & Notifications: The environment provides clear, real-time status for each agent (e.g., "Working," "Done," "Needs you"). Notifications are delivered via system chime, spoken agent name, and a macOS Dynamic Island (notch) marker, ensuring developers are alerted to agent state changes even when the Zoku window is not in focus.

Problems Solved

1. Pain Point: Serialized AI Workflow Bottleneck. Developers are limited to interacting with one AI agent at a time, creating a queue of ideas and tasks. This serial process drastically slows down development cycles and parallel problem-solving.
2. Pain Point: Context Switching and Tab Overload. Manually managing multiple terminals, IDE tabs, and AI chat interfaces is distracting and error-prone. Developers waste time hunting for the correct tab and lose mental context when redirecting an agent.
3. Target Audience: Senior Full-Stack Developers and Tech Leads who utilize multiple AI coding tools (Claude, Cursor, GPT Engineer) and need to parallelize complex feature development, debugging, and code review. Solo Founders and Indie Hackers building products rapidly who need to maximize their AI-assisted output without managing infrastructure.
4. Use Cases: Parallel Feature Development: Spawning separate agents to simultaneously work on an API endpoint, frontend component, and database schema. Competitive Code Review: Having Claude, Codex, and Cursor analyze the same pull request from different perspectives concurrently. Rapid Prototyping: Using voice commands to iteratively steer multiple agents through a complex, multi-step build process without touching the keyboard.

Unique Advantages

1. Differentiation: Unlike monolithic AI IDEs or single-agent plugins, Zoku is an agnostic orchestration platform. It does not provide its own AI model or lock users into a specific ecosystem. It leverages the user's existing subscriptions (Claude Pro, Cursor Pro, OpenAI) and local CLIs, putting the developer in control of costs and model choice.
2. Key Innovation: The combination of on-device, name-based voice control with persistent multi-terminal management. The technical integration of system-level accessibility APIs for global voice capture, coupled with a stateful canvas that maintains live CLI sessions, creates a seamless "voice-as-interface" layer for agentic development that is both private and instantaneous.

Frequently Asked Questions (FAQ)

1. Does HeyZoku (Zoku) require an internet connection or API keys to run the coding agents? No. Zoku itself runs locally on your Mac. It launches the coding agent CLIs (like Claude Code or Cursor) that are already installed on your system. You use your own existing subscriptions and API keys directly with those services; Zoku does not meter tokens or act as a middleman. Your code never leaves your machine for the core orchestration functions.
2. What are the system requirements for the Zoku voice-first dev environment? Zoku requires macOS 14 (Sonoma) or later. The on-device voice transcription feature, which provides instant and private command processing, requires a Mac with Apple Silicon (M1, M2, M3, or later). The app will request Microphone and Accessibility permissions upon first launch to enable the global voice shortcut.
3. Is Zoku a subscription service, and what does the one-time purchase include? Zoku is a one-time purchase of $49 (early access price, regularly $100). This grants a lifetime license for the application on every Mac you own, including all future updates. The optional "Cloud" component for the AI companion (with memory and web app integration) is a separate monthly credit system that can be added or canceled without affecting your core license.
4. Can I use Zoku with AI coding agents other than Claude, Codex, and Cursor? Yes. While Claude, Codex (via ais.cx), Cursor, and Pi are pre-configured, Zoku allows you to add any command-line AI agent. You simply provide the launch command, define the spoken trigger words to spawn it, and specify the interrupt key, integrating it fully into the voice-controlled canvas.
5. How does Zoku handle code conflicts when running multiple agents simultaneously? Zoku mitigates conflicts through automatic Git worktree management. When you instruct an agent to work on a specific branch name, Zoku handles the underlying git worktree commands, creating an isolated directory for that agent's changes. This keeps each agent's modifications separate from the main branch and from each other.