Honest status
Tell us
In short
This site has no forms and sends nothing to anyone else’s servers, so what you want to tell us goes to Wanigan’s repository on GitHub, as an issue anyone can read. Security problems, and anything you cannot describe without private details, go privately through the security policy instead.
On this page
Where your input goes
Wanigan’s website deliberately has no forms, sets no cookies and loads nothing from anyone else’s servers. So there is nowhere here to type a message: input goes to Wanigan’s repository on GitHub, as an issue. Issues are public, so read what you write before you send it.
Open an issue
Open the issue chooser
Go to the repository’s new issue page on GitHub, and sign in to GitHub if it asks.
Choose a template
Pick the one that fits: Bug for something that does not work as it should, or Idea for something Wanigan should do, or do differently. The chooser also offers a blank issue, and a link for a security problem. A third template, A site edit was refused or landed wrong, is in the next release’s source, and appears in the chooser once that release is published.
Fill it in
Each field says what belongs in it, and the ones the template needs are marked as required. What each template asks for is below.
Read it, then submit
Read it through once more for anything private, then submit it.
| Template | Use it when | It asks for |
|---|---|---|
| Bug | Something in Wanigan does not work as it should. | What happened; the steps to reproduce it, saying if it happens in the demo (Help › Open the Demo), which makes it much easier to fix; the Wanigan commit; your macOS version; your Claude Code and Codex versions, if a session is involved; the relevant lines of core.log. |
| Idea | Wanigan should do something, or do something differently. | The problem first: what gets in your way today, working with agents. Then what would help. |
| A site edit was refused or landed wrong | The live editor refused a change, saved it somewhere unexpected, or Verify disagreed with what you see. | The platform and its version, how the part is built, what Wanigan said or did, what you expected, Wanigan’s version, and any public plugins or modules involved. |
When a site fights you
Every site is built a different way, and each one that refuses an edit teaches the editor something. The site template asks for exactly what it takes to rebuild the problem somewhere else:
- The platform and its version: Drupal or WordPress, such as “Drupal 11.2” or “WordPress 6.8 with PHP 8.3”.
- How the part is built, in generic words: “a field on a node”, “a block placed in Layout Builder”, “a Paragraphs item”, “a block in a synced pattern”, “an Elementor widget”, “a menu link”.
- What Wanigan said or did: its words exactly as they appeared (a refusal says whether the site’s core keeps no such thing, or Wanigan does not do it yet), where the change went, or the Verify verdict.
- What you expected.
- Wanigan’s version, from Settings › Updates.
- The plugins or modules involved: public ones only, such as a page builder or a fields plugin, with their versions, if you think they matter.
The demo sites are two made-up sites, Northstar on Drupal and Fieldnotes on WordPress. scripts/demo-sites/build.sh all in the source builds them, with ddev and Docker.
Attaching a log
Wanigan writes two logs, core.log and core.out.log, in its data folder, ~/Library/Application Support/Wanigan 2/. They contain your project paths. Read the one you attach first, paste only the lines that matter, and take out anything you would rather not share, such as a folder named after a private site.
More fixes for common problems are in troubleshooting.
Security problems, and anything private
Never put a security problem in a public issue. Report it privately instead: only the maintainer sees it.
Open the security policy
Go to the repository’s security policy on GitHub.
Report a vulnerability
From the Security tab, choose Report a vulnerability.
Say how to see it
Give the steps to reproduce it, and your macOS, Claude Code and Codex versions.
Use the same private report for anything you cannot describe without private details, such as a problem you can show only on a client’s site.
Wanigan is in beta and maintained by one person. You’ll get a reply as soon as possible, and credit in the fix if you want it. Security and privacy says what Wanigan protects, and what it does not.
If you want to fix it
Bug reports with steps, and small, well-tested fixes, help most right now. For anything larger, open an issue first, so the shape is agreed before you build it. CONTRIBUTING.md in the source has the rules, among them that tests never touch your real machine, nothing spends tokens without a click, and no real site ever appears in the repository.