acryl

ACRYL — the development environment your agents live in

ACRYL is a living Agentic Development Environment and runtime for your agents — infinitely adaptive to you, yours to shape, extend and grow into any workflow, any idea, from the inside out, where everything is a plugin. Bring any coding agent, it plugs in as a replaceable worker, and every decision, diff, and session survives the swap.

⭐ Star ACRYL · Website · Documentation · Download v0.2.6 · Discord [!IMPORTANT] ACRYL is in active early development. Interfaces, workflows, and packaging may change while the first public foundation is established. Why ACRYL?

You don't use one coding agent anymore. You use Claude Code for this, Codex for that, a terminal agent for the quick fix — and every switch costs you the context, the setup, and the thread of the work.

ACRYL flips the relationship. Instead of your project living inside one agent's chat, agents live inside your project:

Claude Code, Codex, OpenCode, Pi, Gemini CLI, DeepSeek Harness agents, ACP-compatible agents, plain PTY tools — even agents that don't know ACRYL exists. They are replaceable workers entering and leaving one persistent development scene. ACRYL owns the workspace, the context, the tasks, and the handoffs. What you get

🖼️ A real canvas, not a chat window. Projects and git worktrees on the left, a tabbed canvas in the middle: agent sessions, native terminals, a file editor, diffs with line-by-line review comments you can send straight back to the agent, a draggable kanban for your notes, docs, and checks. Panes are tiles — open, close, and arrange the environment around the work.

🤖 Every agent, one roster. A built-in catalog of 33 coding agents you can launch into any project, plus your own custom agent definitions. An attention queue tells you the moment an agent needs you (Claude Code hooks ship today), so you can run several and stop babysitting terminals.

🎮 Agents that can drive the app. Agent Control gives the agent inside ACRYL computer-use-style command of ACRYL itself: it reads the accessibility tree, clicks, types, opens panels, enables or disables plugins — every mutating action approved by you per call, recorded in an audit log, stoppable with one key. From the outside, the same power in your terminal: acryl control drives a running app, and acryl doctor / acryl repair diagnose and fix an install that won't boot, with backups and undo.

🧩 Everything is a plugin — really. Built on Cordis, the meta-framework of spatiotemporal composability. Install and hot-reload plugins live across all three surfaces without restarting. Plugins can contribute their own canvas tab types, tools, slots, and services. Browse the ecosystem at cordisplugins.github.io.

🥤 Blends: whole setups, shareable. A Blend is a complete, pullable composition of plugins — an entire opinionated environment as one unit. ACRYL itself is just one Blend, the maxed-out one. Yours can be another. See acrylblends.github.io.

🖥️ Three surfaces, one brain. Desktop (Electron), local Web (acryl web), and the terminal UI are peers rendering the same runtime — same project model, same plugins, same capabilities. Use whichever fits the moment; the work is the same. Install ACRYL v0.2.6

The three surfaces are deliberately separate installs — installing one never silently installs or starts another. Desktop GUI The Desktop app carries the runtime it needs; it does not add acryl to your PATH or leave a web server running after exit. CLI terminal