molecule-ai/molecule-core
52
0
Fork 2
Code Issues 183 Pull Requests 17 Actions 1 Packages Projects Releases Wiki Activity

canvas Config tab renders empty PROVIDER/MODEL for env-resolved workspaces — show effective values, guard Save from wiping #2594

New Issue
Closed
opened 2026-06-11 16:41:25 +00:00 by core-devops · 0 comments
core-devops commented 2026-06-11 16:41:25 +00:00
Member
Copy Link
Copy Source

Live report (agents-team, CP Security Agent 387d0deb): workspace is ONLINE and working, but Config tab shows PROVIDER* = '— select provider —' and MODEL* = '— select provider first —'.

Mechanism: the workspace's stored config is EMPTY (GET /workspaces/:id/config → {"data":{}}, DB model=NULL) — it predates/bypassed the create-time model requirement and the runtime resolves model/provider from persona env baked at provision (MODEL / MODEL_PROVIDER / ANTHROPIC_BASE_URL), which is why it runs fine. The Config form renders the stored config only, so it shows blanks for a healthy agent — confusing (today's CTO question: "how can some workspace config without provider and working?") and risky:

  • A user who fills ONLY one field (or hits Save & Restart with blanks) can wedge a working agent (fail-closed model rule rejects, or worse a partial write drifts config vs env).

Asks:

  1. When config.yaml lacks provider/model, the form should show the effective values resolved from the runtime (same source as get_runtime_identity: live env) with a 'derived from environment (not set in config.yaml)' hint — not empty required dropdowns.
  2. Save must not silently clear env-derived routing: either persist the effective values into config on first save, or block save with a clear message.
  3. Backfill consideration: migrate env-resolved workspaces' model/provider into config.yaml (SSOT convergence with providers.yaml registry).

Related: providers.yaml runtime-matrix SSOT (RFC#580 Opt C), CTO 2026-05-22 no-silent-DefaultModel directive.

🤖 Generated with Claude Code

Live report (agents-team, CP Security Agent 387d0deb): workspace is ONLINE and working, but Config tab shows PROVIDER* = '— select provider —' and MODEL* = '— select provider first —'. Mechanism: the workspace's stored config is EMPTY (`GET /workspaces/:id/config` → `{"data":{}}`, DB `model=NULL`) — it predates/bypassed the create-time model requirement and the runtime resolves model/provider from **persona env baked at provision** (MODEL / MODEL_PROVIDER / ANTHROPIC_BASE_URL), which is why it runs fine. The Config form renders the stored config only, so it shows blanks for a healthy agent — confusing (today's CTO question: "how can some workspace config without provider and working?") and risky: - A user who fills ONLY one field (or hits Save & Restart with blanks) can wedge a working agent (fail-closed model rule rejects, or worse a partial write drifts config vs env). Asks: 1. When config.yaml lacks provider/model, the form should show the **effective** values resolved from the runtime (same source as `get_runtime_identity`: live env) with a 'derived from environment (not set in config.yaml)' hint — not empty required dropdowns. 2. Save must not silently clear env-derived routing: either persist the effective values into config on first save, or block save with a clear message. 3. Backfill consideration: migrate env-resolved workspaces' model/provider into config.yaml (SSOT convergence with providers.yaml registry). Related: providers.yaml runtime-matrix SSOT (RFC#580 Opt C), CTO 2026-05-22 no-silent-DefaultModel directive. 🤖 Generated with [Claude Code](https://claude.com/claude-code)
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
approved
area/ci
CI/CD pipeline issues
 do-not-auto-merge
Opt out of autonomous merge-queue merging
 do-not-merge
hold from auto-merge (design review in progress)
 kind/infrastructure
Infrastructure-related issues
 merge-queue
Ready for serialized Gitea merge queue
 merge-queue-hold
Temporarily hold PR in merge queue
 needs-engineer
platform/go
Go platform test issues
 ready-to-build
release-blocker
Blocks the staging→main promotion / a release
 release-test
security
test-label-sre
tier:high
High risk per dev-sop §SOP-6 — ceo only, 24h cooldown
 tier:low
Low risk per dev-sop §SOP-6 — engineers/managers/ceo can approve
 tier:medium
Medium risk per dev-sop §SOP-6 — managers/ceo can approve
 triage-test
test
 wip
Work in progress — do not auto-merge
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
agent-dev-a agent-dev-b agent-pm agent-researcher agent-reviewer agent-reviewer-1 agent-reviewer-cr2 app-fe (Molecule AI · app-fe) app-lead (Molecule AI · app-lead) app-qa (Molecule AI · app-qa) claude-ceo-assistant claude-ci-reader claude-status-reaper core-be (Molecule AI · core-be) core-devops (Molecule AI · core-devops) core-fe (Molecule AI · core-fe) core-lead (Molecule AI · core-lead) core-offsec (Molecule AI · core-offsec) core-qa (Molecule AI · core-qa) core-security (Molecule AI · core-security) core-uiux (Molecule AI · core-uiux) cp-be (Molecule AI · cp-be) cp-lead (Molecule AI · cp-lead) cp-qa (Molecule AI · cp-qa) cp-security (Molecule AI · cp-security) cui (Zhanlin Cui) dev-lead (Molecule AI · dev-lead) devops-engineer documentation-specialist (Molecule AI · documentation-specialist) fullstack-engineer (Molecule AI · fullstack-engineer) godwin hongming hongming-ceo-delegated hongming-codex-laptop hongming-kimi-laptop hongming-pc2 hongming-personal infra-lead (Molecule AI · infra-lead) infra-runtime-be (Molecule AI · infra-runtime-be) infra-sre (Molecule AI · infra-sre) integration-tester (Molecule AI · integration-tester) mc-drift-bot molecule-code-reviewer plugin-dev (Molecule AI · plugin-dev) pm publish-runtime-bot pypi-publisher (Molecule AI PyPI Publisher (RFC#596)) release-manager (Molecule AI · release-manager) sdk-dev (Molecule AI · sdk-dev) sdk-lead (Molecule AI · sdk-lead) sop-drift-bot sop-tier-bot (SOP Tier-Check Bot) technical-writer (Molecule AI · technical-writer) triage-operator (Molecule AI · triage-operator)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: molecule-ai/molecule-core#2594
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?