JoAi Plugins Monorepo

Canonical JoAi plugin repo for agent runtimes.

Design goals:

• JoAi-general plugins, not one-off task plugins.
• One plugin per runtime integration (claude, codex, etc.).
• Capabilities are added as modules over time.

Current capability modules:

• board: board item auto-execution callbacks and iteration control.
• mcp: connect to JoAi's MCP servers for apps and agents.

Repository Layout

• plugins/claude: Claude plugin root (joai)
• plugins/codex: Codex MCP server (joai)
• scripts/: install, uninstall, verify, validate
• .claude-plugin/marketplace.json: Claude marketplace index

Install

Claude:

bash scripts/install-claude.sh

Codex:

bash scripts/install-codex.sh

Both:

bash scripts/install-all.sh

Optional Claude scope:

bash scripts/install-all.sh project

Equivalent Claude CLI commands (official flow):

claude plugin marketplace add --scope user JoAiHQ/joai--plugins
claude plugin install --scope user joai@joai-claude-plugins

If the marketplace already exists:

claude plugin marketplace update joai-claude-plugins
claude plugin install --scope user joai@joai-claude-plugins

Validate

bash scripts/validate.sh

Strict mode:

bash scripts/validate.sh --strict

Verify Installed State

bash scripts/verify.sh

Quickstart

• docs-quickstart.md

Official References

• Claude plugin install and CLI reference:
  • Install plugins
  • Plugin CLI reference
• Claude hooks HTTP response handling:
  • Hooks HTTP response handling
• Codex MCP:
  • Remote MCP tools

Capability Expansion Model

When adding new JoAi functionality:

1. Extend plugins/claude and plugins/codex in-place.
2. Add new namespaced commands/tools by capability.
3. Keep runtime plugin identity stable (joai).
4. Avoid creating new runtime plugins unless install/security constraints require it.