Wayland: The AI Agent Orchestrator Built on IonUI
Wayland is a local-first desktop agent that coordinates Claude Code, CodeX, Open Claw, Hermes Agent, and 12+ other CLI tools from one command center, with self-assembling teams, persistent memory, and workflow automation. It's built on IonUI's Apache-licensed codebase with substantial additions in Rust, shipping fast but still early-stage with unsigned installers and a growing issue list.
What Wayland Actually Is
Local-first command center for AI agents
Wayland runs entirely on your machine, keeping files and keys local while acting as a unified control point for multiple AI CLI tools you already use. It perceives your request and project state, reasons about the best approach, acts through sandboxed tools, and evolves by rewriting its own skill prompts against an evaluation system.
Coordinates 16+ separate agent CLIs
Through the Agent Client Protocol (ACP), Wayland launches and drives external tools like Claude Code, CodeX, Open Claw, Hermes Agent, Cursor Agent, GitHub Copilot, and 10 others, each keeping their own subscription while Wayland orchestrates them as one team with shared memory.
Co-work: multi-week project continuity
Instead of answering one question at a time, Wayland handles entire jobs from rough idea to finished result, maintaining state across files, running plans, and persistent memory that survives app restarts, keeping the full arc of work in context.
The IonUI Foundation
Built on IonUI, disclosed in footer
Wayland's codebase is forked from IonUI (built by iOffice.ai) under the permissive Apache 2.0 license, a fact stated at the bottom of Wayland's website but not prominently marketed. IonUI already supported 20+ CLI tools, multi-platform (Windows/macOS/Linux), and had real adoption before Wayland rebranded it.
Apache 2.0 allows commercial forks
The license explicitly permits taking the code, building commercial products, modifying it, and shipping under a different name as long as license terms are followed and the relationship is not misrepresented. Wayland discloses the IonUI origin but does not emphasize it in marketing.
What Wayland Built On Top
Wayland Core: 47MB Rust binary
A single self-contained engine requiring no separate Node or Python runtimes, powering both CLI and desktop app through one codebase. All tool calls pass through OS-level sandboxing (Landlock on Linux, Sandbox Exec on macOS, App Container on Windows) to contain blast radius if something goes wrong.
Self-assembling team system
Instead of coaching one chatbot, you hand a goal to a manager agent that assembles specialist agents, assigns them to a shared blackboard, and keeps them working until the job finishes. Teams can be standing (recurring work) or ad hoc (single push), disbanding once done.
1,900+ curated skills library
Pre-built, audited capabilities that load only when needed, preventing context window bloat. Paired with 100+ ready-to-run workflows (launch plans, competitor teardowns, content calendars) and dozens of pre-built assistants for research, writing, sales, operations, and strategy.
Cognitive memory: five SQLite partitions
Working memory (current task), episodic memory (recent events), semantic memory (general knowledge), procedural memory (preferred methods), and a personal model of you (your preferences). These exist across session, project, and global tiers, creating a living wiki rather than scratch files that reset.
Constitution file: personal governance rules
Write plain-English rules on your machine covering coding standards, tone, and forbidden behaviors. Wayland prepends these rules to every agent turn, with optional overrides for specific specialists when needed.
MCP marketplace: 100+ integrations
Browse and connect curated integrations in clicks, or paste any Model Context Protocol server URL. Recent updates flow these tools directly into Claude Code and Codex chats, not just Wayland's built-in sessions.
25 messaging channels for async work
Kick off tasks and receive results over Telegram, Slack, Discord, WhatsApp, Signal, SMS, iMessage, Microsoft Teams, email, and others. Lets you drive agents from anywhere while your machine works in background.
Cloud self-host: three commands
Install package, run setup with provider key, run start to print QR code and admin login. Designed for affordable VPS kept private behind Tailscale rather than exposed publicly, enabling 24/7 always-on agent work.
Flux Router: intelligent model routing
Optional layer that sends each task to the best-fit model across providers, runs multi-AI cross-audit (multiple models review same work), and fails over to different providers if one goes down without losing context.
Offline voice, image generation, runaway safety
Bundled Whisper for hands-free dictation (no voice sent anywhere), built-in image generation in chat, and a budget gate plus loop detector to stop sessions before they spiral or burn through usage budget.
Project Momentum and Maturity
Sustained growth: hundreds of stars in 2 weeks
Repository climbed steadily rather than spiking once, suggesting real adoption rather than viral hype. Backed by near-weekly releases on two parallel tracks (desktop app and Wayland Core engine).
Recent releases: marketplace, image gen, failover, safety
Latest desktop update added MCP marketplace, image generation in chat, circuit breaker for runaway sessions, and one-click failover. Previous release added X sign-in, browser tabs, and safety classifier for catastrophic commands.
Engine track: two-way messaging and security patches
Core releases added incoming message support across Telegram, Discord, Slack, WhatsApp, Teams, and patched a real cryptography vulnerability transparently and quickly.
Rough edges: unsigned installers, growing issues
macOS build not notarized by Apple (triggers security warning on first launch), Windows installer not code-signed (SmartScreen warning). Open issues accumulating quickly for a young project, normal for fast-moving tools but signals early-stage status.
AGPLv3 license: network services must share changes
Unlike IonUI's permissive Apache license, Wayland's AGPLv3 requires publishing modified source code if you build a network service others connect to over the internet. Does not restrict private use or commercial services, only closed-source hosted forks.
Comparisons to Related Tools
Wayland vs IonUI: orchestration depth vs instant setup
IonUI works immediately with just an API key and includes its own complete agent engine. Wayland leans on external CLIs and adds heavier orchestration (teams, workflows, skills, memory partitions, constitution). Neither strictly better; depends on whether you want instant simplicity or deeper coordination.
Wayland vs Paperclip: operations manager vs company
Paperclip models an entire organization with org charts, CEO agent, departments, budgets, and approval gates; agents run on heartbeats and triggers. Wayland is real-time chat-first, you actively drive work turn by turn. Paperclip manages the organization; Wayland is the operations manager.
Wayland vs Open Web UI: agent orchestration vs chat interface
Open Web UI is a self-hosted privacy-focused chat interface connecting to any model (local or cloud), with massive adoption and enterprise features. It does not autonomously act on files or drive other CLIs. Wayland is agent orchestration; Open Web UI is chat. Different categories solving different problems.
Who Should Use Wayland Now vs Wait
Best fit: juggling 3+ AI coding tools
If you already run Claude Code, CodeX, Open Claw, and Hermes Agent in separate windows with no awareness of each other, Wayland solves the real pain of disconnected tools by offering shared memory, one assignment point, and intelligent routing to the best agent per task.
Good fit: power users wanting deep orchestration
Self-assembling teams, persistent cognitive memory, personal constitution files, and 1,900+ pre-built skills are valuable if you want orchestration depth without building it yourself. Meaningful head start over building from scratch.
Good fit: always-on private agent on VPS
Three-command self-host setup on affordable VPS kept private behind Tailscale makes 24/7 agent work practical without renting expensive enterprise platforms.
Wait if: IT policies require signed/notarized code
Unsigned Windows installer and unnotarized macOS build will trigger security warnings and fail managed work machine policies. Not a blocker for personal use but friction for enterprise environments.
Wait if: you want simplest possible setup
IonUI itself, working immediately with just an API key and no external CLI tools required, may serve you better than Wayland's heavier orchestration layer if minimalism is your priority.
Wait if: you need battle-tested production track record
Wayland simply has not been around long enough to claim thorough production testing, no matter how fast it ships. Fair to treat as promising to watch rather than bet your entire workflow on overnight.
Final Verdict
Legitimate, fast-moving, feature-dense but young
Wayland is shipping real updates on two tracks at hard-to-ignore pace, including actual security fixes. Growth appears to track real usage rather than hype. Unsigned installers, climbing issues, and lack of long-term production proof mean treat as promising to watch closely rather than bet everything on immediately.
Three key takeaways
First: Wayland is a local-first agent orchestrator for Claude Code, CodeX, Open Claw, Hermes Agent, and 12+ others, wrapped in self-assembling teams, workflows, skills, and deep memory. Second: built on IonUI's Apache codebase, disclosed quietly in footer. Third: occupies different lane than Paperclip's company-style orchestration and chat-focused tools like Open Web UI.
Notable quotes
Your CLIs are brilliant strangers who never met. Each one forgets everything between sessions. — Wayland's positioning
Built on IonUI, licensed under Apache 2.0. — Wayland website footer
Wayland is not vaporware. It is not an abandoned weekend project, either. — Host analysis