# Morpheus — full reference > Full-stack software, built by chat. Shipped from your pocket. Morpheus turns a phone into a complete software studio. Describe what you want in plain language; Morpheus writes the real code, builds the backend, compiles a native binary, and deploys it — no laptop, no lock-in, no illusions. You own every file. And here, done means verified — every check is proven to actually fail, the part the rest of the market hasn't built. We did. Beside it, in the same account, sits Jarvis: a personal assistant with his own long-term memory, a Command Deck for the rest of your life, and a dock you can put on a website you already run. Both are being built toward a digital possibility engine — everything you tell them, brought together, so it can surface opportunities and possibilities you had not seen. ## A digital possibility engine The destination rather than a shipped feature — and the reason Jarvis exists. Everything you tell Morpheus and Jarvis is kept, brought together, and read back so it can surface opportunities and possibilities you had not seen. Jarvis's suggestions is the first working piece of it: he reads across your own Command Deck unprompted and tells you what you may have missed, and switching that widget off stops it dead with no AI spend. ## What Morpheus does ### Chat-to-code Describe an app in a sentence; Morpheus writes production-ready frontend and backend code you can read, edit, and own. No pseudo-code, no placeholders. Workflow: Type your request in the chat bar → Morpheus plans the file structure → writes each file in full → runs a review pass → saves to the file tree. Tap REVERT beneath your message to undo that prompt. ### Autonomous build pipeline A self-correcting loop: compile → run → on failure, an AI agent reads the logs, writes a fix, and recompiles — only escalating to you when it's truly stuck. Workflow: Tap the bot icon in the chat bar → describe the full scope → watch the multi-step log in real time → STOP anytime. On a failed step it reads the error logs, writes a fix, and recompiles automatically. ### Verification — done means verified Most AI coding tools call a build done the moment the model stops typing. Morpheus doesn't. Its Valiant verification makes done mean verified: 130 automated guards assert real failure modes, the ones that can be proven are mutation-tested so each has been shown to actually fail, the merge gate is enforced by name so a skipped check is a fail, and the reviewer runs on a different model so it can never grade its own work. Workflow: Every build runs the full guard suite and the mutation proof before it's called done — a green result means the checks ran. The build's own record tells you exactly what was verified. ### One chat, every target Compile the same project to a web app, Windows EXE, macOS app, Linux binary, Android APK, iOS app, Python package, or Arduino firmware — all from your phone. Workflow: Pick a compile target in the toolbar → tap COMPILE → Morpheus pushes a GitHub Actions workflow → the build runs on a hosted runner → the artifact lands in _compiled/ ready to download. ### Audio plugins — a modelled amp, compiled for your machine Compile a real VST3, Audio Unit or CLAP plugin around a neural amp model and a cabinet impulse response, for macOS, Windows or 64-bit ARM Linux. The model is baked into the binary and played by the reference implementation of the format, so there is nothing to install beside it. The signal path — input trim, gate, three-band tone, the model, the cabinet — is measured against a reference on every build, and the build writes what it verified into your download. Workflow: Open a project → put your .nam in the file tree (models/ is searched first) → CABINET dialog to add a speaker impulse response if you have one → SIGNAL PATH to arrange the blocks and their order → set the target to audio-plugin-macos, audio-plugin-windows or audio-plugin-linux-arm → COMPILE → unzip _compiled/ and load the plugin in your DAW. BUILD-PROOF.txt beside it is the build's own record of what it checked. ### Bootable OS images Bake your app into a Raspberry Pi image or a full PC/server Linux distro (Debian/Ubuntu/Fedora) that boots and runs your software on first start. Customise hostname, timezone, locale, SSH, and packages at build time. Workflow: Open Distro Config → set hostname, timezone, locale, SSH keys, packages → COMPILE → flash the .img to an SD card with flash.sh, or push it to a remote device with flash-network.sh over SSH. ### Auto-generated backends Morpheus plans, writes, and deploys a backend (API, database, auth) for your app, then wires the frontend to it automatically. Workflow: Open the Architect → describe the API → Morpheus plans the schema and routes → generates the server code → deploy to a connected host → use Wire to Backend to point the frontend at the live URL. ### Marketplace Publish your project as a paid template; browse, buy, and install others' templates in one tap. Sellers get a cut, buyers get working code. Workflow: Finish a project → Marketplace panel → Publish tab → add icon, screenshots, description, price (min $0.50) → Publish. Buyers tap BUY → Stripe checkout → download the ZIP, or tap INSTALL to copy it into their workspace. ### Network flashing Push a finished OS image straight to a Pi or server over SSH — no SD-card swapping, no disk juggling. ### GitHub, end-to-end OAuth in, import existing repos, push new code, and trigger remote builds via GitHub Actions — your code lives in your own account. ### Live deploy with log-pulling Connect Cloudflare, Vercel, Supabase and others; Morpheus deploys and then pulls live logs back so you can watch it run. ### AI diagnosis When a build or deploy breaks, an AI agent analyses the real error logs and either auto-fixes or hands you a precise, actionable next step. ### Dependency sync One tap updates every dependency across npm, pip, Maven, Cargo, Go, Gem, Composer, Gradle, and PlatformIO — nested manifests included. ### Cost transparency Every AI action shows its estimated compute cost in USD up front, so you always know what you're spending. ### Perpetual project memory Every message you type and every file Morpheus writes is stored permanently with the construct. On each build, the full conversation history and the complete file tree are fed back in as context — so Morpheus never forgets a requirement, a decision, or a fix from earlier in the project. The more you tell him, the better he builds. Workflow: Just chat normally — every prompt is saved to the construct's permanent record. When you ask for the next change, Morpheus re-reads the entire history and all current files before building, so earlier decisions carry forward automatically. ### Searchable project history An important diagnostics tool. Every chat message, build log, tool action, diagnosis, and file snapshot is stored permanently and searchable end-to-end. When something breaks or a requirement drifts, search the full record to find exactly when, why, and what changed — no scrolling, no guessing. Workflow: Open the History panel → BUILD LOGS to search event details and tool names; SNAPSHOTS to find a saved state by label; CHAT to search every message Morpheus has ever written for this construct. Each tab shows a live match count and highlights results in context. ### Help mode Toggle it on and tap any feature; Morpheus explains what it does and how to use it, inline. ### Voice On demand, Morpheus speaks its replies aloud — for hands-free building on the go. ### Jarvis — the personal assistant Morpheus is the builder; Jarvis is the assistant — a second product in the same account, at /deck, with his own connections, his own long-term memory and his own chat history rather than a view onto Morpheus's. You talk or dictate freely and Jarvis splits what you said into separate thoughts, files each one where it belongs — a task, a strategy note, something worth keeping, or one of the five life streams (health, money, home, people, growth) — assigns the owner, and keeps your original words instead of replacing them with a summary. Ask him for a synthesis and he reasons across everything he has been told; turn on Voice and he reads the reply aloud as it is being written. Workflow: Open /deck → type or dictate into Brain dump, the capture box pinned to the top of the page → Jarvis separates the thoughts, assigns each to the right stream and the right person, and remembers all of it. Ask him anything in the Jarvis tab — every message is kept in his permanent history and read back to him as context. ### Command Deck — a dashboard for your own life Jarvis's home: a configurable dashboard at /deck with 15 widgets — the five life streams (health, money, home, people, growth), a task board, an inbox, a calendar, strategy, a signal chain and a knowledge base, with the brain-dump capture box pinned first and a permanent record behind every one. Each account sees only its own Deck, and which widgets appear, and in what order, is per account. Workflow: Open /deck → Deck Settings → Widgets to switch widgets on or off and reorder them. Jarvis's suggestions is also the per-account opt-out from proactive insight: switch it off and he stops reading across your Deck unprompted, and no AI credit is spent on it. ### Morpheus Dock — the plugin for a site you already run Put Morpheus on your own website. Mint a scoped widget token, paste one script tag, and the site gets the dock: the same chat, deploy, site-health, shop, pages, SEO and traffic panels, floating over your own pages. It renders inside a shadow root, so the host site's CSS cannot bleed in or out, and it passes the page you are looking at into the chat so answers can be grounded in what is on screen. The Morpheus WordPress plugin ships the same dock and also carries Morpheus's deploys onto the live site, signed with an HMAC the plugin verifies. Workflow: Project → WEBSITE panel → EMBED tab → create a token, ticking the scopes you want (chat, deploy, store, SEO, traffic; the secret is shown once and only its hash is stored) → copy the script tag onto the site, or use one-tap dock setup to push it to a connected WordPress site. The floating corner dock comes from data-dock="1"; without it the panel drops inline where the tag sits. Revoke a token at any time from the same list. ## Downloads Everything Morpheus hands you as a file, in one place. Most of what you make is deliberately not here: your builds land in your own project, in your own repository, in _compiled/ — which is the point. - **Portable Morpheus** (macOS · Windows · Linux) — The whole product — the builder and the Command Deck — running on your own machine. Your data stays with you, and nothing stops working if you stop paying. A ZIP of the product's own source, generated at build time from the repository. Published source, not open source — see the notice inside. - **The user manual** (Every target) — How to install and run what Morpheus builds, for every target it builds — including what each platform's unsigned-software warning means, and how to get past it. Generated at build time from the same module that writes USER-MANUAL.txt into every build, so the published manual cannot drift from the one a download carries. - **Audio plugin — demo builds** (Windows · Linux AArch64 · macOS on request) — A prebuilt plugin you can load in a DAW today: the project owner's own Marshall JCM 800 2203 captured in four states, through one Marshall G12M 4x12 captured with four mics, into a drive, a three-band tone stack, a delay and a spring reverb, in VST3, CLAP and a standalone app. Unsigned, so your platform will warn once. All four captures and all four cabinets are included, and you switch between them with the Capture and Speaker controls in the plugin's own panel or the host's parameter list. This is the demo rig and not the product — what Morpheus makes for you is a plugin built in your own repository around your own model and your own cabinet. - **Marketplace templates** (Any target) — Working projects other people have published — buy one or install it into your workspace in a tap, and read every file before you run it. Published by other users, not by us. Sellers get a cut. ### What you compile is not a download from us Every target compiles inside your own GitHub repository and its output lands in _compiled/ in your own project: an Android APK, an iOS app, a macOS app, a Windows EXE, a Linux binary, a Raspberry Pi image, a full Linux distro, a Python package, a web app, or a VST3 / Audio Unit / CLAP plugin. That is the difference between a download page and a build tool — the file is yours, in your account, from your source. ## Audio — your amp, in the box Morpheus builds real audio plugins around a neural amp model. Put a .nam model in the project, add a cabinet impulse response if you have one, pick the target for your machine and COMPILE — the build runs on a hosted runner, and the finished plugin lands in _compiled/ with a proof file the build itself wrote. The model is played by NeuralAmpModelerCore, the reference implementation of the format, and the signal path around it is a measured design rather than a sketch: input trim, gate, bass/mid/treble, the neural model, the cabinet, output. ### Three routes, each for one machine A plugin format exists on more than one platform, so a target that named only its formats would read as "builds for whatever you are on". Each route below is one machine and says so; a plugin compiled for the wrong one loads nowhere and explains nothing. - **audio-plugin-macos** — macOS only. VST3, Audio Unit, CLAP, and a standalone app. The only route that can produce an Audio Unit, because there is no AU outside Apple's platforms. - **audio-plugin-windows** — Windows only. VST3, CLAP, and a standalone app. No Audio Unit, and that is not an omission — it is what Windows hosts load. - **audio-plugin-linux-arm** — 64-bit ARM Linux only (a Raspberry Pi 4 or 5, for instance). VST3, CLAP, and a standalone app. A 64-bit ARM ELF, which is what a Raspberry Pi runs — not an x86 Linux binary. ### Using it 1. **Get a model** — A .nam file — train your own, or download one. Put it in the project: models/amp.nam is what the builder looks for first, and the compile panel tells you which file it found, or says there is none. 2. **Add a speaker** — Optional, but it matters: a modelled amp on its own sounds like a bee in a jar. Upload a cabinet impulse response as a .wav in the CABINET dialog and it is baked into the plugin — nothing to install beside it. Only the first 4096 samples are convolved, so a 48 kHz IR of roughly 85 ms is the whole of it. 3. **Arrange the signal path** — The COMPILE panel's SIGNAL PATH dialog is the plugin's own block diagram: the blocks in the order the audio runs, move one with the arrows, switch one off, set each control's default. Add a Drive — a clean path and a clipped path summed, so the harmonics arrive without the level moving — a Delay, or a Spring reverb, a tank of three springs whose controls set how long it rings and how dark it is. Anywhere in the path, before or after the amp model. It is saved into the project's morpheus.plugin.json, so the file says what the plugin does. Every block carries its own On/Off switch inside the plugin, beside its controls: a block switched off here is still built in and opens switched off, so it can be turned on while you play without a rebuild — and it keeps its control either way, because a host stores automation against a control's id. 4. **Pick your machine** — audio-plugin-macos, audio-plugin-windows or audio-plugin-linux-arm — whichever one you will actually open it on. They are not interchangeable. 5. **Compile and install** — COMPILE pushes the project to your own GitHub and runs the build there. When it finishes the plugin is in _compiled/ with BUILD-PROOF.txt beside it. Unzip, and put the VST3, AU or CLAP in your plugin folder; the standalone needs no installation at all. 6. **Play it** — The full signal path is six controls, all of them in your host's automation list: Input (±24 dB), Gate (off to 0 dB), Bass, Mid and Treble (±12 dB each) and Output — the count is whatever your signal path has, and the ids do not move when you rearrange it. The gate's bottom position is OFF rather than a very low threshold, so it is exactly transparent when you do not want it. ### What the build proves The proof is a measurement the build makes and writes down, not a claim. The plugin's own entry point and NeuralAmpModelerCore's own renderer were given the same dry signal from the same pinned commit and compared sample by sample: they agree to −144.0 dB on a 64-bit ARM runner. The chain around it was measured the same way — bass, mid and treble each inside 0.5 dB of the filter that designed them, the cabinet nulling to −147.5 dB against a direct convolution of its own impulse response, and the gate taking the quiet part 44.8 dB below the loud one. ### On the bench, not in the app yet - **A capture rig** — built and measured, in the repository rather than in the app. The awkward part of capturing an amp is not the recording, it is knowing whether the recording can be trained on. Morpheus can now fetch the re-amp signal the trainer accepts, check a recorded pair against the trainer's own rules before anyone spends an hour of GPU time — sample rate, length, whether the amp held still for the whole take, the delay it will be aligned at — and then measure the model that comes back against the recording. Today that is a command-line tool in the repository, not a panel in the app. - **A Raspberry Pi you plug in and play** — planned. The plugin above runs on a Pi. A bootable image that carries the plugin, the audio routing and the first-boot setup, controlled from your phone, is the next step — the image target exists, it is the audio host that does not yet. - **A practice amp with no operating system** — planned. The same model in a small microcontroller, for the cheapest and most deterministic tier: no OS, no buffering, fixed latency. - **Effects pedals and instruments that are programmable logic** — planned. Running quantized models on an FPGA. The open question is not whether a network fits — it is what low bit-widths cost the sound, and that gets measured before anything is bought. ## User manual The manual that ships with a build, for every target. Each section covers installing it, starting it, and the unsigned-software warnings that platform puts in your way. ### Web App Target id: `web-app` ============================ Your project — user manual ============================ What this is : a Web App build, compiled for you by Morpheus Generated : 2026-10-18 This file travelled with your download. It covers installing the app, starting it, and the things that platform does to unsigned software. It is written from what Morpheus knew at compile time — for what the app does once it is running, see the project's own notes at the bottom. INSTALLING IT (Web App) You downloaded a static web build (.zip). Unzip it and serve the folder — it is plain files. npx serve or upload the folder to any static host. STARTING IT Open the served address in a browser. IF IT WILL NOT OPEN, OR WILL NOT START A blank page with no errors is usually a build that expects to be served from the root of a domain. CONNECTING IT TO MORPHEUS Some compiled apps can sign in to Morpheus from inside the app, so the work they do is billed to your own account. That is a device login: the app shows a short code, you approve it in your browser on the Morpheus site, and the app picks up a token scoped to one capability. If the app has no such screen, it does not need one. -------------------------------------------------------------------------- THE PROJECT'S OWN NOTES (none shipped) -------------------------------------------------------------------------- This project did not ship a README, so there is nothing here to quote. Morpheus will not invent one: it has not read the app's interface, and a manual that describes menus that do not exist is worse than a short one. What the app does when you open it is the authority. -------------------------------------------------------------------------- End of manual. the app itself is the authority on what it does. ### Android APK Target id: `android-apk` ============================ Your project — user manual ============================ What this is : a Android APK build, compiled for you by Morpheus Generated : 2026-10-18 This file travelled with your download. It covers installing the app, starting it, and the things that platform does to unsigned software. It is written from what Morpheus knew at compile time — for what the app does once it is running, see the project's own notes at the bottom. INSTALLING IT (Android APK) You downloaded an Android .apk. 1. Copy it to the device (or open the download on the device itself). 2. Your browser or Files app will ask to install an unknown app — allow it for that app only. 3. Android will warn that it cannot check the app for harmful behaviour. That is Play Protect reacting to an unsigned build, not a finding about this app. STARTING IT Open it from the app drawer once installed. IF IT WILL NOT OPEN, OR WILL NOT START "App not installed" usually means an older build with a different signing key is already present — uninstall that first. CONNECTING IT TO MORPHEUS Some compiled apps can sign in to Morpheus from inside the app, so the work they do is billed to your own account. That is a device login: the app shows a short code, you approve it in your browser on the Morpheus site, and the app picks up a token scoped to one capability. If the app has no such screen, it does not need one. -------------------------------------------------------------------------- THE PROJECT'S OWN NOTES (none shipped) -------------------------------------------------------------------------- This project did not ship a README, so there is nothing here to quote. Morpheus will not invent one: it has not read the app's interface, and a manual that describes menus that do not exist is worse than a short one. What the app does when you open it is the authority. -------------------------------------------------------------------------- End of manual. the app itself is the authority on what it does. ### Python Package Target id: `python-package` ============================ Your project — user manual ============================ What this is : a Python Package build, compiled for you by Morpheus Generated : 2026-10-18 This file travelled with your download. It covers installing the app, starting it, and the things that platform does to unsigned software. It is written from what Morpheus knew at compile time — for what the app does once it is running, see the project's own notes at the bottom. INSTALLING IT (Python Package) You downloaded a Python package (a wheel or a source archive). pip install Then run the module or entry point the project documents. STARTING IT A virtual environment (python -m venv) is worth it if you do not want it system-wide. IF IT WILL NOT OPEN, OR WILL NOT START A failed install names the requirement it could not satisfy. CONNECTING IT TO MORPHEUS Some compiled apps can sign in to Morpheus from inside the app, so the work they do is billed to your own account. That is a device login: the app shows a short code, you approve it in your browser on the Morpheus site, and the app picks up a token scoped to one capability. If the app has no such screen, it does not need one. -------------------------------------------------------------------------- THE PROJECT'S OWN NOTES (none shipped) -------------------------------------------------------------------------- This project did not ship a README, so there is nothing here to quote. Morpheus will not invent one: it has not read the app's interface, and a manual that describes menus that do not exist is worse than a short one. What the app does when you open it is the authority. -------------------------------------------------------------------------- End of manual. the app itself is the authority on what it does. ### Windows EXE Target id: `windows-exe` ============================ Your project — user manual ============================ What this is : a Windows EXE build, compiled for you by Morpheus Generated : 2026-10-18 This file travelled with your download. It covers installing the app, starting it, and the things that platform does to unsigned software. It is written from what Morpheus knew at compile time — for what the app does once it is running, see the project's own notes at the bottom. INSTALLING IT (Windows EXE) You downloaded a .zip. Unzip it first — running an .exe from inside a zip does not work. Then double-click the .exe inside the extracted folder. STARTING IT Windows may show "Windows protected your PC" (SmartScreen). Choose "More info", then "Run anyway". This appears for any program that is not signed with a paid certificate. IF IT WILL NOT OPEN, OR WILL NOT START Nothing on screen after launching: this app may have been built without a console window, so it prints nothing and a crash is silent. Look for a log file next to the .exe or under %APPDATA%. CONNECTING IT TO MORPHEUS Some compiled apps can sign in to Morpheus from inside the app, so the work they do is billed to your own account. That is a device login: the app shows a short code, you approve it in your browser on the Morpheus site, and the app picks up a token scoped to one capability. If the app has no such screen, it does not need one. -------------------------------------------------------------------------- THE PROJECT'S OWN NOTES (none shipped) -------------------------------------------------------------------------- This project did not ship a README, so there is nothing here to quote. Morpheus will not invent one: it has not read the app's interface, and a manual that describes menus that do not exist is worse than a short one. What the app does when you open it is the authority. -------------------------------------------------------------------------- End of manual. the app itself is the authority on what it does. ### Linux Binary Target id: `linux-binary` ============================ Your project — user manual ============================ What this is : a Linux Binary build, compiled for you by Morpheus Generated : 2026-10-18 This file travelled with your download. It covers installing the app, starting it, and the things that platform does to unsigned software. It is written from what Morpheus knew at compile time — for what the app does once it is running, see the project's own notes at the bottom. INSTALLING IT (Linux Binary) You downloaded a .tar.gz. tar xzf .tar.gz chmod +x ./ STARTING IT If it exits at once, run it from a terminal so you can see why. IF IT WILL NOT OPEN, OR WILL NOT START A missing shared library names itself in the terminal output; install that package. CONNECTING IT TO MORPHEUS Some compiled apps can sign in to Morpheus from inside the app, so the work they do is billed to your own account. That is a device login: the app shows a short code, you approve it in your browser on the Morpheus site, and the app picks up a token scoped to one capability. If the app has no such screen, it does not need one. -------------------------------------------------------------------------- THE PROJECT'S OWN NOTES (none shipped) -------------------------------------------------------------------------- This project did not ship a README, so there is nothing here to quote. Morpheus will not invent one: it has not read the app's interface, and a manual that describes menus that do not exist is worse than a short one. What the app does when you open it is the authority. -------------------------------------------------------------------------- End of manual. the app itself is the authority on what it does. ### macOS App Target id: `mac-app` ============================ Your project — user manual ============================ What this is : a macOS App build, compiled for you by Morpheus Generated : 2026-10-18 This file travelled with your download. It covers installing the app, starting it, and the things that platform does to unsigned software. It is written from what Morpheus knew at compile time — for what the app does once it is running, see the project's own notes at the bottom. INSTALLING IT (macOS App) You downloaded a disk image (.dmg). 1. Double-click it — Finder mounts it like a USB stick. 2. Drag the app onto the Applications shortcut sitting next to it. 3. Eject the disk image (the eject arrow beside it in Finder). STARTING IT The menu bar for a Mac app is at the TOP OF THE SCREEN, next to the logo — not inside the window. If a window looks empty, click it once and look up there. IF IT WILL NOT OPEN, OR WILL NOT START NOT SIGNED: this app is not signed with a paid Apple Developer certificate, so macOS will probably refuse the first launch — "Apple could not verify ... is free of malware", or the older "...is damaged and can't be opened. You should move it to the Bin." It is not damaged. Fix: open Terminal (Applications -> Utilities) and run, with the path to YOUR app: xattr -cr /Applications/YourApp.app Then open it again. Or: System Settings -> Privacy & Security, scroll down, and click "Open Anyway" after the first attempt. CROSSED-OUT ICON (a circle with a line through it): that means the build is for a different kind of Mac, not that the file is broken. Download the other one — "intel" for an Intel Mac, "apple-silicon" for an M-series Mac. Apple menu -> About This Mac names your chip. CONNECTING IT TO MORPHEUS Some compiled apps can sign in to Morpheus from inside the app, so the work they do is billed to your own account. That is a device login: the app shows a short code, you approve it in your browser on the Morpheus site, and the app picks up a token scoped to one capability. If the app has no such screen, it does not need one. -------------------------------------------------------------------------- THE PROJECT'S OWN NOTES (none shipped) -------------------------------------------------------------------------- This project did not ship a README, so there is nothing here to quote. Morpheus will not invent one: it has not read the app's interface, and a manual that describes menus that do not exist is worse than a short one. What the app does when you open it is the authority. -------------------------------------------------------------------------- End of manual. the app itself is the authority on what it does. ### iOS App Target id: `ios-app` ============================ Your project — user manual ============================ What this is : a iOS App build, compiled for you by Morpheus Generated : 2026-10-18 This file travelled with your download. It covers installing the app, starting it, and the things that platform does to unsigned software. It is written from what Morpheus knew at compile time — for what the app does once it is running, see the project's own notes at the bottom. INSTALLING IT (iOS App) You downloaded an iOS .ipa. An .ipa only installs on a device it was signed for. On a normal iPhone this needs a Mac with Xcode (or a sideloading tool) and a signing identity that includes your device — Apple does not allow installing unsigned apps. STARTING IT The first launch of a sideloaded app is refused until you trust the developer in Settings -> General -> VPN & Device Management. IF IT WILL NOT OPEN, OR WILL NOT START "Unable to Install" almost always means the signing identity does not cover this device. CONNECTING IT TO MORPHEUS Some compiled apps can sign in to Morpheus from inside the app, so the work they do is billed to your own account. That is a device login: the app shows a short code, you approve it in your browser on the Morpheus site, and the app picks up a token scoped to one capability. If the app has no such screen, it does not need one. -------------------------------------------------------------------------- THE PROJECT'S OWN NOTES (none shipped) -------------------------------------------------------------------------- This project did not ship a README, so there is nothing here to quote. Morpheus will not invent one: it has not read the app's interface, and a manual that describes menus that do not exist is worse than a short one. What the app does when you open it is the authority. -------------------------------------------------------------------------- End of manual. the app itself is the authority on what it does. ### Raspberry Pi Distro Target id: `rpi-distro` ============================ Your project — user manual ============================ What this is : a Raspberry Pi Distro build, compiled for you by Morpheus Generated : 2026-10-18 This file travelled with your download. It covers installing the app, starting it, and the things that platform does to unsigned software. It is written from what Morpheus knew at compile time — for what the app does once it is running, see the project's own notes at the bottom. INSTALLING IT (Raspberry Pi Distro) You downloaded a disk image for a Raspberry Pi. Write it to a microSD card with Raspberry Pi Imager (or balenaEtcher) — pick "Use custom image" and choose this file. Then boot the Pi. STARTING IT The first boot takes several minutes while it resizes and sets itself up. IF IT WILL NOT OPEN, OR WILL NOT START A Pi that never appears on the network: re-check that the image was written to the card, not to a file. CONNECTING IT TO MORPHEUS Some compiled apps can sign in to Morpheus from inside the app, so the work they do is billed to your own account. That is a device login: the app shows a short code, you approve it in your browser on the Morpheus site, and the app picks up a token scoped to one capability. If the app has no such screen, it does not need one. -------------------------------------------------------------------------- THE PROJECT'S OWN NOTES (none shipped) -------------------------------------------------------------------------- This project did not ship a README, so there is nothing here to quote. Morpheus will not invent one: it has not read the app's interface, and a manual that describes menus that do not exist is worse than a short one. What the app does when you open it is the authority. -------------------------------------------------------------------------- End of manual. the app itself is the authority on what it does. ### Linux Distro (PC/Server) Target id: `linux-distro` ============================ Your project — user manual ============================ What this is : a Linux Distro (PC/Server) build, compiled for you by Morpheus Generated : 2026-10-18 This file travelled with your download. It covers installing the app, starting it, and the things that platform does to unsigned software. It is written from what Morpheus knew at compile time — for what the app does once it is running, see the project's own notes at the bottom. INSTALLING IT (Linux Distro (PC/Server)) You downloaded a disk image. Write it to a USB stick or disk with balenaEtcher, or boot it directly in a virtual machine. STARTING IT Nothing is installed on your computer until you run the installer from the booted system. IF IT WILL NOT OPEN, OR WILL NOT START A machine that will not boot it usually has Secure Boot enabled — turn it off for the install. CONNECTING IT TO MORPHEUS Some compiled apps can sign in to Morpheus from inside the app, so the work they do is billed to your own account. That is a device login: the app shows a short code, you approve it in your browser on the Morpheus site, and the app picks up a token scoped to one capability. If the app has no such screen, it does not need one. -------------------------------------------------------------------------- THE PROJECT'S OWN NOTES (none shipped) -------------------------------------------------------------------------- This project did not ship a README, so there is nothing here to quote. Morpheus will not invent one: it has not read the app's interface, and a manual that describes menus that do not exist is worse than a short one. What the app does when you open it is the authority. -------------------------------------------------------------------------- End of manual. the app itself is the authority on what it does. ### Arduino Firmware Target id: `arduino-firmware` ============================ Your project — user manual ============================ What this is : a Arduino Firmware build, compiled for you by Morpheus Generated : 2026-10-18 This file travelled with your download. It covers installing the app, starting it, and the things that platform does to unsigned software. It is written from what Morpheus knew at compile time — for what the app does once it is running, see the project's own notes at the bottom. INSTALLING IT (Arduino Firmware) You downloaded firmware for a board. Flash it with the tool the project documents (avrdude, esptool, or the Arduino IDE's "Upload" with the binary). STARTING IT Most boards need a reset (or a double-tap of the reset button) to enter the bootloader for flashing. IF IT WILL NOT OPEN, OR WILL NOT START A board that reports no port is usually a missing USB serial driver, not the firmware. CONNECTING IT TO MORPHEUS Some compiled apps can sign in to Morpheus from inside the app, so the work they do is billed to your own account. That is a device login: the app shows a short code, you approve it in your browser on the Morpheus site, and the app picks up a token scoped to one capability. If the app has no such screen, it does not need one. -------------------------------------------------------------------------- THE PROJECT'S OWN NOTES (none shipped) -------------------------------------------------------------------------- This project did not ship a README, so there is nothing here to quote. Morpheus will not invent one: it has not read the app's interface, and a manual that describes menus that do not exist is worse than a short one. What the app does when you open it is the authority. -------------------------------------------------------------------------- End of manual. the app itself is the authority on what it does. ### Audio Plugin — macOS (VST3 · AU · CLAP) Target id: `audio-plugin-macos` ============================ Your project — user manual ============================ What this is : a Audio Plugin — macOS (VST3 · AU · CLAP) build, compiled for you by Morpheus Generated : 2026-10-18 This file travelled with your download. It covers installing the app, starting it, and the things that platform does to unsigned software. It is written from what Morpheus knew at compile time — for what the app does once it is running, see the project's own notes at the bottom. INSTALLING IT (Audio Plugin — macOS (VST3 · AU · CLAP)) THIS PLUGIN IS FOR MACOS ONLY. It will not load on Windows or Linux — there is no Audio Unit outside Apple's platforms, and the .vst3 and .clap in this download are macOS bundles. If you or your collaborators are on Windows, this is not the build for them. You downloaded FOUR zips because a plugin is four files in four different places, and a DAW only looks in its own. Unzip them and move each one to its folder — the USER one only needs your account, the SYSTEM one needs your password and is shared by everyone on the Mac. VST3 -> ~/Library/Audio/Plug-Ins/VST3/ AU -> ~/Library/Audio/Plug-Ins/Components/ CLAP -> ~/Library/Audio/Plug-Ins/CLAP/ standalone -> anywhere you like; it is an ordinary app, double-click it. If the folder does not exist, make it: open Finder, press Shift-Command-G, paste the line above without the trailing slash, and create it. STARTING IT THE BLOCKS AND THEIR ORDER ARE YOURS. The plugin runs the signal path you arranged in the app — the COMPILE panel's SIGNAL PATH button — and that arrangement is saved in morpheus.plugin.json as the "board" key, so the file you are reading the rest of this from says what this plugin does. A MODEL MAKES IT AN AMP. Put a .nam file in the project — models/ is the usual place, or name one in morpheus.plugin.json as "model" — and rebuild. The model is baked into this download, so there is nothing to install beside it. Without one the plugin is a stereo gain stage, which is what you have if you are reading this and expected an amp sim. A CABINET MAKES IT SOUND LIKE A RECORDING. A .nam is usually the amplifier; the speaker is a separate convolution. Put a .wav impulse response of your cabinet in the project — models/ is the usual place, or name one in morpheus.plugin.json as "cab" — and rebuild. It is baked into the download the same way, so there is nothing to install beside it. A DAW scans its plugin folders at startup, so QUIT AND REOPEN IT — a plugin installed while it was running usually will not appear. Ableton, Reaper, Bitwig and Cubase take the VST3. LOGIC, GARAGEBAND AND MAIN STAGE TAKE ONLY THE AU — they cannot load a VST3 at all, so install the .component for those. The plugin is listed under the vendor name from its manifest, not under "Morpheus", unless that is what you put there. IF IT WILL NOT OPEN, OR WILL NOT START NOT SIGNED: this plugin has no paid Apple Developer certificate, so macOS may quarantine it and the DAW will not see it even though the file is there. That is not a broken plugin. Fix: open Terminal (Applications -> Utilities) and run, with the path to YOUR plugin: xattr -cr ~/Library/Audio/Plug-Ins/VST3/"Your Plugin.vst3" Do the same for the .component, then reopen the DAW. NOT LISTED IN LOGIC: Logic only reads Audio Units. If you installed the .vst3 only, install the .component as well. If it is installed and still missing, run auval -v aufx SUBT MANU with the four-character codes from morpheus.plugin.json — it reports what Logic objects to. TWO PLUGINS WITH THE SAME NAME: the AU registration codes in morpheus.plugin.json must be unique. Change auSubtype, rebuild, and reinstall — a duplicate makes one of them invisible. INSTALLED THE WRONG ARCHITECTURE: this build is universal (Intel and Apple silicon), so it should load on either. If an older copy is still installed, delete it before installing this one. CONNECTING IT TO MORPHEUS Some compiled apps can sign in to Morpheus from inside the app, so the work they do is billed to your own account. That is a device login: the app shows a short code, you approve it in your browser on the Morpheus site, and the app picks up a token scoped to one capability. If the app has no such screen, it does not need one. -------------------------------------------------------------------------- THE PROJECT'S OWN NOTES (none shipped) -------------------------------------------------------------------------- This project did not ship a README, so there is nothing here to quote. Morpheus will not invent one: it has not read the app's interface, and a manual that describes menus that do not exist is worse than a short one. What the app does when you open it is the authority. -------------------------------------------------------------------------- End of manual. the app itself is the authority on what it does. ### Audio Plugin — Windows (VST3 · CLAP) Target id: `audio-plugin-windows` ============================ Your project — user manual ============================ What this is : a Audio Plugin — Windows (VST3 · CLAP) build, compiled for you by Morpheus Generated : 2026-10-18 This file travelled with your download. It covers installing the app, starting it, and the things that platform does to unsigned software. It is written from what Morpheus knew at compile time — for what the app does once it is running, see the project's own notes at the bottom. INSTALLING IT (Audio Plugin — Windows (VST3 · CLAP)) THIS PLUGIN IS FOR WINDOWS ONLY. It will not load on macOS or Linux. There is also no Audio Unit in it — only Apple has those — which is why this download has three files where the macOS one has four. If you are on a Mac, build the MACOS AUDIO PLUGIN route instead. You downloaded THREE zips because a plugin is three files in two different places, and a DAW only looks in its own. Unzip them and move each one to its folder — the "Common Files" folders are shared, so copying into them needs administrator rights. VST3 -> C:\Program Files\Common Files\VST3\ CLAP -> C:\Program Files\Common Files\CLAP\ standalone -> anywhere you like; it is an ordinary .exe, double-click it. If a folder does not exist, create it. The name must match exactly, because the host looks for the path and not for the file. STARTING IT THE BLOCKS AND THEIR ORDER ARE YOURS. The plugin runs the signal path you arranged in the app — the COMPILE panel's SIGNAL PATH button — and that arrangement is saved in morpheus.plugin.json as the "board" key, so the file you are reading the rest of this from says what this plugin does. A MODEL MAKES IT AN AMP. Put a .nam file in the project — models/ is the usual place, or name one in morpheus.plugin.json as "model" — and rebuild. The model is baked into this download, so there is nothing to install beside it. Without one the plugin is a stereo gain stage, which is what you have if you are reading this and expected an amp sim. A CABINET MAKES IT SOUND LIKE A RECORDING. A .nam is usually the amplifier; the speaker is a separate convolution. Put a .wav impulse response of your cabinet in the project — models/ is the usual place, or name one in morpheus.plugin.json as "cab" — and rebuild. It is baked into the download the same way, so there is nothing to install beside it. A DAW scans its plugin folders at startup, so QUIT AND REOPEN IT — a plugin installed while it was running usually will not appear. Ableton, Reaper, Bitwig, Cubase and Studio One take the VST3. CLAP is supported by Reaper, Bitwig and a growing list of hosts; if your DAW does not list it, install the VST3 as well. The plugin is listed under the vendor name from its manifest, not under "Morpheus", unless that is what you put there. 64-BIT ONLY: this build is x64. A 32-bit DAW cannot load it, and that is the most common reason a plugin installs and never appears. IF IT WILL NOT OPEN, OR WILL NOT START NOT SIGNED, AND ON WINDOWS THAT MATTERS LESS THAN YOU WOULD THINK: plugins load unsigned in every DAW, so a VST3 or CLAP that does not appear is almost always in the wrong folder or was skipped by the scan — check the path above first. SMARTSCREEN: the standalone .exe is unsigned, so Windows may show "Windows protected your PC" the first time you run it. Choose "More info" and then "Run anyway". That is the unsigned-file warning, not a detection. NOT LISTED: check that the .vst3 is directly in the VST3 folder and not inside a subfolder created by unzipping. A VST3 on Windows is a single FILE, so a folder containing one is not installed. TWO PLUGINS WITH THE SAME NAME: the id in morpheus.plugin.json is what hosts key on, and two plugins sharing one shadow each other. Change the id and rebuild. CONNECTING IT TO MORPHEUS Some compiled apps can sign in to Morpheus from inside the app, so the work they do is billed to your own account. That is a device login: the app shows a short code, you approve it in your browser on the Morpheus site, and the app picks up a token scoped to one capability. If the app has no such screen, it does not need one. -------------------------------------------------------------------------- THE PROJECT'S OWN NOTES (none shipped) -------------------------------------------------------------------------- This project did not ship a README, so there is nothing here to quote. Morpheus will not invent one: it has not read the app's interface, and a manual that describes menus that do not exist is worse than a short one. What the app does when you open it is the authority. -------------------------------------------------------------------------- End of manual. the app itself is the authority on what it does. ### Audio Plugin — Linux ARM (VST3 · CLAP) Target id: `audio-plugin-linux-arm` ============================ Your project — user manual ============================ What this is : a Audio Plugin — Linux ARM (VST3 · CLAP) build, compiled for you by Morpheus Generated : 2026-10-18 This file travelled with your download. It covers installing the app, starting it, and the things that platform does to unsigned software. It is written from what Morpheus knew at compile time — for what the app does once it is running, see the project's own notes at the bottom. INSTALLING IT (Audio Plugin — Linux ARM (VST3 · CLAP)) THIS PLUGIN IS FOR LINUX ON ARM (aarch64) ONLY — a Raspberry Pi 4, Pi 5, or another ARM64 Linux machine. It will NOT load on an ordinary Intel or AMD Linux desktop: a plugin is compiled for one instruction set, so a build for a Pi and a build for a laptop are different files even though both are "Linux". If you are on an x86-64 Linux desktop, this is not the build for you. There is also no Audio Unit in it — only Apple has those — so this download has three files where the macOS one has four. You downloaded THREE zips because a plugin is three files in different places, and a host only looks in its own. Unzip them and move each one to its folder: VST3 -> ~/.vst3/ (just you) or /usr/lib/vst3/ (everyone, needs sudo) CLAP -> ~/.clap/ (just you) or /usr/lib/clap/ (everyone, needs sudo) standalone -> anywhere you like, but make it executable: chmod +x The VST3 is a FOLDER, not a file — copy the whole .vst3 directory, not the .so inside it. If a folder does not exist, create it: mkdir -p ~/.vst3 ~/.clap STARTING IT THE BLOCKS AND THEIR ORDER ARE YOURS. The plugin runs the signal path you arranged in the app — the COMPILE panel's SIGNAL PATH button — and that arrangement is saved in morpheus.plugin.json as the "board" key, so the file you are reading the rest of this from says what this plugin does. A MODEL MAKES IT AN AMP. Put a .nam file in the project — models/ is the usual place, or name one in morpheus.plugin.json as "model" — and rebuild. The model is baked into this download, so there is nothing to install beside it. Without one the plugin is a stereo gain stage, which is what you have if you are reading this and expected an amp sim. A CABINET MAKES IT SOUND LIKE A RECORDING. A .nam is usually the amplifier; the speaker is a separate convolution. Put a .wav impulse response of your cabinet in the project — models/ is the usual place, or name one in morpheus.plugin.json as "cab" — and rebuild. It is baked into the download the same way, so there is nothing to install beside it. A host scans its plugin folders at startup, so RESTART IT — a plugin installed while it was running usually will not appear. THE STANDALONE NEEDS A DESKTOP. Its window is X11, so it runs on Raspberry Pi OS with the desktop, and it does NOT run on a headless Pi OS Lite image — there it fails with a display error, which is not a broken build. On a headless Pi the format to use is the VST3 or the CLAP, loaded by a host. The plugin is listed under the vendor name from its manifest, not under "Morpheus", unless that is what you put there. THE PI NEEDS ENOUGH OF IT: a Pi 4 or 5 runs the plugin comfortably; a Pi Zero or a Pi 3 will load it and may not keep up, which sounds like crackling and dropouts rather than an error. IF IT WILL NOT OPEN, OR WILL NOT START NOT LISTED: almost always the folder. Check that the .vst3 FOLDER (not the .so inside it) is directly in ~/.vst3, and remember that a host launched from a different user account sees a different home. WRONG MACHINE: if you copied this to an Intel or AMD Linux box it will not load, and the error names the file rather than the reason. Build the LINUX ARM route for a Pi and use a Linux x86 route for a desktop — they are different downloads on purpose. NOT SIGNED, AND ON LINUX THAT BARELY EXISTS AS A CONCEPT: plugins load unsigned here. A plugin that does not appear is in the wrong folder or was skipped by the scan — not blocked by the system. A HOST THAT LOADS NEITHER FORMAT: LV2 is the other common plugin format on Linux, and this build does not produce it. Check that what you are loading into takes VST3 or CLAP before rebuilding anything. TWO PLUGINS WITH THE SAME NAME: the id in morpheus.plugin.json is what hosts key on, and two plugins sharing one shadow each other. Change the id and rebuild. CONNECTING IT TO MORPHEUS Some compiled apps can sign in to Morpheus from inside the app, so the work they do is billed to your own account. That is a device login: the app shows a short code, you approve it in your browser on the Morpheus site, and the app picks up a token scoped to one capability. If the app has no such screen, it does not need one. -------------------------------------------------------------------------- THE PROJECT'S OWN NOTES (none shipped) -------------------------------------------------------------------------- This project did not ship a README, so there is nothing here to quote. Morpheus will not invent one: it has not read the app's interface, and a manual that describes menus that do not exist is worse than a short one. What the app does when you open it is the authority. -------------------------------------------------------------------------- End of manual. the app itself is the authority on what it does.