Key takeaways
- Development stalled: rapid daily releases ended March 16, 2026; last feature commit April 14, only dependency bumps since — evaluate with that risk in mind
- Expanded beyond a desktop app into a shared-daemon workspace: native app, web UI, CLI, and MCP server, with issue-driven worktrees from GitHub/GitLab
- Embedded PTY terminals per worktree, PR inspection with review comments, and live agent activity tracking for Claude Code, Codex, and OpenCode
FAQ
What is Arbor?
Arbor is a Rust-powered native workspace for agentic coding — a desktop app, web UI, CLI, and MCP server sharing one daemon — with issue-driven git worktrees, embedded terminals, PR inspection, and agent activity tracking.
How much does Arbor cost?
Free and open source under the MIT license. Install via Homebrew or build from source.
Is Arbor still maintained?
Unclear. Releases ran daily through March 16, 2026, but the last feature commit landed April 14, 2026, with only automated dependency updates since. The repo is not archived, but momentum has stalled as of June 2026.
Who competes with Arbor?
Aizen (native Swift worktree manager), Emdash (GUI with issue trackers), and dmux (tmux-based worktrees). For full orchestration, Tembo.
Does Arbor support remote development?
Yes — the shared daemon can run remotely with web UI access, and Arbor supports remote outposts over SSH and mosh, making it one of the few tools in this category with remote support.
Executive Summary
Status note (June 11, 2026): Arbor is alive but development has stalled. After daily releases through March 16, 2026, the last feature commit landed April 14, 2026; only automated dependency bumps have merged since.[1][2]
Arbor grew from a desktop worktree manager into a Rust-powered native workspace for agentic coding — a desktop app, web UI, CLI, and MCP server sharing one daemon — with issue-driven worktrees, embedded terminals, PR inspection, and agent activity tracking.[3] Its standout features are remote daemon/outpost support and worktrees derived directly from GitHub and GitLab issues.
| Attribute | Value |
|---|---|
| Company | Independent (penso) |
| Founded | 2026 (created March 4) |
| Funding | Not publicly disclosed (solo open-source project) |
| Headquarters | Unknown |
| GitHub Stars | ~751 (as of June 2026) |
Product Overview
Arbor combines git worktree management with embedded terminals and AI agent monitoring around a shared daemon that serves a native desktop app, web UI, CLI, and MCP server.[4] Each worktree gets its own daemon-backed PTY terminal, and the app tracks live working/waiting status for Claude Code, Codex, and OpenCode.
The March 2026 release run added issue-driven worktrees — derive branches directly from GitHub and GitLab issues with repo-aware branch prefixes — plus PR inspection with native review comments and Procfile/arbor.toml process supervision.[3] The remote story remains differentiated: run the daemon remotely with web UI access, or manage remote worktrees over SSH and mosh.
Key Capabilities
| Capability | Description |
|---|---|
| Git Worktree Control | Create, preview, clean up worktrees; derive from GitHub/GitLab issues |
| Embedded Terminals | Daemon-backed PTY terminals per worktree with attach/detach |
| Process Management | Supervise Procfile and arbor.toml processes per worktree |
| Diff & PR Inspection | Side-by-side diffs, PR summaries, native review comments |
| AI Agent Activity | Live working/waiting status for Claude Code, Codex, OpenCode |
| Remote Daemon/Outposts | Remote daemon with web UI access; SSH and mosh support |
| Configurable UI | 25+ themes, terminal backends, notifications via config.toml |
Product Surfaces
| Surface | Description | Availability |
|---|---|---|
| macOS App | Native desktop app via Homebrew | GA |
| Web UI | Browser access to a (local or remote) daemon | GA |
| CLI | Worktree and daemon control from the shell | GA |
| MCP Server | Expose Arbor to MCP-capable agents | GA |
| Build from Source | Rust/just build system | GA |
Technical Architecture
Arbor is built in Rust with a native UI layer and a shared daemon that backs the desktop app, web UI, CLI, and MCP server.[4] The daemon manages terminal sessions, supervised processes, and agent status, surviving app restarts — and can run on a remote host.
Key Technical Details
| Aspect | Detail |
|---|---|
| Deployment | macOS app (Homebrew) or build from source |
| Runtime | Rust, native UI |
| Model(s) | None — tracks Claude Code, Codex, OpenCode status |
| Integrations | Git, GitHub/GitLab issues and PRs, SSH, mosh, MCP |
| Open Source | Yes (MIT) |
Strengths
- Remote daemon and outposts — Rare in this category: run the daemon remotely with web UI access, or manage remote worktrees over SSH/mosh[5]
- Issue-driven worktrees — Derive worktrees directly from GitHub/GitLab issues with repo-aware branch prefixes[3]
- Rust performance — Native binary, fast startup, low memory usage
- Persistent daemon — One daemon backs the app, web UI, CLI, and MCP server; attach/detach terminals like tmux
- Diff and PR aware — Side-by-side diffs, PR summaries, and native review comments without leaving worktree context
- MIT license — Most permissive option; no AGPL or commercial restrictions
Cautions
- Stalled momentum — Daily releases ended March 16, 2026; the last feature commit landed April 14, with only automated dependency bumps merged since[1][2]
- Solo developer — No team, company, or funding behind the project; bus factor of one
- Limited agent support — Only tracks Claude Code, Codex, and OpenCode; no broader agent discovery
- macOS focus — Homebrew install is macOS; cross-platform builds require manual setup
- Small community — ~751 stars and 3 watchers as of June 2026; essentially no public discussion or third-party validation[4]
What Developers Say
As of June 11, 2026, there is no substantive public discussion of Arbor to quote — searches of Hacker News (zero matching stories or comments for the project) and Reddit turned up no reviews or user threads. The project's visibility is limited to its GitHub repository and website; its ~751 stars have not yet translated into community commentary.[4]
Pricing & Licensing
| Tier | Price | Includes |
|---|---|---|
| Open Source | Free | Full functionality |
Licensing model: MIT — free for commercial and personal use.
Competitive Positioning
Direct Competitors
| Competitor | Differentiation |
|---|---|
| Aizen | Native Swift worktree manager — Arbor has remote outpost support, Aizen has libghostty rendering |
| Emdash | GUI with 20+ agents and issue trackers — Arbor is lighter, has remote support |
| dmux | tmux-based worktrees — Arbor has a GUI and remote outposts |
| Tembo | Full orchestration — Arbor is individual developer tooling |
When to Choose Arbor Over Alternatives
- Choose Arbor when: You manage worktrees across local and remote machines
- Choose Aizen when: You want native Swift performance with libghostty terminals
- Choose Emdash when: You want issue tracker integration and 20+ agent support
Ideal Customer Profile
Best fit:
- Developers working across local and remote machines who need worktree management
- Rust enthusiasts who appreciate native performance
- Solo developers wanting a simple, MIT-licensed worktree manager
Poor fit:
- Teams needing enterprise features or wide agent support
- Developers wanting cloud execution or background agents
- Anyone needing issue tracker integration
Viability Assessment
| Factor | Assessment |
|---|---|
| Financial Health | Unknown — solo open-source project, funding not publicly disclosed |
| Market Position | Early — niche entrant with no public community traction |
| Innovation Pace | Stalled — daily releases through March 16, 2026, then last feature commit April 14; only dependency bumps since[1] |
| Community/Ecosystem | Small — ~751 stars (up from ~295 in March), but no public discussion |
| Long-term Outlook | Uncertain — strong technical foundation, but the two-month feature freeze raises abandonment risk |
Bottom Line
Arbor packed an impressive amount into its first six weeks — a shared-daemon architecture spanning desktop app, web UI, CLI, and MCP server, plus issue-driven worktrees and remote outposts that remain genuinely differentiated in this category. But the release cadence stopped on March 16, 2026, and feature commits stopped April 14; as of June 2026 only automated dependency updates are landing. With a solo developer and no community, that silence matters.
Recommended for: Experimentation by developers who want native worktree management with remote daemon support and accept the MIT-licensed code as-is.
Not recommended for: Production workflows, teams, or anyone who needs an actively maintained tool with broad agent support.
Outlook: The Rust foundation and remote-first design are still the best in this niche, but unless commits resume, Arbor is on the path many fast-churn agent-app projects take — a brilliant sprint followed by quiet abandonment. Watch the commit log before adopting.
Research by Ry Walker Research • methodology