@passioncode-ai/passioncode weekly downloads statistics

PassionCode.ai launcher

The PassionCode.ai launcher (@passioncode-ai/passioncode on npm) sets up PassionCode.ai on a computer with one command: the apps (Fabric, Fabric Switchboard, Fabric Dashboards, Fabric Inbox, Project Observatory) from their signed releases, their MCP servers for every coding agent on it, and the PassionCode.ai skills listed in family.json. Run the same command on a computer that is already set up, and it checks everything, repairs what is wrong and tells you what changed.

npx @passioncode-ai/passioncode@latest setup     # a new computer: set up · an existing one: check and repair
npx @passioncode-ai/passioncode@latest doctor    # check only; changes nothing

Member	Skills
Fabric Agent Adapter	creating-fabric-agents, adapting-projects-to-fabric, building-fabric-services
Observatory Log	explaining-changes, handling-secrets, tracking-resources (+ its session hooks)
passioncode	setting-up-passioncode (set up and check a computer), working-in-passioncode (the organisation's working rules, for every contributor's agent) and the once-a-day update check

Only PassionCode.ai products are members. Agents that people build for themselves stay out of it, even when they implement Fabric protocols.

Set it up with your coding agent

Paste this into Claude Code, Codex or another coding agent:

Set up PassionCode.ai on this computer, or check and repair it if it is already set up. Run npx --yes @passioncode-ai/passioncode@latest setup --yes --json (it needs Node 18 or newer) and read its JSON: it installs the missing apps from their signed releases, the skills and every MCP server, repairs whatever is wrong, and checks everything again. Do not download or install anything by hand, and never stop or kill a running app. Then run each product onboarding step it lists that an agent may run, never ask me for a key or password in the chat (the tools open their own hidden prompts), and finish with npx --yes @passioncode-ai/passioncode@latest doctor. Tell me briefly what you set up or fixed, what still fails, and the numbered steps only I can do, such as signing in, and remind me to restart you so the new skills and MCP servers load.

Once the skills are installed, "set me up" or "check my setup" is enough: the setting-up-passioncode skill knows the rest. What stays yours: signing in, consenting, typing a secret into a product's own hidden prompt, starting Docker for Fabric, and restarting your agent.

Quick start for a new teammate

1. Install (Node 18 or newer; the Claude Code CLI on PATH for the plugins): npx @passioncode-ai/passioncode@latest setup, then restart your agents. In a terminal it asks one question per app and one for the repairs (a --json run never asks); --yes accepts the plan, --with/--without <ids> choose apps (switchboard, dashboards, observatory, inbox, fabric), --no-apps sets up the skills and MCP only, --dry-run shows the plan. Apps are installed on macOS; on other systems setup names each download page, and on Windows doctor reads which version of each app is installed. Skills only: npx @passioncode-ai/passioncode@latest update.
2. Configure: nothing to set, no account and no key. Background updates are on by default; npx @passioncode-ai/passioncode@latest config set update.auto off turns them off. Each app's own onboarding (sign-ins, Fabric Inbox's server, Observatory's projects) is listed by setup.
3. MCP: the launcher serves no MCP server of its own. It registers the apps' servers (fabric-dashboards, fabric with fabric-mcp --runner <agent>, and switchboard with switchboard mcp) for Claude Code, Codex CLI, Gemini CLI and Kimi Code, and doctor proves each one with a real call: initialize, tools/list, then list_services, switchboard_accounts or observatory_status. Fabric's server is never started by doctor, because it enrols a session as it starts: doctor checks its entry, and your agent's first fabric_whoami is the proving call. Fabric is an early preview, so only setup registers it, never a background update. Project Observatory and Fabric Inbox register their own servers through their onboarding; doctor checks those too.
4. Develop: clone, then npm test. There are no dependencies and no lockfile, so there is nothing to install (npm ci refuses to run here). npm run vendor builds payload/ from the members pinned in family.json; claude plugin validate ./payload --strict checks it. Start in lib/launcher.js (update, restore, status, uninstall) and bin/passioncode.js (the CLI); AGENTS.md maps the rest and CONTRIBUTING.md the rules.

How it installs…