product

Install Manifoldone

Sign in, Connect this machine, done — the canonical path. Anonymous curl works too as a fallback.

Manifoldone ships as a Tauri 2 desktop app for macOS, Linux, and Windows. The canonical install path is sign in → Connect this machine from the dashboard — that gives you a personalized installer with a connect-intent token baked in, so the machine is docked the moment the script finishes. The anonymous curl one-liner is kept as a fallback for headless boxes and people who want to read the script first.

The canonical path

  1. Open app.manifoldone.com and sign in.
  2. Click Connect this machine — this docks the box and opens a Feed (one Node + one working directory) on a project.
  3. Pick either the personalized one-liner or, if the desktop app is already installed, the manifoldone:// deeplink. Both paths bake the connect-intent token into the install so you skip the manual connect-code dance.

Anonymous fallback

curl -fsSL https://manifoldone.com/install.sh | sh

Read the installer first — it’s plain bash, no jq dependency, and exits cleanly if there’s no release published yet. Without a token in the URL it installs the app + CLI but does not dock the machine; you finish connecting from the dashboard afterwards via manifoldone dock --code XXXXXX, which opens the Feed.

What this installs

  • Manifoldone.app in /Applications — the desktop shell with Welcome → Login → Projects → Board → Connect flows, system tray, and native notifications. The app also registers the manifoldone:// URI scheme — clicking Connect this machine in the web dashboard opens this app and auto-pairs (Plan 9.A).
  • manifoldone CLI symlinked to /usr/local/bin/manifoldone — the same binary the desktop app uses, surfaced for power-users + scripting. Installed on first launch (or via Settings → CLI in your $PATH).
  • Auto-update — the app checks manifoldone.com/releases/desktop/manifest.json on launch and prompts you when a new version ships. Updates are signed; we never apply an unsigned bundle.

Headless / CI

For CI runners and headless boxes the dashboard surfaces a separate cli.sh one-liner that downloads only the standalone manifoldone Node binary and ends in manifoldone dock --token … — so the box is connected before the user’s shell prompt returns. Same connect-intent token mechanic, no desktop app.

Linux & Windows

Linux .deb / .rpm / .AppImage and Windows .msi ship in v0.6. The installer prints a friendly notice on those platforms — you’ll build from source until the bundles land.

Uninstall

rm -rf /Applications/Manifoldone.app
rm /usr/local/bin/manifoldone
rm -rf ~/.manifoldone

Verifying signatures

Production releases are signed with an Apple Developer ID + an Ed25519 key for the auto-updater. During the v0.5 ramp the bundle is unsigned, so macOS will warn you on first launch. Allow it via System Settings → Privacy & Security → Allow Anyway. Production code-signing lands once the Apple Developer ID is provisioned.