Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.pluxx.dev/llms.txt

Use this file to discover all available pages before exploring further.

This example uses the repository’s self-hosting project in example/pluxx. If you want the flagship third-party example instead of the self-hosted one, use Docs Ops Flagship Proof.

​
Why this example exists

Pluxx ships its own local plugin so the same workflow can be used from inside a host coding agent. That makes this example useful for two reasons:
  • it shows the source-project shape Pluxx expects
  • it shows how Pluxx can be installed and used as a plugin inside another host
It also shows the intended product split:
  • the CLI is the engine
  • the Pluxx plugin is the native UX layer
That is the recommended architecture for Pluxx itself. Do not treat the plugin as a second bundled runtime.

​
Repository example

Repository path: Source project shape: 
example/pluxx/
  pluxx.config.ts
  INSTRUCTIONS.md
  skills/
  commands/
  scripts/
  .pluxx/
    mcp.json
    taxonomy.json
Built outputs: 
dist/claude-code/
dist/cursor/
dist/codex/
dist/opencode/

​
Typical local workflow

From the repository root: 
npx @orchid-labs/pluxx doctor
npx @orchid-labs/pluxx lint
npx @orchid-labs/pluxx test --install --trust
npx @orchid-labs/pluxx verify-install --target claude-code cursor codex opencode
Install one host locally: 
npx @orchid-labs/pluxx install --target claude-code --trust
If Claude Code is already open, run /reload-plugins in the active session after install. If the installed bundle still looks wrong, inspect the shipped bundle directly: 
npx @orchid-labs/pluxx doctor --consumer ~/.claude/plugins/data/pluxx-local-pluxx/plugins/pluxx

​
What this proves

This example is not about a third-party MCP import. It shows that Pluxx’s own source-project model is stable enough to package and test Pluxx itself across the core four hosts.