Start a company
mkdir maple-street && cd maple-streetnpx sanoma init --name "Maple Street Studio" --you "Dana Reyes" --email dana@maplestreet.studioIn an empty directory (dotfiles aside), sanoma init starts a company there, then runs it, as sanoma does there without its options: it copies the template this package ships (template/: sanoma.config.ts with the Anthropic connector, the model the app’s chat answers on, Resend, which sends sign-in codes (login.sender), GitHub, Sanoma Cloud, and the connectors of the chat’s coding agents (OpenAI for Codex, OpenCode, Pi; Claude Code and Copilot come with Anthropic’s and GitHub’s), secrets.ts (the bootstrap keys’ bindings, and SANOMA_CLOUD_TOKEN read from the environment only where it is set, as a host gives it), a record-lead workflow with its scenario, resources/data.ts (the Outbound board it records to), resources/sanoma/infra.ts (the database and host on Sanoma Cloud the company goes live on, named by its slug: --name without its accents, made lower case, each run of other characters a dash, else the directory’s name the same way when that leaves nothing (a name in another script), at <slug>.sanoma.work; nothing is made until it goes live, and until then a merge deploys nothing), policies/policy.cedar (sending or publishing waits for admin) and policies/changes.cedar (every change waits for admin), resources/people.ts with you as its one person, in admin (named --you, else git’s user.name, with --email, else git’s user.email, as the email a host’s sign-in sends codes to; your id is your GitHub login as gh is signed in, else this machine’s user name), an empty resources/ tree, AGENTS.md, .env.example), names the package after the directory, writes --name as the config’s name (the company’s name as the app shows it; without it, the package’s name stands), writes .env with independent new SANOMA_SIGNING_KEY and SANOMA_SECRETS_KEY values (keeping what a .env there already sets; no database URL, so the company runs on its own Postgres), commits what it wrote (never a dotfile that was already there) as the first commit of a git repository on main, “Start a Sanoma company”, as your git user, then installs with the package manager that ran it (npm_config_user_agent; pnpm when it names none), with sanoma at its own exact version and each connector the template names at the exact version released with it, and adds the lockfile to that commit. The sanoma it installed then serves the company; the chat asks for the Anthropic key, pasted on its connector page, before its first turn. Without git or a git user it stops before writing anything; a failed install leaves the commit, to install and run sanoma again in. A directory holding anything else and no sanoma.config.ts is refused, as for every command (sanoma init exits 2 there). An --email that is no address is refused (exit 2) before anything is written. Sanoma-AI/company-template, which Sanoma Cloud’s sign-up makes a company from, is this template as each release pushes it there (release.yml), at that release’s versions with a lockfile.
These pages describe sanoma 0.11.24.