molecule-ai/molecule-ai-workspace-runtime
35
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
94 Commits 4 Branches 13 Tags 377 KiB
Python 96.6%
Shell 3.4%
main
Go to file
devops-engineer 3a9c76eeef
All checks were successful
ci / mirror-guard (push) Successful in 10s
Details
Secret scan / Scan diff for credential-shaped strings (push) Successful in 13s
Details
Merge pull request 'fix(post-suspension): migrate github.com/Molecule-AI refs to git.moleculesai.app (Class G #168)' (#2) from fix/post-suspension-github-urls into main
2026-05-07 20:02:39 +00:00
.github/workflows fix(ci): inline secret-scan body, drop cross-repo uses: of private molecule-core 2026-05-07 02:29:03 -07:00
molecule_runtime fix(pre-commit): align SECRET_PATTERNS with molecule-core canonical (add sk-cp-) 2026-04-28 15:21:13 -07:00
tests chore(precommit): add sk-cp- MiniMax pattern (F1088 retroactive fix); bump 0.1.16 → 0.1.17 2026-04-26 21:43:24 -07:00
.gitignore chore: gitignore credentials for molecule-ai-workspace-runtime 2026-04-16 09:18:48 -07:00
CONTRIBUTING.md fix(post-suspension): migrate github.com/Molecule-AI refs to git.moleculesai.app (Class G #168) 2026-05-07 13:02:35 -07:00
pyproject.toml chore(precommit): add sk-cp- MiniMax pattern (F1088 retroactive fix); bump 0.1.16 → 0.1.17 2026-04-26 21:43:24 -07:00
README.md fix(post-suspension): migrate github.com/Molecule-AI refs to git.moleculesai.app (Class G #168) 2026-05-07 13:02:35 -07:00

README.md

molecule-ai-workspace-runtime

⚠️ This repo is a publish artifact, not the source of truth.

Runtime code lives in Molecule-AI/molecule-core → workspace/. This repo is regenerated and republished from there by the publish-runtime workflow on every runtime-v* tag.

Don't edit files here directly. PRs against this repo will not be merged. Open them against molecule-core instead.

Shared Python runtime infrastructure for all Molecule AI agent adapters.

This package provides the core machinery every Molecule AI workspace container needs:

  • A2A server — registers with the platform, heartbeats, serves A2A JSON-RPC
  • Adapter interface — BaseAdapter / AdapterConfig / SetupResult
  • Built-in tools — delegation, memory, approvals, sandbox, telemetry
  • Skill loader — loads and hot-reloads skill modules from /configs/skills/
  • Plugin system — per-workspace + shared plugin discovery and install
  • Config / preflight — YAML config loading with validation

Installation

pip install molecule-ai-workspace-runtime

Adapter discovery

The runtime discovers adapters in two ways:

  1. ADAPTER_MODULE env var (standalone adapter repos):

    ADAPTER_MODULE=adapter molecule-runtime

    The runtime imports adapter and calls adapter.Adapter.

  2. Subdirectory scan (monorepo local dev): falls back to scanning molecule_runtime/adapters/<runtime>/ and importing the matching subdir's Adapter class.

Contributing

Don't open PRs here. Send your change to Molecule-AI/molecule-core under the workspace/ directory. After your PR merges to main and a runtime-v* tag is pushed, the publish-runtime workflow rebuilds this mirror + uploads the new wheel to PyPI.

See docs/workspace-runtime-package.md for the full publishing flow.

Why this split

The runtime needs to ship as a PyPI artifact (so the 8 workspace template images can pip install it), but it also needs to evolve in lock-step with the platform's wire protocol (queue shape, A2A metadata, event payloads). A monorepo edit + auto-publish pipeline gives both: atomic cross-cutting changes, plus a clean PyPI release on every tag.

For the back-history of why this repo previously was the source of truth and the drift that caused: see issue Molecule-AI/molecule-core#2103.