diff --git a/.github/workflows/mantis-discord-status-reactions.yml b/.github/workflows/mantis-discord-status-reactions.yml
index 2c59ab94d36..429f339e8a3 100644
--- a/.github/workflows/mantis-discord-status-reactions.yml
+++ b/.github/workflows/mantis-discord-status-reactions.yml
@@ -287,7 +287,7 @@ jobs:
           ARTIFACT_URL: ${{ steps.upload_artifact.outputs.artifact-url }}
           BASELINE_SHA: ${{ needs.validate_refs.outputs.baseline_revision }}
           CANDIDATE_SHA: ${{ needs.validate_refs.outputs.candidate_revision }}
-          MANTIS_COMMENT_BOT_LOGIN: openclaw-mantis-qa[bot]
+          MANTIS_COMMENT_BOT_LOGIN: ${{ vars.MANTIS_GITHUB_APP_BOT_LOGIN || 'openclaw-mantis-qa[bot]' }}
         shell: bash
         run: |
           set -euo pipefail
diff --git a/docs/concepts/mantis.md b/docs/concepts/mantis.md
index 6d5b4c757a5..d9090ae204b 100644
--- a/docs/concepts/mantis.md
+++ b/docs/concepts/mantis.md
@@ -355,9 +355,11 @@ messages, and other bulky evidence stay in the Actions artifact.
 Production workflows should post those comments with the Mantis GitHub App, not
 with `github-actions[bot]`. Store the app id and private key as
 `MANTIS_GITHUB_APP_ID` and `MANTIS_GITHUB_APP_PRIVATE_KEY` GitHub Actions
-secrets. The workflow should update an existing Mantis-owned comment when one
-exists; if only an older `github-actions[bot]` comment exists, it should create a
-new Mantis-owned comment instead of rewriting the legacy bot comment.
+secrets. If the app is renamed, set `MANTIS_GITHUB_APP_BOT_LOGIN` as a GitHub
+Actions variable to the new bot login, for example `openclaw-mantis[bot]`. The
+workflow should update an existing Mantis-owned comment when one exists; if only
+an older `github-actions[bot]` comment exists, it should create a new
+Mantis-owned comment instead of rewriting the legacy bot comment.
 
 The PR comment should be short and visual: