|
All checks were successful
CI / Adapter unit tests (push) Successful in 1m31s
CI / Template validation (static) (push) Successful in 1m34s
Secret scan / Scan diff for credential-shaped strings (pull_request) Successful in 8s
CI / Template validation (static) (pull_request) Successful in 1m20s
CI / Adapter unit tests (pull_request) Successful in 1m21s
CI / Template validation (runtime) (pull_request) Successful in 14m10s
CI / Template validation (runtime) (push) Successful in 14m54s
CI / validate (pull_request) Successful in 10s
CI / validate (push) Successful in 7s
The .github/workflows/ tree is silently shadowed on this repo because
.gitea/workflows/ exists (reference_molecule_core_actions_gitea_only) —
so both files were never firing on Gitea Actions:
- Secret scan / Scan diff for credential-shaped strings is a required
status-check on main branch protection; until now it has been satisfied
only via a compensating signed POST /statuses/{SHA}. Porting restores
the gate.
- publish-image was dormant, so the claude-code template image stayed
stale and never rebuilt against new runtime versions. After this port
the cascade signal (molecule-core/publish-runtime.yml git-pushes
.runtime-version to main) trips on: push: branches: [main] here and
pushes ECR :latest + :sha-<7> to
153263036946.dkr.ecr.us-east-2.amazonaws.com/molecule-ai/workspace-template-claude-code.
Both files copy the canonical Gitea-ported shape verbatim from
molecule-core and molecule-ai-workspace-template-hermes respectively
(only repo-specific identifiers — image name + descriptions — adjusted).
Gitea 1.22.6 hostile-shape constraints already baked in:
- no workflow_dispatch.inputs (feedback_gitea_workflow_dispatch_inputs_unsupported)
- no cross-repo uses: (feedback_gitea_cross_repo_uses_blocked)
- no on.push.paths: (feedback_path_filtered_workflow_cant_be_required)
- GITHUB_SERVER_URL pinned at workflow level
(feedback_act_runner_github_server_url)
T4 close-out — Hongming authorized direct merge.
|
||
|---|---|---|
| .claude | ||
| .gitea/workflows | ||
| .github/workflows | ||
| .molecule-ci/scripts | ||
| runbooks | ||
| scripts | ||
| tests | ||
| __init__.py | ||
| .gitattributes | ||
| .gitignore | ||
| .runtime-version | ||
| adapter.py | ||
| claude_sdk_executor.py | ||
| CLAUDE.md | ||
| config.yaml | ||
| Dockerfile | ||
| entrypoint.sh | ||
| known-issues.md | ||
| README.md | ||
| requirements.txt | ||
template-claude-code-default
Molecule AI workspace template for the claude-code-default runtime.
Usage
In Molecule AI canvas
Select this template when creating a new workspace — it appears in the template picker automatically.
From a URL (community install)
Paste this URL when creating a workspace:
github://Molecule-AI/template-claude-code-default
Files
config.yaml— workspace configuration (runtime, model, skills, etc.)system-prompt.md— agent system prompt (if present)
Auth paths
| Path | Env var(s) | Where to get the key |
|---|---|---|
| OAuth (Claude Code subscription) | CLAUDE_CODE_OAUTH_TOKEN |
claude login |
| Anthropic API (direct) | ANTHROPIC_API_KEY |
console.anthropic.com |
| Third-party Anthropic-compat (e.g. Xiaomi MiMo pay-as-you-go) | ANTHROPIC_API_KEY (provider's key) |
provider console |
| Xiaomi MiMo Token Plan | ANTHROPIC_API_KEY (Token Plan key), ANTHROPIC_BASE_URL (Token Plan endpoint) |
token-plan dashboard |
For third-party providers, entrypoint.sh rewrites ANTHROPIC_BASE_URL based on the selected MODEL so the claude CLI routes there. Currently auto-routes mimo-* models to https://api.xiaomimimo.com/anthropic (pay-as-you-go). Token Plan users should set ANTHROPIC_BASE_URL=https://token-plan-sgp.xiaomimimo.com/anthropic as a workspace or org-level secret — the shell mapping is the fallback and operator-set values always win. Other Token Plan endpoints (e.g. token-plan-hk.xiaomimimo.com) can be used by setting the secret explicitly.
Schema version
template_schema_version: 1 — compatible with Molecule AI platform v1.x.
License
Business Source License 1.1 — © Molecule AI.