Make.com VS Crystl.dev

Crystl.dev's answer:

Crystl makes the workspace itself transparent i(n more ways then one). Every command, tool output, and message contains agent readable metadata. So Agent A, B, and C can coordinate, chat, and see what everyone else is doing. Assign an orchestrator agent and they can run the whole show, across multiple projects and code bases.

What actually backs that up? Well, I asked Claude while running in crystl and this is what it said:

The CLI is aimed at the agent, not the human. This is the real differentiator. From inside a shard I can read another agent's screen, type into it, approve its pending tool calls, inspect its transcript and token cost, spawn new workers, and block on bridge events over SSE. Competitors give the human a dashboard over their agents. Crystl gives the agent an API over the workspace. That inverts who does the coordinating.

Proof from thirty seconds ago: you asked me a question about Crystl and I answered it by calling crystl docs — the product documented itself to an agent running inside it, with no browser and no human step.

It solves the failure mode that kills fan-out in practice. Workers stop on approval prompts and go silent. Silence reads as "done." Everyone who has run parallel agents has been burned by this. Crystl classifies that state (⏸ awaiting input), pushes it over the event stream, and gives both the human and the orchestrating agent a way to unblock it.

That's not a feature-list item, it's evidence someone ran this at scale and got hurt.

The RPG layer is an org chart, not a theme. This gets dismissed as whimsy and it shouldn't be. Court is the example: the crown owns the conversation and owns no work, the hand orchestrates beneath it, officers hold standing remits — and agents are forbidden from messaging a crown. That's a real architectural constraint about who may interrupt whom.

"Crown / hand / officers" conveys the delegation shape instantly; "supervisor / worker /pool" doesn't. Naming multi-agent topologies in vocabulary people already have intuitions for is a genuine design idea.

The agent is made responsible for your ergonomics. crystl copy so you never drag-select a wrapped terminal line. crystl card for honestly attributed notifications on desktop and phone. crystl markdown show to surface a file in your editor instead of dumping it. crystl screenshots --last N so "the screenshot I just took" resolves to a path. Most tools optimize the agent's convenience. This optimizes the human's hands.

Agent-agnostic by design, with a real bet inside it. Heroes ask for a model size, not a model id, and you teach the mapping once. That's a deliberate wager that the agent-CLI and model-id landscape churns faster than anyone's config should. It ages well by refusing to hardcode.

Shared state lives in plain files. WORKBENCH.md is markdown at the project root, live-rendered to a panel, read and written by both you and every agent. No proprietary task database. It survives the tool — which is a trust argument as much as a technical one.

Crystl.dev's answer:

I loved running CLI agents in a terminal, but I hated that was so difficult to manage more than one. I kept ending up with a dozen terminal sessions, constantly typing into the wrong one, or playing messenger by copying and pasting info from one agent to another. I started by building the crystl rail, an agent notification system that allowed me to keep on top of approval requests, questions, and idle agents. Once I had a basic version of the app, I started using crystl to build crystl.

And now when users submit bugs they get delivered directly to agents in my cryst app in a git worktree. They start investigating and fixing the bugs when I'm not even there.

Who knows, maybe someday, cryst won't need me at all. :)

Crystl.dev's answer:

Most tools in this space let you watch your agents work. crystl lets your agents work with each other, and keeps you as the one who decides.

Three reasons:

It is a real terminal first. Every shard is a full terminal session, so git, npm, docker, and ssh all work normally. You are not locked into a purpose-built agent UI that you have to leave whenever you want to do ordinary command-line work.

It is native, not a web app in a window. crystl is a Swift macOS app with GPU-accelerated rendering built for keeping a fleet of noisy agent sessions light. Parallel agents produce a lot of output, and that is exactly where wrapped Electron terminals struggle.

The free tier is genuinely usable. Isolated worktree sessions, parallel agents, approval panels, the activity panel, history search, token tracking, the workbench, MCP management, and scheduling are all free. You can run the core multi-agent workflow without paying, and the Guild plan adds CLI orchestration and the phone app on top.

It also works with whatever agent you already use. Claude Code has the deepest integration and Codex supports hooks too, but any CLI agent runs in it.

Crystl.dev's answer:

Well, I'd like to think anyone could use crystl, developer or not. I think if you are using AI a CLI agent is the best agent.

This being said, crystl is development focused because developers are usually the ones most familiar with a terminal interface.

So, developers on macOS who already run CLI coding agents and have hit the ceiling of doing it in a normal terminal.

The core user right now is a solo developer or a small engineering team, usually one to ten people, running Claude Code, Codex, or a similar agent every day. They are past the experimentation stage. They run more than one agent at a time, they work across several repositories, and they have felt the specific pain crystl was built for: a dozen terminal tabs, typing into the wrong one, and copying context by hand from one agent to another.

A second group is anyone building agent workflows rather than just using them. Orchestration, fan-out, scheduled runs, and multi-agent topologies are first-class here, and the scriptable CLI means an agent can drive the workspace itself.

Crystl.dev's answer:

crystl is a native macOS application written in Swift. It is not a web app in a wrapper.

The terminal engine, Cavrn, is built specifically for multi-agent workflows and renders on the GPU with Metal, which keeps a fleet of busy agent sessions responsive. API keys are stored in the macOS Keychain.

Parallel agent sessions are backed by Git worktrees and branches, so several agents can work the same repository without colliding. Remote development runs over SSH. Agents connect to tooling through MCP (the Model Context Protocol), and the scriptable CLI talks to a local bridge that streams events over SSE.

The website runs on Cloudflare Pages.

Crystl.dev's answer:

Well, most of my customers so far are solo developers and small teams. I have had some corporate interest, I just don't have the time/money to pursue that unless they want to front the bill. I may build out some more scalable solutions for larger teams as things progress. We'll see.