A Launcher launch still opens the tool in the active workspace's folder,
tracks its process, streams observed output and stops it. What it no
longer does:
- set WAGGLE_SIGNAL_EMIT, WAGGLE_SIDECAR_URL, HIVE_MIND_DATA_DIR or the
Room identity variables (WAGGLE_RUN_ID, WAGGLE_ROOM_ID,
WAGGLE_DANCE_TEAM_ID, WAGGLE_SENDER_ID, WAGGLE_RUN_TOKEN). Only the
removed coding-agent hooks and the WaggleDance CLI read them. The
external-process allowlist now admits WAGGLE_WORKSPACE_ID alone;
- issue a run credential. Run tokens existed for Room workers (the dance
CLI and OpenClaw's model calls), so the registry's credential store,
the middleware's run-token bearer on /v1/chat/completions and the
proxy's per-run model scope go. While an agent run with a model is
active, the proxy still serves only the session bearer.
The run record that a launch creates in the agent-run registry stays: it
backs cancel from the Room canvas, which this change does not remove.
Waggle Room is not part of the community edition (decision Q2, ADR-0002).
Its headless runs of Claude Code, Codex, Hermes and OpenClaw needed the
packaged collaboration CLI from the removed @waggle/hive-mind-cli, so
POST /api/tools/run answered 503 collaboration_runtime_missing.
- Remove POST /api/tools/run (routes/external-tool-runs.ts) with its
Room fan-out, WaggleDance publishing, OpenClaw provisioning and the
memory write-back of run results.
- Remove runExternalTool (agent/external-tool-runner.ts) and
resolveWaggleRuntime; the taskkill path helper moves into the process
tracker, its only remaining user.
- Launcher: drop the hidden "Run task" composer, the Room hand-off and
adapter.runExternalToolTask. Detect, launch, watch and stop stay.
- Drop the `room` flag from the memory feature map: it only gated the
Launcher task button.
- The viewer policy no longer reads participants[].workspaceIds, a body
shape only /api/tools/run accepted.
- The WaggleDance routes left the sidecar with team mode, so the
x-waggle-run-token header no longer opens /api/waggle-dance/signal or
/api/waggle-dance/signals. A run token still authenticates only as a
Bearer on /v1/chat/completions (OpenClaw).
- Remove the session inactivity timeout. It switched on only in team
mode, when CLERK_SECRET_KEY was set.
KVARK is the commercial enterprise product and is not part of the community
edition. The agent's KVARK tools were never wired into the server, so
removing them changes no runtime behaviour beyond the routes listed here.
- agent: delete kvark-tools; CombinedRetrieval and formatCombinedResult now
merge workspace and personal memory only (no KVARK lane, no source
conflict note); connector substrate is always 'waggle'
- agent: promote_skill stops at workspace scope; team and enterprise scopes
answer "not available in this edition" instead of an upgrade prompt
- server: delete src/kvark and GET /api/marketplace/enterprise-packs
- marketplace: delete ENTERPRISE_PACKS
- compliance (EU AI Act dashboard, its templates and the KVARK template
seeded on every boot): delete core/src/compliance, the /api/compliance/*
routes, agent compliance-pdf and the Cockpit compliance panel. The
ai_interactions table lives in the memory substrate and goes with P1.5.