Wiki3 App

Wiki3 App is a desktop application (Tauri 2) for running Wiki3.ai sites. It presents a dashboard of wikis, where each wiki is a loose collection of up to three independent properties:

• a local git working copy,
• a remote git repository (for example GitHub),
• a site URL (for example GitHub Pages).

Any one of the three is enough to create an entry; the others can be attached later. The app also provides Open, Run, and Publish flows built on the JupyterLab / JupyterLite platform, with desktop permission gating and persistent local state.

Why it is on our list

• It makes git-backed publishing a GUI. Local checkout, remote, and live URL are visible per site, which is the mental model most people are missing.
• Explicit permission gating. Enabling execution in a wiki requires an explicit allow-once / allow-always / deny decision rather than implicit trust.
• Origin allowlisting. Trusted origins are verified (wiki3.ai, *.github.io, plus user-registered site URLs).
• It is the tool behind our own publishing pattern: Markdown in Git plus a generated site.

Install and first run

1. Download or build the app from https://github.com/wiki3-ai/wiki3-app.
2. Launch it; the dashboard seeds two wikis (wiki3-ai/wiki3-ai-site and wiki3-ai/wiki3-ai-template).
3. Add a wiki by giving any one of local path, remote URL, or site URL.
4. Use the per-wiki Local / Remote / Site links to reveal files, open the repository, or open the site in an in-app window.

Configuration worth knowing

• wikis.json holds dashboard entries; a legacy workspaces.json is migrated once on first run.
• Window state is persisted: open site windows are restored on next launch, with per-wiki close-all / reopen-all supported.
• GitHub publishing uses a token stored in the OS keychain with a file fallback, and supports GitHub Pages publishing via gh-pages or a docs folder.

Common pitfalls

• Licence expectations. AGPL-3.0 is a strong copyleft licence. If you plan to redistribute a modified version or run it as a network service, read the licence rather than assuming "open source = do anything".
• Deleting a seeded wiki. It does not come back on its own; use "Restore defaults".
• Trusting arbitrary origins. The allowlist is a safety feature; adding a random site URL to it undermines it.
• Assuming cross-platform parity. The README's overview describes the macOS app specifically; treat other platforms as unproven until you test them yourself.
• Token handling. Publish tokens belong in the keychain, not in a project file you might commit.

Tips and tricks

• Keep one wiki per site. Cramming several unrelated repositories into one dashboard entry makes the Local/Remote/Site mapping meaningless.
• Use the in-app Site window for quick previews, but verify the deployed URL in a normal browser — an in-app webview can cache aggressively.
• This app is a good concrete example of the wiki pattern described in Publishing content and Deploy your own wiki.

Videos

No video specifically covering Wiki3 App was verified as of 2026-10-28. Rather than link something adjacent and call it a match, this page deliberately has none. The nearest useful general material is the dev-container and devcontainer guides linked from Hermes devcontainer.

Related

• Hermes devcontainer — from the same organisation.
• Publishing content — the workflow this app implements.
• Deploy your own wiki.

Verification note: features, stack, seeded wikis, and publishing details were read from the repository README on 2026-10-28; licence from the repository LICENSE file (AGPL-3.0). The README describes the macOS app, so platform claims beyond macOS are marked as unproven.