Skip to content

Publish kars plugins to their ecosystems (OpenClaw plugin, Headlamp plugin, lightweight mesh plugin) #427

Description

@pallakatos

Track proper, registry-based publishing of the three kars plugins. Today they are bundled into the CLI npm package / sandbox image so kars dev --release works out-of-the-box, but each should also be published to its native ecosystem so third parties can consume them independently.

1. Official OpenClaw kars plugin

The kars OpenClaw plugin (runtimes/openclaw, mesh + governance integration). Publish to the OpenClaw plugin ecosystem / npm so any OpenClaw user can add kars governance + E2E mesh without the full kars stack.

2. Headlamp plugin

The kars Headlamp CRD-view plugin (tools/headlamp-plugin). Publish per the Headlamp plugin publishing flow → https://headlamp.dev/docs/latest/development/plugins/publishing/ (Artifact Hub package + plugin catalog), so it installs via Headlamp's plugin manager rather than a side-loaded ConfigMap.

  • Currently: prebuilt dist/main.js is bundled into the CLI package and side-loaded into the kind cluster's Headlamp.

3. Lightweight mesh plugin (runtime-agnostic)

A minimal AGT-mesh client plugin that works for any OpenClaw-compatible runtime — including nemoclaw. Decouple the Signal/AGT mesh transport from the kars-specific bits so it's a drop-in for other agent runtimes. Stretch goal: validate it against nemoclaw.

For now

Everything is bundled (CLI npm package + sandbox image) so kars dev --release / kars up --release work with no repo checkout. This issue tracks moving to proper per-ecosystem publishing.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions