Power your agent
คำสั่งของผู้เผยแพร่เอง ไม่ใช่เอนด์พอยต์ของ PlugMCP
Host a copy with our keys and logs.
npx -y @passioncode-ai/[email protected]Claude Code ไม่มีลิงก์ติดตั้งสำหรับคำสั่งแบบโลคัล ให้คัดลอกคำสั่งด้านล่างแล้วรันในเทอร์มินัล
claude mcp add passioncode-ai-passioncode -- npx -y @passioncode-ai/passioncode@0.2.77รันในเทอร์มินัล
{ "mcpServers": { "passioncode-ai-passioncode": { "command": "npx", "args": [ "-y", "@passioncode-ai/[email protected]" ] } }}claude_desktop_config.json
URL แบบรีโมตหรือคำสั่งบนเครื่องของคุณ? การติดตั้งสองแบบต่างกันอย่างไร
รันบน PlugMCP
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
เปิดจากผู้เผยแพร่
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 . 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.
Set up PassionCode.ai on a computer with one command: the apps from their verified releases, their MCP servers for every coding agent and the PassionCode.ai skills. Check and repair it with the same command or `doctor`.
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
Only PassionCode.ai products are members. Agents that people build for themselves stay out of it, even when they implement Fabric protocols.
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 withnpx --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.
PATH for the plugins):
npx @passioncode-ai/passioncode@latest setup, then restart your agents. In a terminal it asks
one question per app; --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.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.fabric-dashboards, fabric (fabric-mcp --runner <agent>) and switchboard
(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.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.passioncode at
~/.passioncode/current — no GitHub access needed. A plugin that was installed from
its old single-member marketplace (fabric-agent-adapter@fabric-agent-adapter,
observatory-log@observatory-log) is replaced once the new one is verified, and that
marketplace is unregistered and taken out of settings.json once nothing installed
comes from it.~/.agents/skills, linked from each channel that exists on
the machine. On Windows these links (and ~/.passioncode/current) are junctions, which
need neither an administrator session nor Developer Mode.~/.claude/skills: a plain copy there shadows the plugin. Such
copies, and hub entries that pointed at a repository's working tree, are moved into
~/.passioncode/quarantine/ — npx @passioncode-ai/passioncode@latest restore puts them back.~/.passioncode/releases/<version>; an update
keeps the release it replaced for rollback and removes older ones.update (and therefore setup) registers the MCP server inside each installed app — Fabric
Dashboards (fabric-dashboards), Fabric Switchboard (switchboard, unless Claude Code already
gets it from the switchboard plugin) and, from setup only because it is an early preview,
Fabric (fabric, with each agent's own --runner) —
for every agent that is present: Claude Code (through claude mcp add --scope user), Codex CLI
(~/.codex/config.toml), Gemini CLI (~/.gemini/settings.json) and Kimi Code
(~/.kimi-code/mcp.json). An entry that already exists is left alone; one that points elsewhere
is reported and kept. restore and uninstall remove what the launcher added
(ADR-0003,
ADR-0004).setup checks first, then installs the absent apps you chose, repairs what the checks found,
checks again and prints a before → after table and the steps that stay yours. On a healthy
computer it changes nothing and exits 0. An app is installed only after its release's
SHA256SUMS.asc verifies against the PassionCode.ai release key bundled in this package
(fingerprint 63B3 0DC3 24BD 6974 87AA 3194 4FAF B8AE C803 B6A7), the file matches the signed
checksum and GitHub's digest, and the app passes codesign, carries team KJ35UYYL22, has its
notarization ticket stapled and is accepted by Gatekeeper. An outdated or damaged app is
reinstalled only when it is not running; the old one goes to the Trash. A family service that
does not answer is started through launchd (launchctl kickstart, never a kill).
doctor changes nothing. It reads prerequisites, the skill set, each app's version, signature
and team, each agent's MCP entries with one proving call per server, and the Fabric services of
the family; each line names its state and its fix. Exit codes: 0 no check failed, 1 a
check (or a setup step) failed, 2 bad arguments. doctor --fix runs setup's repairs without
installing new apps. Details: the CLI contract.
At Claude Code session start the passioncode plugin uses a cached npm check for up
to 24 hours and, when a newer set is out and every npm account that publishes it is in the
plugin's trust.json, updates to that exact version in the background — it takes
effect in the next session. A version published by anyone else is named and not
installed (SECURITY.md).
npx @passioncode-ai/passioncode@latest config set update.auto off makes it only say so.
status reads local state without contacting npm. Its npm version is labelled
npm latest (cached) with the saved check timestamp, or check time unknown.
When that stable version is below the installed stable version, the line also says
stale: older than installed. A newer or equal cached version is still a saved
observation, not a live registry check. With no saved version it says
npm latest: not checked; --json retains the raw latest and checkedAt fields.
npx @passioncode-ai/passioncode@latest status # the installed release: its members, their channels, shadows
npx @passioncode-ai/passioncode@latest update --dry-run
npx @passioncode-ai/passioncode@latest uninstall
For supported flags, JSON fields, exit codes and partial-failure recovery, read the
CLI contract. restore repairs the latest quarantine batch;
it is not a release rollback. A successful uninstall preserves recovery files and
turns automatic updates off. Unsupported flags are rejected before mutation.
Repository docs describe the current source. See the documentation index and dated handoffs for which changes have actually been published or installed.
The ssheleg family (sshlg-skills, on npm as
sshlg-skills) is a separate, public set of skills for coding agents: a working method with
task-pipeline (gated delivery and release iterations), agent-sync (leases and id
reservation), super-ux, sheleg-design, make-skill, agent-stack and others. It is not a
member of this launcher's set, and neither set installs or vendors the other's plugins. Install
both and update each as one set with its own command:
npx @passioncode-ai/passioncode@latest update # this set: Fabric Agent Adapter, Observatory Log, passioncode
npx --yes sshlg-skills@latest update # the family; it takes no member argument
npx sshlg-skills routers writes one routing block into each agent's global
instructions (~/.claude/CLAUDE.md, ~/.codex/AGENTS.md, ~/.gemini/GEMINI.md, …). It says
which member owns which kind of work: interface behaviour, look, copy, delivery, coordination.
On a computer where Fabric is installed (its services directory exists) the block gains a
fabric router, which sends questions about the computer's agent services to the Fabric
tooling and to this set's Fabric Agent Adapter skills.task-pipeline's release iteration. Principle 10's wait rule (a wait is
not a stop) reaches personal repositories as the family's opt-in rule block
(npx sshlg-skills config set rules.wait on). In a passioncode-ai repository both reach the
agent through this plugin's session-start line and working-in-passioncode instead.task-pipeline writes workflow
checkpoints and planned handoffs through it and records cross-project lessons in its shared
lesson store, as proposals; agent-sync takes the git leases that passioncode-ai repositories
declare.passioncode marketplace, each family member's from its own (<name>@<name>). A plain skill
copy in ~/.claude/skills shadows a plugin; both updaters take such copies out of the way and
never create one. Never update a plugin member with a bare npx skills update <name>: it
recreates that copy.ref to that tag in family.json.version in package.json and plugin/passioncode/.claude-plugin/plugin.json
(a test holds them and the CHANGELOG in sync), add the CHANGELOG section.plugin/passioncode/trust.json
(npmPublishers), and be the package's only kind of maintainer — otherwise every
installed hook refuses the update and says so.vX.Y.Z and push the tag. .github/workflows/release.yml
validates, checks the tag against both manifests, creates the GitHub release from the
CHANGELOG section, vendors every member from its own repository at its pinned tag,
runs the tests, exercises packed update/status/uninstall with a fake Claude CLI
in a temporary home (node scripts/smoke-pack.mjs), publishes
@passioncode-ai/passioncode and waits until npm serves it. It runs when the repository
variables RELEASE_ENABLED and PUBLISH_NPMJS are true; npm auth is trusted publishing
(OIDC) or the NPM_TOKEN secret; a private member needs MEMBERS_READ_TOKEN.
By hand, npm publish still works: prepublishOnly vendors from tags only (--release),
refuses credential-shaped strings and runs the tests.npx @passioncode-ai/passioncode@<version> update on each machine; restart the agents.Vendoring clones every member from its own repository at its tag. A maintainer with
local clones can point the vendor at them instead — PASSIONCODE_CHECKOUT_ROOT=<dir>
reads a member from <dir>/<repository name>, and PASSIONCODE_CHECKOUT_<MEMBER>=<path>
(the member's name upper-cased, - as _) names one clone kept under another name.
PASSIONCODE_VENDOR_CLONE=1 ignores both. family.json names no machine paths.
Open source under the GNU AGPL-3.0. A commercial license is available for use that does not meet the AGPL's terms — passioncode.ai/business. Versions before 0.1.12 were released under PolyForm Noncommercial or Internal Use (v0.1.5 to v0.1.11) and MIT (v0.1.4 and earlier); each keeps the licence it was released under. Contributions are accepted under CLA.md (CONTRIBUTING.md).
Set up PassionCode.ai on a computer with one command: the apps from their verified releases, their MCP servers for every coding agent and the PassionCode.ai skills. Check and repair it with the same c
{ "mcpServers": { "passioncode-ai-passioncode": { "command": "npx", "args": [ "-y", "@passioncode-ai/[email protected]" ] } }}ภาพรวม
Set up PassionCode.ai on a computer with one command: the apps from their verified releases, their MCP servers for every coding agent and the PassionCode.ai skills. Check and repair it with the same command or `doctor`.
เครื่องมือ
ยังไม่มีรายการเครื่องมือ เซิร์ฟเวอร์แบบรีโมตจะได้รายการหลังการตรวจสอบสถานะครั้งแรก
FAQ
คัดลอกคอนฟิก stdio สำหรับ Cursor, Claude Desktop, Claude Code หรือ VS Code ได้ในหน้านี้ คอนฟิกนี้ใช้การติดตั้งของผู้เผยแพร่ ไม่ใช่พร็อกซีของ PlugMCP
ระเบียนนี้ไม่ได้ระบุตัวแปรสภาพแวดล้อมที่จำเป็น
@passioncode Ai/passioncode ทำงานแบบโลคัลผ่าน stdio
ตรวจสอบล่าสุดเมื่อ 2026-11-14 Set up PassionCode.ai on a computer with one command: the apps from their verified releases, their MCP servers for every coding agent and the PassionCode.ai skills. Check and repair it with the same command or `doctor`.