Go to file

Molecule AI · sdk-lead d587919d17 Merge pull request '[migrate] vanity import go.moleculesai.app/cli (internal#71 phase 2)' (#2 ) from migrate/issue-71-vanity-imports into main		2026-05-09 00:59:40 +00:00
.claude	docs: add CLAUDE.md, known-issues.md, and .claude/settings.json (#2 )	2026-04-20 23:10:40 +00:00
.github/workflows	ci(release): switch release.yml to GoReleaser + race-detector tests	2026-04-30 05:30:31 -07:00
bin	fix(cli): align rootCmd.Use to goreleaser binary name	2026-04-22 05:36:07 +00:00
cmd/molecule	fix(post-suspension): vanity import path go.moleculesai.app/cli (closes molecule-ai/internal#71 phase 2)	2026-05-07 22:26:45 +00:00
internal	lint: extend gate to .json files (internal#71 — package metadata drift)	2026-05-07 22:57:16 +00:00
.gitignore	chore: gitignore credentials for molecule-cli	2026-04-16 09:18:55 -07:00
.goreleaser.yaml	ci(release): switch release.yml to GoReleaser + race-detector tests	2026-04-30 05:30:31 -07:00
CLAUDE.md	fix(post-suspension): vanity import path go.moleculesai.app/cli (closes molecule-ai/internal#71 phase 2)	2026-05-07 22:26:45 +00:00
go.mod	fix(post-suspension): vanity import path go.moleculesai.app/cli (closes molecule-ai/internal#71 phase 2)	2026-05-07 22:26:45 +00:00
go.sum	feat: implement full CLI command tree	2026-04-21 01:18:24 +00:00
known-issues.md	fix(post-suspension): vanity import path go.moleculesai.app/cli (closes molecule-ai/internal#71 phase 2)	2026-05-07 22:26:45 +00:00
pr-description-draft-cli-full.md	fix(cli): align rootCmd.Use to goreleaser binary name	2026-04-22 05:36:07 +00:00
README.md	fix(post-suspension): vanity import path go.moleculesai.app/cli (closes molecule-ai/internal#71 phase 2)	2026-05-07 22:26:45 +00:00

README.md

molecule-cli

Command-line companion for Molecule AI. The primary entry point for external-runtime workspaces — bridge a workspace to a local agent backend (Claude Code, an arbitrary shell command, or a mock for CI).

Install

go install go.moleculesai.app/cli/cmd/molecule@latest

The vanity import path go.moleculesai.app/cli resolves via the Molecules AI go-get responder (issue internal#71) to our canonical SCM at git.moleculesai.app. It is independent of any specific SCM host — when we move SCMs again, no install command changes.

Alternatively, build from source:

git clone https://git.moleculesai.app/molecule-ai/molecule-cli.git
cd molecule-cli
go build -o molecule ./cmd/molecule

Quick start — connect an external workspace

When you create a workspace with runtime: external, the platform returns a per-workspace token. Run:

export MOLECULE_API_URL=https://your-tenant.staging.moleculesai.app
export MOLECULE_WORKSPACE_TOKEN=ws_secret_xxx

molecule connect ws_abcdef

connect registers the workspace, starts heartbeating, polls the platform for inbound A2A messages, and dispatches each message to the selected backend. Replies are posted back over the platform API.

Backends

--backend selects how A2A messages are handled. Three are built in:

Name	What it does
`claude-code`	Default. Invokes `claude -p <message>` for each turn (claude-code SDK).
`exec`	Runs an arbitrary shell command (`--backend-opt cmd=...`). Stdout = reply.
`mock`	Echo backend for CI / smoke tests.

Backend options are passed via repeatable --backend-opt KEY=VALUE:

# Claude Code with a 10-minute per-turn timeout
molecule connect ws_abc \
  --backend claude-code \
  --backend-opt timeout=10m

# Generic shell handler
molecule connect ws_abc \
  --backend exec \
  --backend-opt cmd='./my-agent.sh' \
  --backend-opt timeout=5m

Other useful flags

--mode poll|push         delivery mode (default: poll)
--interval-ms 2000       poll cadence
--since-secs 60          initial activity cursor lookback
--token TOKEN            override MOLECULE_WORKSPACE_TOKEN
--dry-run                build backend + print summary, exit

State (the activity cursor) is persisted to ~/.config/molecule/state/<workspace-id>.json (mode 0600) so a restart resumes from the last delivered message.

Other subcommands

molecule agent      list / inspect agent sessions
molecule config     view / set CLI defaults
molecule completion generate shell completions

The full M1 design is in RFC #10 (originally filed on the suspended GitHub org; the issue may be re-filed on Gitea — check the issue tracker for the live discussion).