Arachne

Arachne: an agent built to finish the job — not just suggest it

Most agents stop at a plan or a diff and hand the real work back to you. Arachne opens the shells, drives its own browser, writes the tools it is missing, argues its plan past a panel of models, and keeps proof of what it did. Here is what is under the hood.

One CLI, many hands

Arachne runs from a single command line that opens and coordinates several shells at once. A real task rarely fits in one terminal — so it doesn't force it to. It fans the work across parallel shells and keeps them in sync, so a build, a test run, and a deploy can move together instead of one after another.

Eyes without eyes

It browses the web through its own headless browser, reading the page's structure directly instead of squinting at screenshots. No pixel-guessing, no brittle vision — it sees the DOM the way the page is actually built. That makes it fast, precise, and far harder to fool than an agent that navigates by looking at images.

It writes its own tools

When Arachne hits a task it doesn't have a tool for, it writes one, installs it, and keeps going. The toolbox grows to fit the job instead of the job shrinking to fit the toolbox. Every self-made tool is inspectable and revocable — nothing runs that you can't see.

A war room, not a single opinion

Before it commits to a plan, Arachne can convene a panel: several models debate the approach, a red team attacks it, a judge weighs the arguments, and a vote settles it. You get a decision that survived scrutiny — not the first thing that came to mind. When the stakes are low it moves fast; when they're high it argues with itself first.

Safe by construction

Every action passes a preview first — blast radius, dry run, sandbox — so you can see what it will touch before it touches anything. It runs under policy, can be locked to read-only, and everything is reversible: a full timeline, rollback, undo, even per-step time travel. And it keeps visual proof-of-work of what it actually did, so "done" is something you can verify, not just a claim.

It speaks MCP

Arachne exposes and consumes MCP, so it plugs into your stack and orchestrates other tools and agents instead of living on an island. It's built to be the hands that drive everything else, not one more thing you have to babysit.

The challenge

Don't take our word for any of this. There's a live arena where Arachne takes real tasks from real people, in the open — the messy migration, the multi-step research, the build that always breaks. Bring the thing you're sure an agent can't do and try to stump it. Then tell us where it cracked. That's the feedback we're actually here for.

Early access — for developers

Arachne is in private beta, and we're opening it to a first group of developers. If you build things and want to put it through its paces, email me directly at [email protected] and tell me where to activate your membership — no forms, no waitlist. Windows & macOS, in beta.

Request developer accessMeet Arachne →

— Abdulelah, Nourva