molecule-ai-workspace-runtime 0.1.100

Molecule AI workspace runtime — shared infrastructure for all agent adapters

molecule-ai-workspace-runtime

Shared workspace runtime for Molecule AI agent adapters. Installed by every workspace template image (workspace-template-claude-code, -langgraph, -hermes, etc.) to provide A2A delegation, heartbeat, memory, plugin loading, and skill management.

This package is published from the molecule-core monorepo workspace/ directory by the publish-runtime GitHub Actions workflow on every runtime-v* tag push. Do not edit this package directly — edit workspace/ in the monorepo.

External-runtime MCP server (molecule-mcp)

Operators running an agent outside the platform's container fleet (any runtime that supports MCP stdio — Claude Code, hermes, codex, etc.) can install this wheel and run the universal MCP server locally:

pip install molecule-ai-workspace-runtime
WORKSPACE_ID=<uuid> \
  PLATFORM_URL=https://<tenant>.staging.moleculesai.app \
  MOLECULE_WORKSPACE_TOKEN=<bearer> \
  molecule-mcp

That exposes the same 8 platform tools (delegate_task, list_peers, send_message_to_user, commit_memory, etc.) that container-bound runtimes already get via the workspace's auto-spawned MCP. Register the binary in your agent's MCP config (e.g. Claude Code's claude mcp add molecule -- molecule-mcp with the env above).

The token comes from the canvas → Tokens tab. Restarting an external workspace from the canvas no longer revokes the token (PR #2412), so operator tokens persist across status nudges.

See docs/workspace-runtime-package.md for the publish flow and architecture.