Questions.

Is it free?

Yes. Wanigan is open source under the MIT license. Cloud agents use your own provider accounts; local models use a runtime on your Mac.

Can I download Rust Edition?

Not yet. The Rust rebuild is in progress. Follow its progress on the Build Board; this page will say when there is a verified release.

Does it edit my live (production) site?

No. Wanigan edits the local site you already run, with ddev, Lando or a dev script. It can show the same page on your hosted Dev, Test or Live, but only read-only: in a private session that shares no cookies with your local site, sending only requests that read, with no helper and no edits there. Your changes reach production the way they always have, through your own deploy.

Which Drupal and WordPress versions does it work with?

Drupal core 10.3 to 11.4. WordPress names no minimum: the helper was written against WordPress 7.1, and a few saves need a newer release (6.6 to read a block’s markup, 6.7 to write formatted words back, 6.9 to write one block alone), which says so when it refuses. The details.

What about page builders?

On Drupal, Wanigan saves an inline block’s words through its Layout Builder layout, and a paragraph’s through the page that holds it. On WordPress, blocks and patterns are core’s; Elementor’s pages are saved through Elementor’s own save, and ACF’s fields through ACF. Other builders’ own layouts are refused, saying so. Adapters.

Where do my edits go, and can I undo them?

Into Wanigan’s design layer first: the page shows them, the site doesn’t have them, and each can be undone, redone or discarded. Make it real saves words into the site, with a revision where the site keeps one; a value with no revision, such as a custom field, can be put back with Undo for ten minutes. The design layer.

What is the helper, and is it safe?

A small Drupal module or WordPress must-use plugin that lets Wanigan see what made each part and save through core. It is written into your local site only when you install it, after showing exactly what it writes and runs; git never sees it, and it comes out on your click. It acts only for requests carrying the key Wanigan keeps, which only the live view sends: every other visitor gets the page exactly as core makes it. The helper.

Do I need Claude Code or Codex, an account, or to pay anything?

No Wanigan account, and nothing to pay: it’s free. Editing your site needs no agent at all. To hand work to an agent you need Claude Code, Codex or Gemini CLI installed and signed in; Wanigan runs them as you, on the plans you already have. The demo needs none of them.

Does anything leave my computer?

Only what you ask for. Update checks use GitHub; Jev uses TypeSafe when configured; voice input downloads its speech model from Hugging Face once, when you ask, and never sends your voice. Optional Phone access uses your Tailscale network, and enabled phone notifications send encrypted payloads through the browser’s push service. Agents use their configured cloud or local backends, and requested model downloads use LM Studio. See What leaves your Mac.

Which agents does it run?

Claude Code, Codex, Gemini CLI and a plain shell. Supported local models run through Claude Code or Codex. Codex’s usage limit has not yet been seen from a real account, and Gemini CLI has not yet run a real model turn here. Replying from Needs you works for Claude Code and Gemini CLI, and for Codex once its own hooks have reported.

Does it write anything into my repository?

Routine launches do not add harness configuration to your working files. Agents and actions you choose, such as project MCP settings, skill copying, setup commands and Git operations, can change repository files. Checkpoints live in Wanigan’s store; Git registers a card’s worktree in your repository.

What happens to running sessions if I close it or restart?

Closing the window: they keep running. Quitting Wanigan’s core: they end. Restarting or logging out of your Mac: they end. An ended Claude Code or Codex conversation can be resumed from History.

Is it safe to let agents run in it?

As safe as running them in your own terminal, and no safer: Wanigan doesn’t sandbox them. What it does add is under Security.

Windows?

Not yet. This beta is for macOS on Apple silicon. Much of it is written for Windows too, its keys among them, but it has not been tested there.

Is it ready for real work?

It’s a beta, and a work in progress. Every feature in the feature matrix names the test that proves it, but a lot has been seen working only on the demo and local sites, or against stand-ins. Use it on local sites under version control, and read what isn’t done yet.

How do I report a bug?

Open an issue on GitHub: say the platform and its version, the kind of part, and what Wanigan said, and never a private site’s address or content. A security problem goes privately, through the security policy.

Something wrong or missing? Tell us