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.