Zest

Product Introduction

1. Definition: Zest is a context-aware, AI-powered developer productivity tool for macOS. Technically, it is a system-wide hotkey application that overlays a radial menu (the "Liquid Glass" wheel) directly at the user's cursor, enabling rapid task delegation to AI coding assistants or local shell commands.
2. Core Value Proposition: It exists to eliminate context-switching and streamline the developer workflow by providing a single, instantaneous interface (⌥ Space) to execute common project tasks—from AI-assisted code generation to running terminal commands—without leaving the current coding environment. Its primary keywords are: macOS developer tool, AI coding workflow, radial menu for devs, local AI agent runner, git worktree automation.

Main Features

1. The Liquid Glass Radial Menu: The core UI is a circular, context-sensitive menu that appears at the cursor upon holding ⌥ Space. Users "flick" their cursor toward a visual slice to select a command. This design enables near-instant, mouse-driven command execution without precise clicking, significantly reducing interaction time compared to traditional keyboard shortcuts or CLI recall.
2. Multi-Agent Task Delegation: Zest acts as a unified dispatcher for multiple AI coding assistants and local tools. It can hand off tasks defined in a slice to Claude Code, Codex, Gemini CLI, or any shell command. It uses the local installation and API keys of these agents, ensuring code never leaves the user's machine.
3. Project-Specific & Version-Controlled Configuration: Workflows are defined in a .zest.yml file placed in a project repository. This YAML file configures custom wheels, slices, agents, and prompts using placeholders like {selection}, {screenshot}, or {ask}. Committing this file shares the standardized workflow across an entire development team.
4. Isolated Git Worktree Execution: A critical technical feature is the optional worktree: true parameter. When set, Zest creates a dedicated Git worktree on a new branch for the agent to operate within. This isolates changes from the main working directory. Developers can then review the diff, merge it cleanly, or discard ("yeet") it without polluting their primary checkout.
5. Screenshot & Context Integration: Slices can be configured to capture the current window ({screenshot}) and attach it to the prompt sent to an AI agent. This enables use cases like "fix what I see," where a visual bug can be described contextually to the AI alongside the code.

Problems Solved

1. Pain Point: Fragmented and disruptive developer workflows. Constantly switching between IDE, terminal, browser (for AI tools), and Git CLI breaks focus and slows down development cycles.
2. Target Audience: Software engineers and developers on macOS, particularly those integrating AI pair programmers (Claude, Codex) into their daily work. It also appeals to tech leads seeking to standardize team workflows and solo developers/indie hackers prioritizing speed and context preservation.
3. Use Cases:
   • AI-Powered Code Reviews: A "vibe check" slice sends the current diff to Claude for instant analysis.
   • Context-Aware Bug Fixes: A "fix what I see" slice captures a screenshot and the relevant code, sending both to Codex for a suggested fix.
   • Safe AI Experimentation: Running a speculative AI refactor in an isolated Git worktree, reviewing the diff, and merging only if satisfactory.
   • Project-Specific Scripts: Creating custom wheels for a Node.js project with slices to "start dev server," "run tests," and "deploy to staging" via local shell commands.

Unique Advantages

1. Strengths & Limitations (Pros & Cons):

   • Pros:
     • Unparalleled Workflow Speed: The radial menu interaction is faster than searching through command palettes or recalling shell commands.
     • Local & Private: All execution happens locally using user-configured agents; no code or data is sent to Zest's servers.
     • Team Scalability: Version-controlled .zest.yml files ensure consistent tooling across engineering teams.
     • Risk Mitigation: Git worktree isolation prevents AI agents from corrupting the main codebase.
     • One-Time Purchase: Lifetime license for version 1.x, contrasting with the SaaS subscription model prevalent in dev tools.
   • Cons:
     • Platform Lock-in: Exclusively for macOS 26+, excluding Windows, Linux, and web-based developers.
     • Agent Dependency: Requires pre-installation and configuration of third-party AI CLI tools (Claude Code, etc.), adding setup overhead.
     • Learning Curve: Defining effective YAML configurations and prompts requires technical understanding.
     • Distribution: Not available on the Mac App Store due to sandboxing limitations, requiring direct download.

2. Key Alternatives & Differentiation:

   • IDE-Specific AI Plugins (e.g., GitHub Copilot, Cursor): These are deeply integrated into the editor but are typically limited to that single IDE and focused on inline code completion. Zest differentiates by being editor-agnostic, system-wide, and capable of orchestrating broader workflows involving shell commands, screenshots, and Git operations.
   • Traditional CLI Tools & Shell Aliases: While powerful, they require memorization, lack a unified visual interface, and do not natively integrate AI context or screenshot capture. Zest provides a discoverable, visual layer on top of these commands with enhanced context-passing abilities.
   • Raycast/Slack/Alfred Scripts: These are general-purpose launchers that can run scripts. Zest differentiates with its specialized, developer-centric radial menu UI, built-in concepts of AI agents and Git worktrees, and project-specific configuration files designed explicitly for coding workflows.

Frequently Asked Questions (FAQ)

1. Is Zest a subscription service? No, Zest is a one-time purchase license. The $19 launch price grants a lifetime license for all 1.x updates, with no recurring subscription fees.
2. Does Zest send my code to its own servers? No. Zest operates entirely locally on your Mac. It acts as a dispatcher, routing tasks to your locally installed AI agents (Claude Code, Codex) or shell. Your code, prompts, and API keys never pass through Zest's infrastructure.
3. Why is Zest not available on the Mac App Store? Apple's App Store sandbox restricts applications from launching other local tools and accessing certain system functionalities. Since Zest's core function is to launch external AI agents and terminals, it cannot operate within the sandbox and is distributed directly as a signed and notarized macOS application.
4. Can Zest be used for non-programming tasks? While optimized for software development, its ability to run any shell command via the radial menu makes it adaptable for other automated tasks. However, its feature set (Git worktrees, AI code agents, context placeholders) is specifically tailored for developer use cases.
5. How does Zest handle potential mistakes made by AI agents? The integration with Git worktrees is the primary safety mechanism. You can configure any slice to run in an isolated worktree. The AI's changes are contained there, allowing you to review a clean diff before deciding to merge, amend, or discard them entirely, protecting your main branch.