Key takeaways
- First Mac client built specifically for the Agent Client Protocol (ACP) standard
- Supports Claude Code, Codex, Cursor Agent, and OpenCode in a single interface
- Keyboard-first design with ⌘K command palette and native macOS feel
FAQ
What is Acepe?
Acepe is a native Mac desktop client that provides a unified interface for interacting with ACP-compatible AI coding agents like Claude Code, Codex, and OpenCode.
What agents does Acepe support?
Acepe supports Claude Code, Codex, Cursor Agent, OpenCode, and any other ACP-compatible agent.
Is Acepe free?
Yes, Acepe is free to download and use. You pay your agent providers (Anthropic, OpenAI) directly for API usage.
Executive Summary
Acepe is a native Mac desktop client designed to provide a unified interface for interacting with AI coding agents that implement the Agent Client Protocol (ACP). Rather than switching between different terminal windows or apps for each agent, developers can use Acepe as a single pane of glass for Claude Code, Codex, Cursor Agent, and OpenCode.
| Attribute | Value |
|---|---|
| Company | Independent |
| Founded | 2026 |
| Funding | Unknown |
| Employees | Unknown |
| Headquarters | Unknown |
Product Overview
Acepe solves the fragmentation problem that developers face when using multiple AI coding agents. The Agent Client Protocol (ACP), developed by Zed Industries, standardizes communication between code editors and coding agents. Acepe builds on this standard to provide a clean, native Mac experience for agent interaction.
The app renders agent plan mode outputs as clean markdown instead of terminal walls of text, indexes session history across projects for searchability, and enables running multiple agents in parallel panels.
Key Capabilities
| Capability | Description |
|---|---|
| ACP Support | Native support for any ACP-compatible agent |
| Multi-Agent | Switch between agents with ⌘L |
| Session History | Indexes all sessions, searchable and filterable |
| Parallel Sessions | Run multiple agents side by side |
| Plan Mode Rendering | Clean markdown with copy/download/preview |
Product Surfaces
| Surface | Description | Availability |
|---|---|---|
| macOS App | Native desktop client | GA |
Technical Architecture
Acepe communicates with agent CLIs via the Agent Client Protocol, a standardized protocol that allows editors to connect to any compliant agent without vendor lock-in. ACP has been adopted by JetBrains AI Assistant and is supported by the AI SDK.
Key Technical Details
| Aspect | Detail |
|---|---|
| Deployment | Local Mac app |
| Protocol | Agent Client Protocol (ACP) |
| Agents Supported | Claude Code, Codex, Cursor Agent, OpenCode |
| Open Source | No |
Strengths
- Protocol-native — Built specifically for ACP, ensuring compatibility with any compliant agent as the ecosystem grows
- Keyboard-first — ⌘K command palette, ⌘L agent switch, ⌘/ model change, ⌘N new thread; designed for developers who minimize mouse usage
- Session management — Unlike CLIs, Acepe indexes all sessions across projects with search and filtering
- Clean rendering — Plan mode outputs rendered as readable markdown instead of raw terminal text
- No vendor lock-in — Works with multiple agents simultaneously; switch based on task requirements
Cautions
- Early stage — New product with limited track record and community feedback
- Mac-only — No Windows or Linux support currently available
- Depends on ACP adoption — Value proposition tied to ACP ecosystem growth
- Unknown company — Limited information about the team and company behind the product
- Feature depth unclear — Marketing focuses on UX; unclear how advanced features compare to native agent apps
Pricing & Licensing
| Tier | Price | Includes |
|---|---|---|
| Free | $0 | Full app functionality |
Licensing model: Free app; BYOK (bring your own key) for agent providers
Hidden costs: You pay agent providers (Anthropic, OpenAI, etc.) directly for API or subscription access
Competitive Positioning
Direct Competitors
| Competitor | Differentiation |
|---|---|
| Agentastic | Acepe focuses on ACP protocol vs Agentastic's terminal-first approach with Ghostty |
| Commander AI | Acepe supports more agents; Commander is SwiftUI-native but fewer protocols |
| Codex App | Acepe is agent-agnostic; Codex App is OpenAI-specific |
When to Choose Acepe Over Alternatives
- Choose Acepe when: You use multiple ACP-compatible agents and want a single interface
- Choose Agentastic when: You need terminal access, worktrees, and agentic code review
- Choose Commander AI when: You want the most polished native Mac UI for a single agent
Ideal Customer Profile
Best fit:
- Developers using multiple AI coding agents who want a unified interface
- Power users who value keyboard-driven workflows
- Early adopters interested in the ACP standard
Poor fit:
- Teams needing enterprise features or team collaboration
- Developers who prefer embedded IDE experiences
- Users requiring Windows or Linux support
Viability Assessment
| Factor | Assessment |
|---|---|
| Financial Health | Unknown |
| Market Position | Niche (ACP-focused) |
| Innovation Pace | Unknown |
| Community/Ecosystem | Limited |
| Long-term Outlook | Tied to ACP adoption |
Acepe's value proposition is directly tied to the success of the Agent Client Protocol. As ACP gains adoption through JetBrains, Zed, and other tools, Acepe could become the default multi-agent interface for Mac developers.
Bottom Line
Acepe is an early-stage product targeting developers who use multiple AI coding agents and want a unified, keyboard-driven interface. Its bet on the Agent Client Protocol standard could pay off as the ecosystem matures.
Recommended for: Developers using multiple ACP-compatible agents who want a cleaner interface than terminal juggling
Not recommended for: Teams needing enterprise features, Windows/Linux users, or those preferring IDE-integrated experiences
Outlook: Promising concept, but success depends on ACP ecosystem growth and competition from agent providers building their own apps
Research by Ry Walker Research • methodology