molecule-ai/molecule-core
52
0
Fork 2
Code Issues 184 Pull Requests 15 Actions Packages Projects Releases Wiki Activity

[runtime] workspace boot does not set git user.name/user.email from $GITEA_USER (persona drift on commits) #155

New Issue
Closed
opened 2026-05-09 19:41:29 +00:00 by claude-ceo-assistant · 0 comments
claude-ceo-assistant commented 2026-05-09 19:41:29 +00:00
Owner
Copy Link
Copy Source

Symptom

Every Core-* workspace booted from core-team-only org-template has GITEA_USER populated correctly (core-lead, core-be, etc.), GITEA_TOKEN injected (40-char PAT), but git config --global user.name and user.email are unset. Result: any commit from these workspaces would be authored under whatever git falls back to (empty, or the runtime image's baked default), not the team's persona identity.

Why it matters

Same class as #193 (persona drift on background agents). The point of per-persona Gitea identities is that a Gitea audit shows the team did the work — not all work attributed to claude-ceo-assistant (which is the founder PAT and got us banned on GitHub). With user.name/user.email unset, every team commit pushes under the WRONG identity even though the right identity exists in env.

Fix shape

Workspace runtime image (molecule-ai-workspace-runtime and per-template variants like workspace-template-claude-code) should run at boot:

[ -n "${GITEA_USER:-}" ] && git config --global user.name  "$GITEA_USER"
[ -n "${GITEA_USER:-}" ] && git config --global user.email "${GITEA_USER}@bot.moleculesai.app"

Place: entrypoint.sh or whatever runs as PID 1 before the agent starts. Idempotent (git config overwrites cleanly).

Workaround (already applied to 8 local workspaces)

docker exec ws-<id> sh -c "git config --global user.name '$GITEA_USER' && ..." — but this resets on container restart. Real fix needs to live in the image.

Filed by

orchestrator after Hongming flagged 0 team commits in Gitea despite 8 workspaces "running" (2026-05-09 19:40 UTC).

## Symptom Every Core-* workspace booted from `core-team-only` org-template has `GITEA_USER` populated correctly (`core-lead`, `core-be`, etc.), `GITEA_TOKEN` injected (40-char PAT), but `git config --global user.name` and `user.email` are **unset**. Result: any commit from these workspaces would be authored under whatever git falls back to (empty, or the runtime image's baked default), not the team's persona identity. ## Why it matters Same class as #193 (persona drift on background agents). The point of per-persona Gitea identities is that a Gitea audit shows the team did the work — not all work attributed to `claude-ceo-assistant` (which is the founder PAT and got us banned on GitHub). With `user.name`/`user.email` unset, every team commit pushes under the WRONG identity even though the right identity exists in env. ## Fix shape Workspace runtime image (`molecule-ai-workspace-runtime` and per-template variants like `workspace-template-claude-code`) should run at boot: ```sh [ -n "${GITEA_USER:-}" ] && git config --global user.name "$GITEA_USER" [ -n "${GITEA_USER:-}" ] && git config --global user.email "${GITEA_USER}@bot.moleculesai.app" ``` Place: `entrypoint.sh` or whatever runs as PID 1 before the agent starts. Idempotent (`git config` overwrites cleanly). ## Workaround (already applied to 8 local workspaces) `docker exec ws-<id> sh -c "git config --global user.name '$GITEA_USER' && ..."` — but this resets on container restart. Real fix needs to live in the image. ## Filed by orchestrator after Hongming flagged 0 team commits in Gitea despite 8 workspaces "running" (2026-05-09 19:40 UTC).
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
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
 platform/go
Go platform test issues
 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#155
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?