Honest status

Honesty is the point of this page. Each line says what was actually seen working, and how, so you can tell what has been shown from what has only been built.

Every feature and rule Wanigan claims has a row in its feature matrix: the claim, the test that proves it, and a status. The statuses mean:

A stand-in is a made-up program or answer that takes the real one’s place in a test: a pretend claude, codex, gh, ddev or Tailscale that answers the way the real one does, a pretend Drupal or WordPress built from classes in the shape of core’s, a pretend model provider answering on the same computer, or a pretend page. Stand-ins let the tests run on any machine without touching your accounts, spending from a plan or opening a real site.

The demo inside the app, Help › Open the Demo, is something else again: sample projects and stand-in agents in a data folder of their own, where nothing real is touched and no model is called. The demo sites are the two made-up websites above.

This beta is for the core workflow: project boards, real terminal sessions, saved work and Needs you. Its rules live in Wanigan’s core, not in the window, and each is proven by tests against a real core.

Every row, with the test that proves it, is in the feature matrix.

These are in the app and pass their tests, but have not all been seen against the real thing they depend on: a running site, a signed-in agent, a real phone or a real microphone.

• Serve this card: switching which checkout ddev serves.
• A component’s props form.
• Canvas pieces by their own ids.
• Pictures, adding and taking out as edits in the design layer: for now those are done directly on the page.
• In the code editor: creating, renaming or deleting files, searching the contents of every file, language servers, and two files side by side.
• Grok Build as an agent: its hook events are translated and tested, waiting for it to be installed and seen running.
• A signed feed that would bring adapter fixes between releases: an open decision.

These were seen in the real app, driven by a script, on Northstar and Fieldnotes. The sources record them on no other site yet.

• Words made real and verified: a product title on Northstar.
• The component library and its pictures: Northstar’s 73 entries and Fieldnotes’ 166, each pictured at exact sizes in hidden windows and kept for the next time it is asked.
• Where an entry is used across the site: on Northstar, the theme’s components found in the templates that use them; on Fieldnotes, a button style found in nineteen places through synced patterns and a template part. Each search took 5 to 270 ms.
• Taking a placed item out, and Undo: a block placement switched off on Northstar and put back; on Fieldnotes, a block taken out of a page as a new revision, and out of a template after its question, each put back.
• Part identity: 318 of 394 parts named on Northstar and 164 of 165 on Fieldnotes, the same after a reload, and a moved menu link keeping its identity.
• A site helper set up by another Wanigan, which answers only to that one, and says so.
• What WordPress core’s AI Client and the Abilities API did during a save, on Fieldnotes: nothing, since no site here has a provider connected.

Each says what happens, what to do in the meantime, and which kind of edge it is. Not done yet is Wanigan’s to do. Core keeps no such thing belongs to the site’s platform, and Wanigan says so when it refuses.

• Not done yet

  Verify checks the old address after a save moves the page

  When saving words gives the page a new address, as a new title does on a Drupal site that makes addresses from titles with Pathauto, the view goes to the new address. The edit still remembers the old one: Verify renders the old address, which may now answer “not found” or a redirect, and Edits lists the edit under the old page.

  Meanwhile: Look at the page at its new address yourself, with the eye in the toolbar to see it without the layer. Do not rely on Verify’s verdict for that edit.

• Not done yet

  Edits does not show what a stored-words save said, or its Undo

  When words are saved where the content keeps them (a page builder’s, a shortcode’s or a custom field’s), Wanigan reads the reloaded page back, notes which adapter saved them and whether that plugin version is verified, and keeps a way back for ten minutes, the only one for a custom field, which keeps no revision. The Edits panel shows none of that yet: only that the words were saved, with the revision when there is one.

  Meanwhile: Look at the reloaded page and run Verify. To put the old words back, use the site’s own editor: the edit in Edits still shows them as its old value.

• Not done yet

  Adapters are verified on one release each, and no watch checks new ones yet

  Each adapter’s verified range is the single plugin release whose source it was written from. The weekly compatibility watch that would check every new plugin release is not built yet. On a newer release an adapter is marked unverified and still saves, or refuses by name if something it calls is gone; the window does not show the unverified mark yet.

  Meanwhile: After a plugin update, look at the page after each save and run Verify. If an adapter refuses, see adapters, and tell us the plugin and its version.

• Not done yet

  The shortcut sheet lists two code-editor keys wrongly for Windows and Linux

  Off a Mac, the sheet lists Ctrl+G for Go to a line, but the editor’s key there is Ctrl+Alt+G, and Ctrl+G finds the next match instead. It lists Ctrl+- and Ctrl+Shift+- for Back and Forward, but the editor uses Alt+← and Alt+→, as its breadcrumbs say. This site’s keyboard shortcuts page is made from the same sheet, so it shows the same two.

  Meanwhile: On Windows and Linux, use Ctrl+Alt+G, and Alt+← and Alt+→ or the mouse’s back and forward buttons. The Mac keys are right.

• Not done yet

  Two tours name the wrong key or the wrong place

  The tour of a session says On a Mac, ⌘⇧M·; on Windows and Linux, Ctrl+Shift+M moves between the message box and the terminal; that key now starts voice input, and the move is On a Mac, ⌘⇧E·; on Windows and Linux, Ctrl+Shift+E. The welcome tour says List is under ···; List is now the board’s other mode, switched from the board’s toolbar.

  Meanwhile: Press On a Mac, ⌘⇧E·; on Windows and Linux, Ctrl+Shift+E to move between the message box and the terminal. Open List from the board’s toolbar, or with G then L. Tours explains the rest.

• Not done yet

  Verify sees a change that leaked past your edit only with the page from before

  Verify compares the page with and without the layer, then the rest of the page with the page as Wanigan kept it just before the edit was made real; no platform’s core keeps that page for configuration or code. A change the site made beyond the edited elements shows in both of today’s renders, so only the page from before reveals it. Where there is none (the edit was made real in a template or by an agent, another edit was made real on that page since, or the page could not be rendered then), the rest of the page is compared with the design only, and the verdict says step 3 did not run, and why.

  Meanwhile: Verify each edit before making the next one on the same page real. When a verdict says step 3 did not run, look over the rest of the page yourself, with and without the layer.

• Not done yet

  The message box waits for an agent’s first turn

  Codex reports nothing until its first turn begins, so its message box refuses until then. Gemini CLI’s first screen may ask you to sign in or to trust the folder, so its message box works from the second message.

  Meanwhile: Answer startup questions and send the first message in the agent’s terminal, then use the message box.

• Not done yet

  A Codex session without its hooks misses limits, failures and Esc

  When Codex’s hooks are not trusted, Wanigan reads only Codex’s own notifications, which say a turn ended and never that one began. Such a session cannot find its own record, so a usage limit, a failed turn or Esc goes unseen, and it reads as working until its next prompt. Needs you cannot reply to it, and says so.

  Meanwhile: Answer it in its terminal. The session says why it started without its hooks.

• Not done yet

  A Codex conversation stays in the account it lives in

  Codex resumes a conversation only in its own account folder. When one Codex account hits its limit, its conversation cannot carry on under another account, as a Claude Code conversation can.

  Meanwhile: Wait for the reset Needs you shows, or start a new conversation on another account.

• Not done yet

  Codex asks before each wanigan command

  Codex’s sandbox does not let its agent reach Wanigan, so Codex asks you to approve each wanigan command the agent runs.

  Meanwhile: Approve each one as it asks. Widening Codex’s sandbox is your call, and Wanigan does not do it for you.

• Not done yet

  Gemini CLI’s usage limit is read from its screen

  Nothing Gemini reports carries its usage limit, so Wanigan reads the exact words of the dialog Gemini draws. If a Gemini release rewords that dialog, Wanigan misses the limit.

  Meanwhile: If a Gemini session stops with no reason given, look at its terminal.

• Not done yet

  What Wanigan keeps for undo and evidence is never cleared by itself

  Per-turn checkpoints, attachments and the records in Wanigan’s database are kept with no total limit, so its data folder grows as you work. Automatic deletion was left out on purpose: it would remove undo and evidence without a rule you can see.

  Meanwhile: Keep an eye on the size of ~/Library/Application Support/Wanigan 2/.

• Not done yet

  Updates are installed by hand, and the app is not notarized

  Wanigan checks GitHub for a newer version when you ask, or once a day after you say yes, but it does not install one. The build is ad-hoc signed and not notarized, so macOS asks for your approval the first time you open it.

  Meanwhile: When Settings › Updates offers a new version, download it, quit Wanigan, and drag the new one into Applications over the old. Your projects, boards and history stay.

• Core keeps no such thing

  Drupal’s next configuration import puts configuration words back

  A field’s label, a block’s title, the site’s name and slogan, a view’s words and a webform are configuration. Wanigan saves them through Drupal’s own API, but the next configuration import puts back whatever is exported, and each such save says so.

  Meanwhile: Export the site’s configuration after the save to keep the change.

• Core keeps no such thing

  WordPress keeps no id for a block

  Wanigan names a WordPress block by its place in the stored markup, with its words as a guard. An edit to one block that shows no words is kept only by that place, so after the blocks are reordered it lands on whichever block is there now. Wanigan marks such an edit Fragile before you make it.

  Meanwhile: Finish or discard a fragile edit before reordering the blocks on that page. A style for every block of its kind is kept by its name instead, so it is not fragile.

Behaviour that has been seen, or a question still open, with no known cause yet. Each is kept as it was seen, not explained away or hidden.

• Not understood yet

  A control crawl failure in CI that did not happen again locally

  In one release candidate’s CI run, the control crawl, which presses every reachable control in the demo, passed 1,436 checks and failed one: a criterion’s checkbox on a demo review card, where the browser driver timed out before it could click. An unchanged local crawl of the same screen, with one worker, passed all 39 of its controls, that checkbox included. It did not reproduce the failure or the load CI was under, and the cause is not known. An earlier CI run failed the same way on another click, and later runs passed.

  Meanwhile: Nothing changes in the app for it, and no fix is claimed. It is kept as an open risk in how the tests run.

• Not understood yet

  The test machine could not open a microphone

  Started by the testing agent, Wanigan could not open even Chromium’s pretend audio device: the request never settled, no permission request was logged, and its audio came out as silence. Headless Chromium on the same machine did not have that problem. So voice input has not yet heard a real microphone.

  Meanwhile: If the mic will not listen on your Mac, it says why and what to do, with a button to the system setting. If it still does not listen, tell us your macOS version and what the mic said.

• Not understood yet

  Whether a Codex conversation could move to another account

  A copy of a Codex conversation in another account loads its history without a model call, but leaves one conversation id in two accounts, which History refuses to choose between. Whether the second account accepts the first one’s encrypted reasoning is not known without spending a turn to find out.

  Meanwhile: Continue a Codex conversation in the account it lives in.

Wanigan is maintained by one person, its owner, who decides what is built next. The design notes record each decision with its date and the reason for it.

• The next release, beta.5, brings Studio, the new design for the whole app. Its plan ends with an independent review, whose findings are fixed before the release.
• Adapters are built in an order ranked by how many sites each reaches, and by risk.
• What has not been seen working stays on the source’s Not done yet list, and on this page, until it has been. The feature matrix changes with every feature added or changed.
• Bug reports with steps, and small, well-tested fixes, help most right now. For anything larger, an issue comes first, so the shape is agreed before anyone builds it.
• An open decision is said as one: a signed feed for adapter fixes between releases is the current example.

Found something that is not on this page, or something here that is wrong? Input goes to GitHub as an issue, and security problems go privately.

• Tell usOpen an issue for a bug, an idea or a site edit that went wrong, or report a security problem privately.