Skip to content

Local Packs

Jump to bottom
Lorenzo edited this page Apr 16, 2026 · 1 revision

Local Packs

JoyBoy separates the public open-source core from optional local packs.

The public core should remain clean, neutral, and safe to publish. Local packs can extend behavior on the user's own machine without forcing those assets or workflows into the main repository.

What Local Packs Can Do

Depending on the pack contract, local packs may provide:

  • Extra routing behavior.
  • Prompt assets.
  • Model metadata.
  • UI surfaces.
  • Specialized workflows.
  • Provider-specific setup guidance.
  • Local-only runtime assets.

Public Core Boundary

The public repository should not include:

  • Private provider tokens.
  • Downloaded model weights.
  • Generated outputs.
  • Private local assets.
  • Mature pack assets.
  • User-specific paths.
  • Runtime caches.

The core should provide the harness, validation, UI, and runtime boundaries.

Mature Workflows

Some optional local packs may target mature workflows where legal, consensual, and compliant with platform policies.

These packs are not part of the public core, and JoyBoy should keep that boundary explicit.

Roadmap For Packs

  • Clearer install flow.
  • Better manifest validation.
  • Safer activation and deactivation.
  • Better documentation for what packs can extend.
  • Better UI distinction between public core features and local pack features.

The goal is flexibility without making the public project messy or risky.

Clone this wiki locally