Key takeaways
- Rebranded as 'The Agentic Developer Environment' (ADE) and open-sourced in March 2026 — the Rust codebase is on GitHub with 83 stars as of June 2026
- Supports Claude Code, Codex, Cursor Agent, and OpenCode in parallel sessions with an attention queue, checkpoints, and built-in Git panel and SQL Studio
- Free desktop app today; a $20/mo Premium tier (cloud agents, Linear integration, mobile) is announced but not yet shipped
FAQ
What is Acepe?
Acepe is an open-source Mac desktop client — self-described as 'The Agentic Developer Environment' — that provides a unified interface for ACP-compatible AI coding agents like Claude Code, Codex, Cursor Agent, and OpenCode.
What agents does Acepe support?
Acepe supports Claude Code, Codex, Cursor Agent, and OpenCode side by side; any agent that runs in a terminal can also work in Acepe.
Is Acepe free?
Yes, the desktop app is free and open source with unlimited local agent sessions. A $20/mo Premium tier with cloud agents and mobile access is announced as 'coming soon.' You pay your agent providers (Anthropic, OpenAI) directly.
Executive Summary
Acepe is a Mac desktop client — now branded "The Agentic Developer Environment" (ADE) — that provides a unified interface for AI coding agents implementing the Agent Client Protocol (ACP). Rather than switching between different terminal windows or apps for each agent, developers use Acepe as a single workspace for Claude Code, Codex, Cursor Agent, and OpenCode, running them in parallel with checkpoints, an attention queue, and built-in Git and SQL tooling. Since this profile's original publication, the project open-sourced its Rust codebase (March 2026) and has shipped steadily, with eight GitHub releases through v2026.5.17 (May 17, 2026) and commits as recent as June 8, 2026.
| Attribute | Value |
|---|---|
| Company | Independent (indie developer project) |
| Founded | 2026 |
| Funding | Not publicly disclosed |
| Employees | Unknown (appears solo/small) |
| 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. Releases through mid-2026 added an attention queue that triages sessions by urgency, file-level checkpoints with revert ("time-travel debugging"), a built-in Git panel and diff viewer, a SQL Studio, kanban and by-project views, and unified skill management synced across agents.
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, with attention-queue triage |
| Plan Mode Rendering | Clean markdown with copy/download/preview |
| Checkpoints | Snapshot every tool run; revert a file or session |
| Built-in Tooling | Git panel, diff viewer, SQL Studio |
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 (Linux "next," Windows "after that" per the official FAQ ) |
| Protocol | Agent Client Protocol (ACP) |
| Agents Supported | Claude Code, Codex, Cursor Agent, OpenCode |
| Open Source | Yes — Rust codebase at github.com/flazouh/acepe, open-sourced March 2026 |
| Privacy | Runs locally; the app does not send code anywhere itself |
Adoption
As of June 2026, the GitHub repository (created March 22, 2026) has 83 stars and 7 forks, with eight releases shipped between April 6 and May 17, 2026 (latest: v2026.5.17) and the most recent push on June 8, 2026.
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
- Open source — Full Rust codebase published on GitHub in March 2026; inspectable, forkable, and runs entirely locally
Cautions
- Modest traction — Open source since March 2026 but only 83 GitHub stars and 7 forks as of June 2026; releases paused after v2026.5.17 (May 17), though commits continued into June
- Mac-only — Linux and Windows are roadmap items, not shipped
- Depends on ACP adoption — Value proposition tied to ACP ecosystem growth
- Indie project — Appears to be a solo/small developer effort with no disclosed funding; the GitHub license is non-standard ("Other"), so verify terms before forking
- Premium tier unshipped — The $20/mo cloud-agents tier is "coming soon," so monetization is unproven
What Developers Say
As of June 11, 2026, there is no substantive community discussion of Acepe to report: a Hacker News search turns up no submissions or comment threads about the product, and no Reddit discussion surfaced in web searches either. For an open-source tool launched in early 2026, that silence is consistent with its modest GitHub traction (83 stars) — and is itself a signal that adoption remains too small to have generated independent developer commentary.
Pricing & Licensing
| Tier | Price | Includes |
|---|---|---|
| Free | $0 | Unlimited local agent sessions, multi-agent support, session history, checkpoints, SQL Studio, Git integration |
| Premium | $20/mo (announced, "coming soon") | Cloud agents on remote machines, Linear integration, mobile app, session sync, priority support |
| Enterprise | Custom | SSO/SAML, dedicated cloud infrastructure, audit logs, SLAs |
Pricing as of June 2026.
Licensing model: Free open-source app; works with existing Claude Code/Cursor subscriptions (BYOK or picks up existing agent authentication)
Hidden costs: You pay agent providers (Anthropic, OpenAI, etc.) directly for API or subscription access
Competitive Positioning
Direct Competitors
Acepe's own pricing page now positions it against Superset, 1Code, T3 Code, and Conductor.
| Competitor | Differentiation |
|---|---|
| Conductor | Conductor emphasizes Mac-native Claude Code/Codex workspaces with worktrees; Acepe claims broader agent coverage, an attention queue, and SQL Studio |
| Superset | Superset is terminal-first with isolated worktrees; Acepe leans into the operator layer (triage, checkpoints, built-in tools) |
| 1Code | 1Code focuses on Claude Code/Codex with kanban and browser previews; Acepe differentiates on built-in agent breadth |
| 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 open-source interface with checkpoints and session triage
- Choose Conductor when: You want a polished Mac-native workspace centered on Claude Code/Codex with worktree isolation
- Choose Superset when: You prefer a terminal-first parallel-agent workflow
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 | Not publicly disclosed; free product, paid tier unshipped |
| Market Position | Niche (ACP-focused), in a crowded Mac agent-client field |
| Innovation Pace | Active — open-sourced March 2026, eight releases through May 2026, commits into June 2026 |
| Community/Ecosystem | Small (83 GitHub stars, 7 forks as of June 2026) |
| Long-term Outlook | Tied to ACP adoption and indie sustainability |
Acepe is alive and actively developed as of June 2026: the site is live with a rebrand to "The Agentic Developer Environment," the codebase was open-sourced in March 2026, and the repo shows commits as recent as June 8, 2026. Its value proposition remains tied to the Agent Client Protocol; as ACP gains adoption through JetBrains, Zed, and others, Acepe could carve out a position as an open-source multi-agent workspace for Mac developers — but traction is still small and it competes with better-funded entrants like Conductor.
Bottom Line
Acepe is an early-stage but actively developed open-source product targeting developers who use multiple AI coding agents and want a unified, keyboard-driven interface. Since February 2026 it has rebranded as "The Agentic Developer Environment," open-sourced its Rust codebase, shipped eight releases, and added checkpoints, an attention queue, Git/SQL tooling, and a roadmap toward a $20/mo cloud tier — but community traction remains small (83 GitHub stars as of June 2026).
Recommended for: Developers using multiple ACP-compatible agents who want an open-source, inspectable alternative to terminal juggling
Not recommended for: Teams needing shipped enterprise features today, Windows/Linux users, or those preferring IDE-integrated experiences
Outlook: Alive and shipping, but an indie project with modest adoption in a fast-churn category; viability depends on ACP ecosystem growth, Premium-tier monetization landing, and competition from better-funded apps like Conductor and from agent providers building their own clients
Research by Ry Walker Research • methodology