@aetheros/create

One command that sets up AetherOS in a project: a new empty folder or an existing app.

npx @aetheros/create            # this folder
npx @aetheros/create my-app     # a new folder (created, git init)

Without npm access (or to test an unreleased checkout), build the self-contained installer from an AetherOS checkout (npm run installer:pack) and run it in your project folder: npx --yes --package "/path/to/aetheros-create-<version>.tgz" create-aetheros.

What it does

1. Installs the AetherOS runtime into .aether/runtime/ with its own package.json. Your package.json, lock files, node_modules and scripts are not touched. Archives are checked against their sha512 digests before install.
2. Adds .aether/runtime/, .aether/local/ and .aether/runs/ to .gitignore (keeps what's there).
3. Writes .aether/aether.mjs, a small launcher that always runs AetherOS from the project folder: node .aether/aether.mjs workspace, node .aether/aether.mjs check, and every other aether command.
4. Runs the existing aether setup (kits github,memory,claude,openai; existing files are kept, never replaced; git hooks and MCP settings are not installed unless you ask with --kits), aether workspace init and aether doctor.
5. Writes start-aetheros.cmd and start-aetheros.sh, then runs aether start: asks for an AI provider key once (saved in your home folder, never the project), starts the workspace and opens the orb screens (the Talk tab is the voice). Next time, double-click start-aetheros.cmd (or run ./start-aetheros.sh). Use --no-start in scripts and CI.

It asks only for the brand (OS and assistant name) when you run it in a terminal without --yes. It never asks for or stores API keys: set ANTHROPIC_API_KEY or OPENAI_API_KEY in your terminal for live replies.

Running it again

Safe. A runtime of the same version is reused, files that exist are kept, and .gitignore entries are added once. A runtime of another version is reported and left alone unless you pass --upgrade. A .aether/runtime folder that this installer didn't make, or a .aether/aether.mjs that isn't its launcher, is reported and never overwritten. If the app itself lists @aetheros/* packages in its package.json, that is reported and left as it is.

Options

| Option | What it does | |---|---| | --yes | No questions | | --no-start | Don't open the workspace at the end | | --kits a,b | Kits for aether setup | | --os-name, --assistant, --accent | Branding | | --port, --no-memory | Workspace options | | --from <dir> | Install from a folder of package archives with manifest.json (for example artifacts/ from npm run pack:verify) | | --manifest-sha256 <hex> | Require that digest for the manifest | | --upgrade | Replace a runtime of another version | | --no-git | No git init in a new, empty folder | | --dry-run | Show the plan, change nothing |

Works on Windows, macOS and Linux with Node.js 20 or newer (tested with paths containing spaces and from another folder).